Extend error handling accuracy to about_Throw, about_Try_Catch_Finally

- about_Throw: Add $ErrorActionPreference suppression caveat (throw CAN
  be suppressed by SilentlyContinue/Ignore), add NOTE block with Ignore
  still recording in $Error, update description to "by default"
- about_Try_Catch_Finally: Add NOTE about throw suppression with cross-ref
  to about_Error_Handling, fix $tempPath -> $tempFile code bug (line 264)
- about_Preference_Variables: Fix Ignore bullet - clarify that Ignore only
  prevents $Error recording for non-terminating errors, not terminating
- everything-about-exceptions: Change -ErrorAction Stop from
  "script-terminating" to "terminating" (context-dependent behavior)

All claims verified against live PowerShell 7.6 behavior.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: 2 people

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

@@ -391,7 +391,9 @@ The valid values are as follows:
   command. Unlike **SilentlyContinue**, **Ignore** doesn't add the error
   message to the `$Error` automatic variable. The **Ignore** value is also
   valid for `$ErrorActionPreference`, where it suppresses both non-terminating
-  and statement-terminating errors without recording them in `$Error`.
+  and statement-terminating errors. However, **Ignore** only prevents `$Error`
+  recording for non-terminating errors. Terminating errors that are suppressed
+  by `Ignore` are still recorded in `$Error`.
 - **Inquire**: Displays the error message and asks you whether you want to
   continue.
 - **SilentlyContinue**: No effect. The error message isn't displayed and

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

@@ -1,7 +1,7 @@
 ---
-description: Describes the `throw` keyword, which generates a script-terminating error.
+description: Describes the `throw` keyword, which generates a script-terminating error by default.
 Locale: en-US
-ms.date: 01/18/2026
+ms.date: 03/29/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,18 +10,31 @@ title: about_Throw
 
 ## Short description
 
-Describes the `throw` keyword that generates a script-terminating error.
+Describes the `throw` keyword that generates a script-terminating error by
+default.
 
 ## Long description
 
-The `throw` keyword causes a script-terminating error. You can use the `throw`
-keyword to stop the processing of a command, function, or script.
+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
 call stack. Execution stops completely unless the error is caught by a
-`try/catch` block or `trap` statement. For more information about error
-categories, see [about_Error_Handling](about_Error_Handling.md).
+`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.
+
+For more information about error categories and `$ErrorActionPreference`
+behavior, see [about_Error_Handling](about_Error_Handling.md).
 
 For example, you can use the `throw` keyword in the statement block of an `if`
 statement to respond to a condition or in the `catch` block of a

reference/7.6/Microsoft.PowerShell.Core/About/about_Try_Catch_Finally.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: 01/13/2026
+ms.date: 03/29/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
@@ -27,8 +27,13 @@ A statement-terminating error stops the current statement from running, but
 PowerShell continues at the next statement unless the error is also
 script-terminating. A script-terminating error (such as an error produced by
 the `throw` keyword) stops the entire script unless caught by a `try/catch`
-block or `trap` statement. In other languages, such as C\#, terminating errors
-are referred to as exceptions.
+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 the
+> [_throw_ suppression section][07] in **about_Error_Handling**.
 
 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,
@@ -261,7 +266,7 @@ try {
     "An error occurred that could not be resolved."
 } finally {
     $wc.Dispose()
-    if (Test-Path $tempPath) { Remove-Item $tempFile }
+    if (Test-Path $tempFile) { Remove-Item $tempFile }
 }
 ```
 
@@ -281,3 +286,4 @@ try {
 [04]: about_Throw.md
 [05]: about_Trap.md
 [06]: about_Error_Handling.md
+[07]: about_Error_Handling.md#script-terminating-errors

reference/docs-conceptual/learn/deep-dives/everything-about-exceptions.md

@@ -92,7 +92,7 @@ At line:1 char:1
 #### Write-Error -ErrorAction Stop
 
 I mentioned that `Write-Error` doesn't throw a terminating error by default. If you specify
-`-ErrorAction Stop`, `Write-Error` generates a script-terminating error that can be handled with a
+`-ErrorAction Stop`, `Write-Error` generates a terminating error that can be handled with a
 `catch`.
 
 ```powershell
@@ -104,7 +104,7 @@ Thank you to Lee Dailey for reminding about using `-ErrorAction Stop` this way.
 #### Cmdlet -ErrorAction Stop
 
 If you specify `-ErrorAction Stop` on any advanced function or cmdlet, it turns all `Write-Error`
-statements into script-terminating errors that stop execution or that can be handled by a `catch`.
+statements into terminating errors that stop execution or that can be handled by a `catch`.
 
 ```powershell
 Start-Something -ErrorAction Stop