Merge pull request #11840 from MicrosoftDocs/main

2/24/2025 PM Publish

Author: Taojunshen

.github/actions/.pwsh/module/functions/utility/Get-GHAConsoleError.ps1

@@ -6,7 +6,7 @@
     properties to the fully qualified ID, the type of the error, the error message, and the target
     object (which for GH CLI errors is always the command-line arguments for the failing command).
 
-    It can retrieve errors from the `$error` variable or act on an input object.
+    It can retrieve errors from the `$Error` variable or act on an input object.
 .PARAMETER Newest
     Specifies the number of error records to return, from newest to oldest.
 .PARAMETER InputObject
@@ -19,7 +19,7 @@
     The cmdlet gets the alternate view for the last error in the session.
 .EXAMPLE
     ```powershell
-    Get-GHAConsoleError -InputObject $error[0]
+    Get-GHAConsoleError -InputObject $Error[0]
     ```
 
     The cmdlet gets the alternate view for the last error in the session.

.github/actions/.pwsh/module/readme.md

@@ -78,7 +78,7 @@ This cmdlet returns an alternate view of an error record for the GH CLI. It limi
 properties to the fully qualified ID, the type of the error, the error message, and the target
 object (which for GH CLI errors is always the command-line arguments for the failing command).
 
-It can retrieve errors from the `$error` variable or act on an input object.
+It can retrieve errors from the `$Error` variable or act on an input object.
 
 For more information, review the [source code][utility-Get-GHAConsoleError]
 

reference/5.1/CimCmdlets/Register-CimIndicationEvent.md

@@ -94,12 +94,12 @@ Register-CimIndicationEvent -Query $query -SourceIdentifier "Timer"
 ### Example 3: Run a script when the event arrives
 
 This example shows how to use an action in response to an event. The variable `$action` holds the
-script block for **Action**, which uses the `$event` variable to access the event received from CIM.
+script block for **Action**, which uses the `$Event` variable to access the event received from CIM.
 
 ```powershell
 $action = {
-  $name = $event.SourceEventArgs.NewEvent.ProcessName
-  $id = $event.SourceEventArgs.NewEvent.ProcessId
+  $name = $Event.SourceEventArgs.NewEvent.ProcessName
+  $id = $Event.SourceEventArgs.NewEvent.ProcessId
   Write-Host -Object "New Process Started : Name = $name ID = $id"
 }
 $event = @{

reference/5.1/ISE/Get-IseSnippet.md

@@ -100,14 +100,14 @@ This example displays the title and description of all snippets in the session,
 snippets, user-defined snippets, and imported snippets.
 
 ```powershell
-$PSISE.CurrentPowerShellTab.Snippets | Format-Table DisplayTitle, Description
+$psISE.CurrentPowerShellTab.Snippets | Format-Table DisplayTitle, Description
 ```
 
-The `$PSISE` variable represents the Windows PowerShell ISE host program. The
-**CurrentPowerShellTab** property of the `$PSISE` variable represent the current session. The
+The `$psISE` variable represents the Windows PowerShell ISE host program. The
+**CurrentPowerShellTab** property of the `$psISE` variable represent the current session. The
 **Snippets** property represents snippets in the current session.
 
-The `$PSISE.CurrentPowerShellTab.Snippets` command returns a
+The `$psISE.CurrentPowerShellTab.Snippets` command returns a
 **Microsoft.PowerShell.Host.ISE.ISESnippet** object that represents a snippet, unlike the
 `Get-IseSnippet` cmdlet. `Get-IseSnippet` returns a file object (System.Io.FileInfo) that represents
 a snippet file.

reference/5.1/ISE/Import-IseSnippet.md

@@ -92,7 +92,7 @@ you don't need to run a command like this because modules that have snippets wil
 ```powershell
 ($env:PSModulePath).split(";") |
   ForEach-Object {dir $_\*\Snippets\*.Snippets.ps1xml -ErrorAction SilentlyContinue} |
-    ForEach-Object {$psise.CurrentPowerShellTab.Snippets.Load($_)}
+    ForEach-Object {$psISE.CurrentPowerShellTab.Snippets.Load($_)}
 ```
 
 ### Example 5: Copy all module snippets

reference/5.1/ISE/New-IseSnippet.md

@@ -244,7 +244,7 @@ For more information about Windows PowerShell execution policies, see
   Windows PowerShell ISE.
 - To delete a snippet that you added, delete the snippet file.
 - You cannot delete a built-in snippet, but you can hide all built-in snippets by using the
-  "$psise.Options.ShowDefaultSnippets=$false" command.
+  "$psISE.Options.ShowDefaultSnippets=$false" command.
 - You can create a snippet that has the same name as a built-in snippet. Both snippets appear in the
   snippet menu in Windows PowerShell ISE.
 

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

@@ -205,7 +205,7 @@ non-zero integer.
 ### `$foreach`
 
 Contains the enumerator (not the resulting values) of a [ForEach][56] loop. The
-`$ForEach` variable exists only while the `ForEach` loop is running; it's
+`$foreach` variable exists only while the `ForEach` loop is running; it's
 deleted after the loop is completed.
 
 Enumerators contain properties and methods you can use to retrieve loop values

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

@@ -202,7 +202,7 @@ You can use this parameter to create a variable that contains only error
 messages from specific commands and doesn't affect the behavior of the `$Error`
 automatic variable. The `$Error` automatic variable contains error messages
 from all the commands in the session. You can use array notation, such as
-`$a[0]` or `$error[1,2]` to refer to specific errors stored in the variables.
+`$a[0]` or `$Error[1,2]` to refer to specific errors stored in the variables.
 
 > [!NOTE]
 > The custom error variable contains all errors generated by the command,

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

@@ -46,8 +46,8 @@ is limited to the following elements:
 
 - All PowerShell operators, except `-match`
 - `If`, `Else`, and `ElseIf` statements
-- The following automatic variables: `$PsCulture`, `$PsUICulture`, `$True`,
-  `$False`, and `$Null`
+- The following automatic variables: `$PSCulture`, `$PSUICulture`, `$true`,
+  `$false`, and `$null`
 - Comments
 - Pipelines
 - Statements separated by semicolons (`;`)

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

@@ -126,8 +126,8 @@ for the following automatic variables:
 
 ```powershell
 $_
-$Args
-$Input
+$args
+$input
 $MyInvocation
 $PSBoundParameters
 ```
@@ -144,7 +144,7 @@ variable.
 For example,
 
 ```powershell
-$scriptArgs = $Args
+$scriptArgs = $args
 $scriptname = $MyInvocation.PSCommandPath
 ```