Fix incorrect case/capitalization in reference documents (28/38) (#11936)

* Fix incorrect case/capitalization in ref docs

This ensures the following components have the correct/consistent case
throughout the reference documentation:

Preference variable, PS environment variable, PS drive, PS provider,
PS command name, PS command argument, PS module, PS file extension,
PS host name/application, #Requires statement, parameter name,
about_* topic, member name, scope modifier, keyword, operator,
calculated property key/value, attribute, type accelerator,
type literal/name, WMI namespace/class, variable name,
special character, comment-based help keyword, product/company name,
Windows drive letter/directory, Windows/Unix environment variable

In addition, changes include fixes to incorrect terminology (e.g.,
referring to a keyword as a command) and formatting of PS syntax
elements (non-exhaustive).

* Format PowerShell example for readability

Reformat code

---------

Co-authored-by: Sean Wheeler <[email protected]>

Author: surfingoldelephant

reference/5.1/Microsoft.PowerShell.Security/Get-AuthenticodeSignature.md

@@ -65,7 +65,9 @@ command line. In this example, the name of the **FilePath** parameter, which is
 ### Example 3: Get only valid Authenticode signatures for multiple files
 
 ```powershell
-Get-ChildItem $PSHOME\*.* | ForEach-object {Get-AuthenticodeSignature $_} | Where-Object {$_.status -eq "Valid"}
+Get-ChildItem $PSHOME\*.* |
+    ForEach-Object {Get-AuthenticodeSignature $_} |
+    Where-Object {$_.Status -eq "Valid"}
 ```
 
 This command lists all of the files in the `$PSHOME` directory that have a valid Authenticode

reference/5.1/Microsoft.PowerShell.Utility/ConvertFrom-Csv.md

@@ -89,7 +89,7 @@ $Header = 'State', 'MoreData', 'StatusMessage', 'Location', 'Command',
           'BeginTime', 'EndTime', 'JobType', 'Output', 'Error', 'Progress',
           'Verbose', 'Debug', 'Warning', 'Information'
 # Delete the default header from $J
-$J = $J[1..($J.count - 1)]
+$J = $J[1..($J.Count - 1)]
 $J | ConvertFrom-Csv -Header $Header
 ```
 

reference/5.1/PSReadLine/About/about_PSReadLine.md

@@ -126,7 +126,7 @@ APIs are documented in [about_PSReadLine_Functions][02].
 PSReadLine maintains a history file containing all the commands and data you've
 entered from the command line. The history files are a file named
 `$($Host.Name)_history.txt`. On Windows systems the history file is stored at
-`$env:APPDATA\Microsoft\Windows\PowerShell\PSReadLine`.
+`$Env:APPDATA\Microsoft\Windows\PowerShell\PSReadLine`.
 
 The history can contain sensitive data including passwords. PSReadLine attempts
 to filter out sensitive information. Any command lines containing the following
@@ -213,7 +213,7 @@ kubectl get secrets
 kubectl get secret db-user-pass -o jsonpath='{.data.password}' | base64 --decode
 kubectl describe secret db-user-pass
 az account get-access-token --resource=https://app.contoso.com --query accessToken --output tsv
-$env:PGPASS = gcloud auth print-access-token
+$Env:PGPASS = gcloud auth print-access-token
 ```
 
 ### Feedback & contributing to PSReadLine

reference/5.1/PSReadLine/About/about_PSReadLine_Functions.md

@@ -1064,8 +1064,8 @@ chords.
 
 ### ViEditVisually
 
-Edit the command line in a text editor specified by `$env:EDITOR` or
-`$env:VISUAL`.
+Edit the command line in a text editor specified by `$Env:EDITOR` or
+`$Env:VISUAL`.
 
 - Emacs mode: `<Ctrl+x,Ctrl+e>`
 - Vi command mode: `<v>`

reference/5.1/PSReadLine/About/about_PSReadLine_Release_Notes.md

@@ -183,7 +183,7 @@ release:
 - Supporting line-wise yanks, including paste and undo
 - Make `y0` yank up to the start of the logical line in `VI` mode
 - Add API to detect if the screen reader is active
-- Make `PageUp/PageDown` and `CtrlPageUp/CtrlPageDown` windows only
+- Make `PageUp/PageDown` and `CtrlPageUp/CtrlPageDown` Windows-only
 - Add script block vi mode indicator option
 - Support vi mode `G` and `gg` movements in multi-line buffers
 - Supports `_` and `$` to move to the beginning and end of the logical line in

reference/5.1/PSReadLine/Set-PSReadLineOption.md

@@ -130,10 +130,10 @@ This example emits a cursor change VT escape in response to a **Vi** mode change
 function OnViModeChange {
     if ($args[0] -eq 'Command') {
         # Set the cursor to a blinking block.
-        Write-Host -NoNewLine "$([char]0x1b)[1 q"
+        Write-Host -NoNewline "$([char]0x1b)[1 q"
     } else {
         # Set the cursor to a blinking line.
-        Write-Host -NoNewLine "$([char]0x1b)[5 q"
+        Write-Host -NoNewline "$([char]0x1b)[5 q"
     }
 }
 Set-PSReadLineOption -ViModeIndicator Script -ViModeChangeHandler $Function:OnViModeChange
@@ -153,9 +153,9 @@ to history.
 
 ```powershell
 $ScriptBlock = {
-    Param([string]$line)
+    param ([string]$Line)
 
-    if ($line -match "^git") {
+    if ($Line -match "^git") {
         return $false
     } else {
         return $true
@@ -520,7 +520,7 @@ platforms store the file in different locations. The filename is stored in a var
 
 If you don't use this parameter, the default path is:
 
-`$env:APPDATA\Microsoft\Windows\PowerShell\PSReadLine\$($Host.Name)_history.txt`
+`$Env:APPDATA\Microsoft\Windows\PowerShell\PSReadLine\$($Host.Name)_history.txt`
 
 ```yaml
 Type: System.String
@@ -529,7 +529,7 @@ Aliases:
 
 Required: False
 Position: Named
-Default value: A file named $($Host.Name)_history.txt in $env:APPDATA\Microsoft\Windows\PowerShell\PSReadLine on Windows and $env:XDG_DATA_HOME/powershell/PSReadLine or $HOME/.local/share/powershell/PSReadLine on non-Windows platforms
+Default value: A file named $($Host.Name)_history.txt in $Env:APPDATA\Microsoft\Windows\PowerShell\PSReadLine on Windows and $Env:XDG_DATA_HOME/powershell/PSReadLine or $HOME/.local/share/powershell/PSReadLine on non-Windows platforms
 Accept pipeline input: False
 Accept wildcard characters: False
 ```

reference/7.4/Microsoft.PowerShell.Core/About/about_Built-in_Functions.md

@@ -53,7 +53,7 @@ the system's pager command. PowerShell uses a different default pager for
 Windows and non-Windows systems. On Windows systems, the default pager is
 `more.com`. On non-Windows systems, the default pager is `less`.
 
-If the `$env:PAGER` environment variable is defined, PowerShell uses the
+If the `$Env:PAGER` environment variable is defined, PowerShell uses the
 specified program instead of the system default.
 
 ## `prompt`

reference/7.4/Microsoft.PowerShell.Core/About/about_Calling_Generic_Methods.md

@@ -22,7 +22,7 @@ overloads, or when the generic method takes no formal parameter. PowerShell can
 fail to resolve the correct method without the explicit generic method
 arguments.
 
-For example, `[Array]::Empty<T>()`. The .NET **Array** class has a static,
+For example, `[array]::Empty<T>()`. The .NET **Array** class has a static,
 generic method `Empty<T>()` that takes no formal parameters.
 
 Prior to PowerShell 7.3, to ensure proper method resolution you had to use
@@ -72,8 +72,8 @@ require two generic type parameters and two formal value parameters.
 $result = [System.Linq.Enumerable]::Select[int, float](
     $list,
     [Func[int, float]]{
-        param($item)
-        [math]::Pow($item, 3)
+        param($Item)
+        [Math]::Pow($Item, 3)
     }
 )
 $result

reference/7.4/Microsoft.PowerShell.Core/About/about_Logging_Windows.md

@@ -203,7 +203,7 @@ private key:
 
 ```powershell
 Get-WinEvent Microsoft-Windows-PowerShell/Operational |
-    Where-Object Id -eq 4104 | Unprotect-CmsMessage
+    Where-Object Id -EQ 4104 | Unprotect-CmsMessage
 ```
 
 ## See also

reference/7.4/Microsoft.PowerShell.Core/About/about_PowerShell_Config.md

@@ -418,7 +418,7 @@ Example:
     "Transcription": {
         "EnableTranscripting": true,
         "EnableInvocationHeader": true,
-        "OutputDirectory": "c:\\tmp"
+        "OutputDirectory": "C:\\tmp"
       }
 }
 ```
@@ -436,7 +436,7 @@ Example:
 ```json
 {
     "UpdatableHelp": {
-      "DefaultSourcePath": "f:\\temp"
+      "DefaultSourcePath": "F:\\temp"
     }
 }
 ```