(AB-568561) [switch] parameter in conceptual docs (#12939)

Author: michaeltlombardi

reference/docs-conceptual/developer/cmdlet/background-jobs.md

@@ -23,7 +23,8 @@ For more information about how background jobs are handled at the command line,
 
 To write a cmdlet that can be run as a background job, you must complete the following tasks:
 
-- Define an `asJob` switch parameter so that the user can decide whether to run the cmdlet as a background job.
+- Define an `AsJob` `[switch]` parameter so that the user can decide whether to run the cmdlet as a
+  background job.
 
 - Create an object that derives from the [System.Management.Automation.Job](/dotnet/api/System.Management.Automation.Job) class. This object can be a custom job object or a job object provided by Windows PowerShell, such as a [System.Management.Automation.PSEventJob](/dotnet/api/System.Management.Automation.PSEventJob) object.
 

reference/docs-conceptual/developer/cmdlet/cmdlet-dynamic-parameters.md

@@ -9,7 +9,7 @@ title: Cmdlet Dynamic Parameters
 Cmdlets can define parameters that are available to the user under special conditions, such as when
 the argument of another parameter is a specific value. These parameters are added at runtime and are
 referred to as dynamic parameters because they're only added when needed. For example, you can
-design a cmdlet that adds several parameters only when a specific switch parameter is specified.
+design a cmdlet that adds several parameters only when a specific `[switch]` parameter is specified.
 
 > [!NOTE]
 > Providers and PowerShell functions can also define dynamic parameters.

reference/docs-conceptual/developer/cmdlet/cmdlet-overview.md

@@ -49,8 +49,8 @@ about this attribute, see [Cmdlet Attribute Declaration](cmdlet-attribute-declar
 ### Cmdlet parameter
 
 The public properties that define the parameters that are available to the user or to the
-application that is running the cmdlet. Cmdlets can have required, named, positional, and *switch*
-parameters. Switch parameters allow you to define parameters that are evaluated only if the
+application that is running the cmdlet. Cmdlets can have required, named, positional, and `[switch]`
+parameters. `[switch]` parameters allow you to define parameters that are evaluated only if the
 parameters are specified in the call. For more information about the different types of parameters,
 see [Cmdlet Parameters](cmdlet-parameters.md).
 

reference/docs-conceptual/developer/cmdlet/creating-a-cmdlet-to-access-a-data-store.md

@@ -145,10 +145,11 @@ public ScriptBlock Script
 ScriptBlock script;
 ```
 
-The `SimpleMatch` parameter is a switch parameter that indicates whether the cmdlet is to explicitly
-match the patterns as they are supplied. When the user specifies the parameter at the command line
-(`true`), the cmdlet uses the patterns as they are supplied. If the parameter is not specified
-(`false`), the cmdlet uses regular expressions. The default for this parameter is `false`.
+The `SimpleMatch` parameter is a `[switch]` parameter that indicates whether the cmdlet is to
+explicitly match the patterns as they are supplied. When the user specifies the parameter at the
+command line (`true`), the cmdlet uses the patterns as they are supplied. If the parameter is not
+specified (`false`), the cmdlet uses regular expressions. The default for this parameter is
+`false`.
 
 ```csharp
 [Parameter]
@@ -160,12 +161,12 @@ public SwitchParameter SimpleMatch
 private bool simpleMatch;
 ```
 
-The `CaseSensitive` parameter is a switch parameter that indicates whether a case-sensitive search
-is performed. When the user specifies the parameter at the command line (`true`), the cmdlet checks
-for the uppercase and lowercase of characters when comparing patterns. If the parameter is not
-specified (`false`), the cmdlet does not distinguish between uppercase and lowercase. For example
-"MyFile" and "myfile" would both be returned as positive hits. The default for this parameter is
-`false`.
+The `CaseSensitive` parameter is a `[switch]` parameter that indicates whether a case-sensitive
+search is performed. When the user specifies the parameter at the command line (`true`), the cmdlet
+checks for the uppercase and lowercase of characters when comparing patterns. If the parameter is
+not specified (`false`), the cmdlet does not distinguish between uppercase and lowercase. For
+example "MyFile" and "myfile" would both be returned as positive hits. The default for this
+parameter is `false`.
 
 ```csharp
 [Parameter]

reference/docs-conceptual/developer/cmdlet/how-to-declare-cmdlet-parameters.md

@@ -5,7 +5,8 @@ title: How to Declare Cmdlet Parameters
 ---
 # How to Declare Cmdlet Parameters
 
-These examples show how to declare named, positional, required, optional, and switch parameters. These examples also show how to define a parameter alias.
+These examples show how to declare named, positional, required, optional, and `[switch]`
+parameters. These examples also show how to define a parameter alias.
 
 ## How to Declare a Named Parameter
 
@@ -69,7 +70,7 @@ For more information about the Parameter attribute, see [Parameter Attribute Dec
     private string userName;
     ```
 
-## How to Declare a Switch Parameter
+## How to Declare a `[switch]` parameter
 
 - Define a public property as type [System.Management.Automation.SwitchParameter](/dotnet/api/System.Management.Automation.SwitchParameter), and then declare the Parameter attribute.
 

reference/docs-conceptual/developer/cmdlet/how-to-declare-dynamic-parameters.md

@@ -7,7 +7,7 @@ title: How to Declare Dynamic Parameters
 
 This example shows how to define dynamic parameters that are added to the cmdlet at runtime. In this
 example, the `Department` parameter is added to the cmdlet whenever the user specifies the
-`Employee` switch parameter. For more information about dynamic parameters, see
+`Employee` `[switch]` parameter. For more information about dynamic parameters, see
 [Cmdlet Dynamic Parameters][02].
 
 ## To define dynamic parameters

reference/docs-conceptual/developer/cmdlet/how-to-support-jobs.md

@@ -11,8 +11,8 @@ information about background jobs, see [Background Jobs](./background-jobs.md).
 
 ## To support jobs
 
-1. Define an `AsJob` switch parameter so that the user can decide whether to run the cmdlet as a
-   job.
+1. Define an `AsJob` `[switch]` parameter so that the user can decide whether to run the cmdlet as
+   a job.
 
     The following example shows an AsJob parameter declaration.
 

reference/docs-conceptual/developer/cmdlet/requesting-confirmation-from-cmdlets.md

@@ -48,9 +48,10 @@ additional confirmation. For these cases, supplement the
 to more finely control the scope of the **Yes to all** response to the confirmation prompt.
 
 If a cmdlet calls the [System.Management.Automation.Cmdlet.ShouldContinue][02] method, the cmdlet
-must also provide a `Force` switch parameter. If the user specifies `Force` when the user invokes
-the cmdlet, the cmdlet should still call [System.Management.Automation.Cmdlet.ShouldProcess][03],
-but it should bypass the call to [System.Management.Automation.Cmdlet.ShouldContinue][02].
+must also provide a `Force` `[switch]` parameter. If the user specifies `Force` when the user
+invokes the cmdlet, the cmdlet should still call
+[System.Management.Automation.Cmdlet.ShouldProcess][03], but it should bypass the call to
+[System.Management.Automation.Cmdlet.ShouldContinue][02].
 
 [System.Management.Automation.Cmdlet.ShouldContinue][02] will throw an exception when it's called
 from a non-interactive environment where the user can't be prompted. Adding a `Force` parameter

reference/docs-conceptual/developer/cmdlet/strongly-encouraged-development-guidelines.md

@@ -110,9 +110,9 @@ cmdlet, do not make the `Process` parameter for another cmdlet a
 
 If your parameter takes only `true` and `false`, define the parameter as type
 [System.Management.Automation.SwitchParameter](/dotnet/api/System.Management.Automation.SwitchParameter).
-A switch parameter is treated as `true` when it is specified in a command. If the parameter is not
-included in a command, Windows PowerShell considers the value of the parameter to be `false`. Do not
-define Boolean parameters.
+A `[switch]` parameter is treated as `true` when it is specified in a command. If the parameter is
+not included in a command, Windows PowerShell considers the value of the parameter to be `false`.
+Do not define Boolean parameters.
 
 If your parameter needs to differentiate between 3 values: $true, $false and "unspecified", then
 define a parameter of type Nullable\<bool>. The need for a 3rd, "unspecified" value typically occurs

reference/docs-conceptual/developer/cmdlet/types-of-cmdlet-output.md

@@ -23,9 +23,9 @@ method. We recommend that you call this method instead of the
 [System.Management.Automation.Host.PSHostUserInterface.WriteLine](/dotnet/api/System.Management.Automation.Host.PSHostUserInterface.WriteLine)
 methods.
 
-You can provide a **PassThru** switch parameter for cmdlets that do not typically return objects.
-When the **PassThru** switch parameter is specified at the command line, the cmdlet is asked to
-return an object. For an example of a cmdlet that has a **PassThru** parameter, see
+You can provide a **PassThru** `[switch]` parameter for cmdlets that do not typically return
+objects. When the **PassThru** `[switch]` parameter is specified at the command line, the cmdlet is
+asked to return an object. For an example of a cmdlet that has a **PassThru** parameter, see
 [Add-History](/powershell/module/Microsoft.PowerShell.Core/Add-History).
 
 ### Error output