Editorial changes - mostly formatting

Author: sdwheeler

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

@@ -1,7 +1,7 @@
 ---
 description: Describes variables that store state information for PowerShell. These variables are created and maintained by PowerShell.
 Locale: en-US
-ms.date: 02/10/2026
+ms.date: 04/02/2026
 no-loc: [Reset, Current, Background, Blink, Bold, Foreground, Formatting, Hidden, Italic, Reset, Reverse, Underline, PSEventArgs, PSEventSubscriber, PSEdition]
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_automatic_variables?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0

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

@@ -1,7 +1,7 @@
 ---
 description: Describes the parameters that can be used with any cmdlet.
 Locale: en-US
-ms.date: 03/29/2026
+ms.date: 04/02/2026
 no-loc: [Confirm, Debug, ErrorAction, ErrorVariable, InformationAction, InformationVariable, OutBuffer, OutVariable, PipelineVariable, ProgressAction, Verbose, WarningAction, WarningVariable, WhatIf]
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_commonparameters?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0
@@ -106,8 +106,7 @@ the display of debugging messages when `$DebugPreference` isn't
 
 Determines how the cmdlet responds to a non-terminating error from the command.
 This parameter overrides the value of the `$ErrorActionPreference` variable for
-non-terminating errors generated by the command, such as those from the
-`Write-Error` cmdlet.
+non-terminating errors generated by the command or the `Write-Error` cmdlet.
 
 ```yaml
 Type: ActionPreference

reference/7.6/Microsoft.PowerShell.Core/About/about_Error_Handling.md

@@ -1,7 +1,7 @@
 ---
 description: Variables that customize the behavior of PowerShell.
 Locale: en-US
-ms.date: 03/29/2026
+ms.date: 04/02/2026
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_preference_variables?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_Preference_Variables
@@ -399,8 +399,8 @@ The valid values are as follows:
 - **SilentlyContinue**: No effect. The error message isn't displayed and
   execution continues without interruption.
 - **Stop**: Displays the error message and stops executing. In addition to the
-  error generated, the **Stop** value generates an ActionPreferenceStopException
-  object to the error stream.
+  error generated, the **Stop** value generates an
+  ActionPreferenceStopException object to the error stream.
 - **Suspend**: Automatically suspends a workflow job to allow for further
   investigation. After investigation, the workflow can be resumed. The
   **Suspend** value is intended for per-command use, not for use as saved
@@ -410,11 +410,11 @@ The valid values are as follows:
 `$ErrorActionPreference` applies to **both** non-terminating and
 statement-terminating errors. Unlike the `-ErrorAction` parameter (which only
 affects non-terminating errors), the preference variable can also suppress or
-escalate errors generated by `$PSCmdlet.ThrowTerminatingError()`.
-When set to **Stop**, it escalates non-terminating errors to
-script-terminating errors. For more information about error categories, see
-[about_Error_Handling][67]. For more information about the **ErrorAction**
-common parameter, see [about_CommonParameters][29].
+escalate errors generated by `$PSCmdlet.ThrowTerminatingError()`. When set to
+**Stop**, it escalates non-terminating errors to script-terminating errors. For
+more information about error categories, see [about_Error_Handling][67]. For
+more information about the **ErrorAction** common parameter, see
+[about_CommonParameters][29].
 
 Many native commands write to `stderr` as an alternative stream for additional
 information. This behavior can cause confusion when looking through errors or

reference/7.6/Microsoft.PowerShell.Core/About/about_Preference_Variables.md

@@ -1,7 +1,7 @@
 ---
 description: Describes the `throw` keyword, which generates a script-terminating error by default.
 Locale: en-US
-ms.date: 03/29/2026
+ms.date: 04/02/2026
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_throw?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_Throw
@@ -10,28 +10,27 @@ title: about_Throw
 
 ## Short description
 
-Describes the `throw` keyword that generates a script-terminating error by
+Describes the `throw` keyword, which generates a script-terminating error by
 default.
 
 ## Long description
 
 The `throw` keyword causes a script-terminating error by default. You can use
 the `throw` keyword to stop the processing of a command, function, or script.
 
-Unlike statement-terminating errors (generated by
-`$PSCmdlet.ThrowTerminatingError()`), the `throw` keyword unwinds the entire
+Unlike statement-terminating errors, the `throw` keyword unwinds the entire
 call stack. Execution stops completely unless the error is caught by a
 `try/catch` block or `trap` statement.
 
 > [!NOTE]
-> `$ErrorActionPreference` can suppress `throw`. When set to
-> `SilentlyContinue` or `Ignore`, the error does not propagate and
-> execution continues at the next statement. When calling an advanced
-> function with `-ErrorAction SilentlyContinue`, the parameter translates
-> to a scope-local `$ErrorActionPreference` value, so it also suppresses
-> `throw` inside that function. Even when suppressed, `throw` still records
-> an entry in `$Error` — `Ignore` only prevents `$Error` recording for
-> non-terminating errors.
+> `$ErrorActionPreference` can suppress `throw`. When set to `SilentlyContinue`
+> or `Ignore`, the error doesn't propagate and execution continues at the next
+> statement. When calling an advanced function with
+> `-ErrorAction SilentlyContinue`, the parameter translates to a scope-local
+> `$ErrorActionPreference` value, so it also suppresses `throw` inside that
+> function. Even when suppressed, `throw` still records an entry in `$Error`.
+> The `Ignore` value only prevents `$Error` recording for non-terminating
+> errors like those generated by `$PSCmdlet.ThrowTerminatingError()`.
 
 For more information about error categories and `$ErrorActionPreference`
 behavior, see [about_Error_Handling](about_Error_Handling.md).

reference/7.6/Microsoft.PowerShell.Core/About/about_Throw.md

@@ -1,7 +1,7 @@
 ---
 description: Describes a keyword that handles statement-terminating and script-terminating errors.
 Locale: en-US
-ms.date: 03/29/2026
+ms.date: 04/02/2026
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_trap?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_Trap

reference/7.6/Microsoft.PowerShell.Core/About/about_Trap.md

@@ -1,7 +1,7 @@
 ---
 description: Describes how to use the `try`, `catch`, and `finally` blocks to handle statement-terminating and script-terminating errors.
 Locale: en-US
-ms.date: 03/29/2026
+ms.date: 04/02/2026
 online version: https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_try_catch_finally?view=powershell-7.6&WT.mc_id=ps-gethelp
 schema: 2.0.0
 title: about_Try_Catch_Finally
@@ -17,10 +17,12 @@ statement-terminating and script-terminating errors.
 
 Use `try`, `catch`, and `finally` blocks to respond to or handle terminating
 errors in scripts. PowerShell has two kinds of terminating errors:
-_statement-terminating_ errors that stop the current statement and
-_script-terminating_ errors that unwind the entire call stack. Both kinds are
-caught by `try/catch`. The `trap` statement can also be used to handle
-terminating errors. For more information, see [about_Trap][05]. For a
+
+- _statement-terminating_ errors that stop the current statement and
+- _script-terminating_ errors that unwind the entire call stack
+
+Both kinds are caught by `try/catch`. You can also use the `trap` statement to
+handle terminating errors. For more information, see [about_Trap][05]. For a
 comprehensive overview of all error types, see [about_Error_Handling][06].
 
 A statement-terminating error stops the current statement from running, but
@@ -30,10 +32,10 @@ the `throw` keyword) stops the entire script unless caught by a `try/catch`
 block or `trap` statement.
 
 > [!NOTE]
-> `$ErrorActionPreference` can suppress `throw`. When set to
-> `SilentlyContinue` or `Ignore`, the error does not propagate and
-> execution continues at the next statement. For details, see
-> [Script-terminating errors][07] in **about_Error_Handling**.
+> `$ErrorActionPreference` can suppress `throw`. When set to `SilentlyContinue`
+> or `Ignore`, the error doesn't propagate and execution continues at the next
+> statement. For details, see the _Script-terminating errors_ section of
+> [about_Error_Handling][07].
 
 Use the `try` block to define a section of a script in which you want
 PowerShell to monitor for errors. When an error occurs within the `try` block,

reference/7.6/Microsoft.PowerShell.Core/About/about_Try_Catch_Finally.md

@@ -1,7 +1,7 @@
 ---
 description: Error handling is just part of life when it comes to writing code.
 ms.custom: contributor-KevinMarquette
-ms.date: 03/29/2026
+ms.date: 04/02/2026
 title: Everything you wanted to know about exceptions
 ---
 # Everything you wanted to know about exceptions
@@ -12,9 +12,9 @@ can easily handle exceptions generated by other people's code or you can generat
 exceptions for others to handle.
 
 > [!NOTE]
-> The [original version][07] of this article appeared on the blog written by [@KevinMarquette][08].
+> The [original version][08] of this article appeared on the blog written by [@KevinMarquette][09].
 > The PowerShell team thanks Kevin for sharing this content with us. Please check out his blog at
-> [PowerShellExplained.com][05].
+> [PowerShellExplained.com][06].
 
 ## Basic terminology
 
@@ -44,16 +44,18 @@ it.
 
 ### Terminating and non-terminating errors
 
-PowerShell has three categories of errors. A _non-terminating error_ (generated
-by `Write-Error`) adds an error to the error stream without stopping execution
-and does not trigger `catch`. A _statement-terminating error_ (generated by
-`$PSCmdlet.ThrowTerminatingError()`, engine errors, or .NET method exceptions)
-stops the current statement but allows the script to continue at the next
-statement. A _script-terminating error_ (generated by `throw`, parse errors, or
-`-ErrorAction Stop` escalation) unwinds the entire call stack. Both
-statement-terminating and script-terminating errors can be caught by
-`try/catch`. For a comprehensive reference, see
-[about_Error_Handling](/powershell/module/microsoft.powershell.core/about/about_error_handling).
+PowerShell has three categories of errors.
+
+- A _non-terminating error_ adds an error to the error stream without stopping execution and doesn't
+  trigger `catch`. By default, `Write-Error` generates non-terminating errors.
+- A _statement-terminating error_ stops the current statement but allows the script to continue at
+  the next statement. Statement-terminating errors can be generated by engine errors,
+  `$PSCmdlet.ThrowTerminatingError()`, or .NET method exceptions.
+- A _script-terminating error_ unwinds the entire call stack. Script-terminating errors can be
+  generated by `throw`, parse errors, or `-ErrorAction Stop` escalation.
+
+Both statement-terminating and script-terminating errors can be caught by `try/catch`. For a
+comprehensive reference, see [about_Error_Handling][04].
 
 ### Swallowing an exception
 
@@ -111,7 +113,7 @@ Start-Something -ErrorAction Stop
 ```
 
 For more information about the **ErrorAction** parameter, see [about_CommonParameters][03]. For more
