Fix automatic variable case (#11831)

Author: surfingoldelephant

reference/5.1/Microsoft.PowerShell.Core/About/about_Object_Creation.md

@@ -251,7 +251,7 @@ For example, the following command creates a session option object.
 ```powershell
 [System.Management.Automation.Remoting.PSSessionOption]@{
   IdleTimeout=43200000
-  SkipCnCheck=$True
+  SkipCnCheck=$true
 }
 ```
 
@@ -291,7 +291,7 @@ cmdlet can be a hash table.
 ```powershell
 New-PSSession -ComputerName Server01 -SessionOption @{
   IdleTimeout=43200000
-  SkipCnCheck=$True
+  SkipCnCheck=$true
 }
 Register-ScheduledJob -Name Test -FilePath .\Get-Inventory.ps1 -Trigger @{
   Frequency="Daily"

reference/5.1/Microsoft.PowerShell.Core/About/about_Prompts.md

@@ -73,7 +73,7 @@ For example:
 ```
 
 ```Output
-"PS $($ExecutionContext.SessionState.Path.CurrentLocation)$('>' * ($nestedPromptLevel + 1)) "
+"PS $($ExecutionContext.SessionState.Path.CurrentLocation)$('>' * ($NestedPromptLevel + 1)) "
 # .Link
 # https://go.microsoft.com/fwlink/?LinkID=225750
 # .ExternalHelp System.Management.Automation.dll-help.xml
@@ -114,7 +114,7 @@ PowerShell includes a built-in `Prompt` function.
 
 ```powershell
 function prompt {
-  "PS $($ExecutionContext.SessionState.Path.CurrentLocation)$('>' * ($nestedPromptLevel + 1)) ";
+  "PS $($ExecutionContext.SessionState.Path.CurrentLocation)$('>' * ($NestedPromptLevel + 1)) ";
   # .Link
   # https://go.microsoft.com/fwlink/?LinkID=225750
   # .ExternalHelp System.Management.Automation.dll-help.xml

reference/5.1/Microsoft.PowerShell.Core/About/about_Properties.md

@@ -28,7 +28,7 @@ object, the file changes too.
 Most objects have properties. Properties are the data that are associated with
 an object. Different types of object have different properties. For example, a
 **FileInfo** object, which represents a file, has an **IsReadOnly** property
-that contains `$True` if the file has the read-only attribute and `$false` if
+that contains `$true` if the file has the read-only attribute and `$false` if
 it doesn't. A **DirectoryInfo** object, which represents a file system
 directory, has a **Parent** property that contains the path to the parent
 directory.

reference/5.1/Microsoft.PowerShell.Core/About/about_Quoting_Rules.md

@@ -312,15 +312,15 @@ reproduced exactly. For example:
 
 ```powershell
 @'
-The $profile variable contains the path
+The $PROFILE variable contains the path
 of your PowerShell profile.
 '@
 ```
 
 The output of this command is:
 
 ```Output
-The $profile variable contains the path
+The $PROFILE variable contains the path
 of your PowerShell profile.
 ```
 
@@ -331,7 +331,7 @@ example:
 @"
 Even if you have not created a profile,
 the path of the profile file is:
-$profile.
+$PROFILE.
 "@
 ```
 

reference/5.1/Microsoft.PowerShell.Core/About/about_Script_Internationalization.md

@@ -160,7 +160,7 @@ if (!($username)) { $msgTable.promptMsg }
 ```
 
 If `Import-LocalizedData` cannot find a `.psd1` file that matches the value of
-`$PSUIculture`, the value of `$msgTable` is not replaced, and the call to
+`$PSUICulture`, the value of `$msgTable` is not replaced, and the call to
 `$msgTable.promptMsg` displays the fallback en-US strings.
 
 ## Examples

reference/5.1/Microsoft.PowerShell.Core/About/about_Scripts.md

@@ -302,12 +302,12 @@ function and the `$ProfileName` variable.
 function New-Profile
 {
   Write-Host "Running New-Profile function"
-  $profileName = Split-Path $profile -Leaf
+  $profileName = Split-Path $PROFILE -Leaf
 
-  if (Test-Path $profile)
+  if (Test-Path $PROFILE)
     {Write-Error "Profile $profileName already exists on this computer."}
   else
-    {New-Item -Type file -Path $profile -Force }
+    {New-Item -Type file -Path $PROFILE -Force }
 }
 ```
 

reference/5.1/Microsoft.PowerShell.Core/About/about_Session_Configuration_Files.md

@@ -205,7 +205,7 @@ active copy of the session configuration file.
 
 When you use a session configuration file in a session configuration,
 PowerShell creates an active copy of the session configuration file and stores
-it in the \$pshome\\SessionConfig directory on the local computer.
+it in the \$PSHOME\\SessionConfig directory on the local computer.
 
 The location of the active copy of a session configuration file is stored in
 the ConfigFilePath property of the session configuration object.

reference/5.1/Microsoft.PowerShell.Core/About/about_Splatting.md

@@ -69,7 +69,7 @@ table of parameter-name and parameter-value pairs and stores it in the
 variable in a command with splatting. The At symbol (`@HashArguments`) replaces
 the dollar sign (`$HashArguments`) in the command.
 
-To provide a value for the **WhatIf** switch parameter, use `$True` or
+To provide a value for the **WhatIf** switch parameter, use `$true` or
 `$false`.
 
 ```powershell

reference/5.1/Microsoft.PowerShell.Core/About/about_Type_Operators.md

@@ -73,7 +73,7 @@ The **Boolean** type operators (`-is` and `-isnot`) always return a **Boolean**
 value, even if the input is a collection of objects.
 
 If `<input>` is a type that is the same as or is _derived_ from the .NET Type,
-the `-is` operator returns `$True`.
+the `-is` operator returns `$true`.
 
 For example, the **DirectoryInfo** type is derived from the **FileSystemInfo**
 type. Therefore, both of these examples return **True**.

reference/5.1/Microsoft.PowerShell.Core/About/about_Updatable_Help.md

@@ -141,7 +141,7 @@ Update-Help -Module Microsoft.PowerShell.Security
 
 ## Permissions for updatable help
 
-To update help for the modules in the directory `$pshome/Modules`, you must be
+To update help for the modules in the directory `$PSHOME/Modules`, you must be
 member of the Administrators group on the computer.
 
 If you aren't a member of the Administrators group, you can't update help for