From 8c58b5f9a95260354dafd0944050fe267c40224a Mon Sep 17 00:00:00 2001 From: sethvs Date: Thu, 12 Feb 2026 01:12:10 +0300 Subject: [PATCH] Remove extra spaces --- .../learn/deep-dives/everything-about-exceptions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/docs-conceptual/learn/deep-dives/everything-about-exceptions.md b/reference/docs-conceptual/learn/deep-dives/everything-about-exceptions.md index 72103e2d13fa..17b065c9f7d1 100644 --- a/reference/docs-conceptual/learn/deep-dives/everything-about-exceptions.md +++ b/reference/docs-conceptual/learn/deep-dives/everything-about-exceptions.md @@ -599,7 +599,7 @@ terminating error by using `-ErrorAction Stop` or calling it from within a `try{ ### Public function templates -One last take a way I had with my conversation with Kirk Munro was that he places a +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.