-information about the `$ErrorActionPreference` variable, see [about_Preference_Variables][04].
+information about the `$ErrorActionPreference` variable, see [about_Preference_Variables][05].
 
 ### Try/Catch
 
@@ -430,7 +432,7 @@ catch [System.IO.FileNotFoundException]
 I compiled a master list with the help of the Reddit `r/PowerShell` community that contains hundreds
 of .NET exceptions to complement this post.
 
-- [The big list of .NET exceptions][06]
+- [The big list of .NET exceptions][07]
 
 I start by searching that list for exceptions that feel like they would be a good fit for my
 situation. You should try to use exceptions in the base `System` namespace.
@@ -562,57 +564,50 @@ the users of your Cmdlet.
 
 ## How try/catch changes error propagation
 
-Inside a `try` block, PowerShell sets an internal flag that causes all
-statement-terminating errors to propagate to the `catch` block. This is by
-design, not a corner case. The following example demonstrates this behavior.
-
-Outside `try/catch`, a statement-terminating error from a child scope does not
-stop the parent scope. Here is a function that generates a divide by zero
-runtime exception.
+Inside a `try` block, PowerShell sets an internal flag that causes all statement-terminating errors
+to propagate to the `catch` block. This is by design, not a corner case. The following example
+demonstrates this behavior.
 
 ```powershell
 function Start-Something { 1/(1-1) }
 ```
 
