Update Get-WinEvent.md (#1876)

Removed future tense in a couple of places to improve readability. Minor edit.

reference/5.1/Microsoft.PowerShell.Diagnostics/Get-WinEvent.md

@@ -84,7 +84,7 @@ Classic logs are usually retrieved first, followed by the new Windows Eventing l
 Because there are typically more than a hundred event logs, this parameter requires a log name or name pattern.
 To get all the logs, use *.
 
-### Example 2: Get the classic system log from a local computer
+### Example 2: Get the classic Setup log from a local computer
 ```
 PS C:\> Get-WinEvent -ListLog Setup | Format-List -Property *
 
@@ -115,7 +115,7 @@ ProviderLatency                : 1000
 ProviderControlGuid            :
 ```
 
-This command gets an object that represents the classic System log on the local computer.
+This command gets an object that represents the classic Setup log on the local computer.
 The object includes useful information about the log, including its size, event log provider, file path, and whether it is enabled.
 
 ### Example 3: Get event logs from a server
@@ -338,8 +338,8 @@ The default value is the current user.
 
 Type a user name, such as User01 or Domain01\User01.
 Or, enter a **PSCredential** object, such as one generated by the Get-Credential cmdlet.
-If you type a user name, you will be prompted for a password.
-If you type only the parameter name, you will be prompted for both a user name and a password.
+If you type a user name, you are prompted for a password.
+If you type only the parameter name, you are prompted for both a user name and a password.
 
 ```yaml
 Type: PSCredential