+Outside `try/catch`, a statement-terminating error from a child scope doesn't stop the parent scope.
+Here is a function that generates a divide by zero runtime exception.
+
 Invoke it like this to see the error reported while the script continues.
 
 ```powershell
 &{ Start-Something; Write-Output "We did it. Send Email" }
 ```
 
-But placing that same code inside a `try/catch`, the error propagates to the
-`catch` block.
+But placing that same code inside a `try/catch`, the error propagates to the `catch` block.
 
 ```powershell
-try
-{
+try {
     &{ Start-Something; Write-Output "We did it. Send Email" }
-}
-catch
-{
+} catch {
     Write-Output "Notify Admin to fix error and send email"
 }
 ```
 
-The error is caught and the subsequent `Write-Output` inside the script block
-does not run. This is standard `try/catch` behavior — all terminating errors
-within the `try` block are caught, whether they originate in the current scope
-or in a child scope.
+The error is caught and the subsequent `Write-Output` inside the script block doesn't run. This is
+standard `try/catch` behavior — all terminating errors within the `try` block are caught, whether
+they originate in the current scope or in a child scope.
 
 ### $PSCmdlet.ThrowTerminatingError() inside try/catch
 
-`$PSCmdlet.ThrowTerminatingError()` creates a statement-terminating error
-within the cmdlet. After the error leaves the cmdlet, the caller treats it as a
-non-terminating error by default. The caller can escalate it back to a
-terminating error by using `-ErrorAction Stop` or calling it from within a
-`try{...}catch{...}`.
+`$PSCmdlet.ThrowTerminatingError()` creates a statement-terminating error within the cmdlet. After
+the error leaves the cmdlet, the caller treats it as a non-terminating error by default. The caller
+can escalate it back to a terminating error by using `-ErrorAction Stop` or calling it from within a
+`try/catch` block.
 
 ### Public function templates
 
-One last takeaway I had with my conversation with Kirk Munro was that he places a
-`try{...}catch{...}` around every `begin`, `process` and `end` block in all of his advanced
-functions. In those generic catch blocks, he has a single line using
-`$PSCmdlet.ThrowTerminatingError($PSItem)` to deal with all exceptions leaving his functions.
+One last takeaway I had with my conversation with Kirk Munro was that he places a `try/catch` block
+inside every `begin`, `process` and `end` block in all his advanced functions. In those generic
+catch blocks, he has a single line using `$PSCmdlet.ThrowTerminatingError($PSItem)` to deal with all
+exceptions leaving his functions.
 
 ```powershell
 function Start-Something
@@ -622,12 +617,9 @@ function Start-Something
 
     process
     {
-        try
-        {
+        try {
             ...
-        }
-        catch
-        {
+        } catch {
             $PSCmdlet.ThrowTerminatingError($PSItem)
         }
     }
@@ -677,8 +669,9 @@ advice and make `ThrowTerminatingError` my goto exception handler for every func
 [01]: /dotnet/api
 [02]: /dotnet/api/System.IO.FileNotFoundException
 [03]: /powershell/module/microsoft.powershell.core/about/about_commonparameters
-[04]: /powershell/module/microsoft.powershell.core/about/about_preference_variables
-[05]: https://powershellexplained.com/
-[06]: https://powershellexplained.com/2017-04-07-all-dotnet-exception-list
-[07]: https://powershellexplained.com/2017-04-10-Powershell-exceptions-everything-you-ever-wanted-to-know/
-[08]: https://twitter.com/KevinMarquette
+[04]: /powershell/module/microsoft.powershell.core/about/about_error_handling
+[05]: /powershell/module/microsoft.powershell.core/about/about_preference_variables
+[06]: https://powershellexplained.com/
+[07]: https://powershellexplained.com/2017-04-07-all-dotnet-exception-list
+[08]: https://powershellexplained.com/2017-04-10-Powershell-exceptions-everything-you-ever-wanted-to-know/
+[09]: https://twitter.com/KevinMarquette