Format PowerShell code blocks and update links.

Author: sdwheeler

reference/5.1/PSScheduledJob/New-ScheduledJobOption.md

@@ -45,7 +45,8 @@ satisfied.
 module that is included in Windows PowerShell.
 
 For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module. Import
-the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
+the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see
+[about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
 
 This cmdlet was introduced in Windows PowerShell 3.0.
 
@@ -98,7 +99,13 @@ returns to set the options for a new scheduled job.
 
 ```powershell
 $runAsAdmin = New-ScheduledJobOption -RunElevated
-Register-ScheduledJob -Name Backup -FilePath D:\Scripts\Backup.ps1 -Trigger $Mondays -ScheduledJobOption $RunAsAdmin
+$registerScheduledJobSplat = @{
+    Name = 'Backup'
+    FilePath = 'D:\Scripts\Backup.ps1'
+    Trigger = $Mondays
+    ScheduledJobOption = $RunAsAdmin
+}
+Register-ScheduledJob @registerScheduledJobSplat
 Get-ScheduledJobOption -Name Backup
 ```
 
@@ -138,7 +145,9 @@ order for easy reading.
 
 ```powershell
 $options = New-ScheduledJobOption -WakeToRun
-$options.psobject.Properties | Sort-Object -Property Name | Format-Table -Property Name, Value -AutoSize
+$options.psobject.Properties |
+    Sort-Object -Property Name | 
+    Format-Table -Property Name, Value -AutoSize
 ```
 
 ```Output
@@ -248,7 +257,7 @@ If the computer is not idle for the specified duration before the value of **Idl
 the scheduled job does not run until the next scheduled time, if any.
 
 Enter a **TimeSpan** object, such as one generated by the `New-TimeSpan` cmdlet, or enter a value in
-\<hours\>:\<minutes\>:\<seconds\> format that is automatically converted to a **TimeSpan** object.
+`<hours>:<minutes>:<seconds>` format that is automatically converted to a **TimeSpan** object.
 
 To enable this value, use the **StartIfIdle** parameter. By default, the StartIfNotIdle property of
 scheduled jobs is set to `$true` and Windows PowerShell ignores the **IdleDuration** and
@@ -274,7 +283,7 @@ parameter, the job does not run until the next scheduled time, if any. The defau
 hour.
 
 Enter a **TimeSpan** object, such as one generated by the `New-TimeSpan` cmdlet, or enter a value in
-\<hours\>:\<minutes\>:\<seconds\> format that is automatically converted to a **TimeSpan** object.
+`<hours>:<minutes>:<seconds>` format that is automatically converted to a **TimeSpan** object.
 
 To enable this value, use the **StartIfIdle** parameter. By default, the **StartIfNotIdle** property
 of scheduled jobs is set to `$true` and Windows PowerShell ignores the **IdleDuration** and
@@ -417,7 +426,8 @@ Accept wildcard characters: False
 Starts the scheduled job even if the computer is running on batteries at the scheduled start time.
 The default value is `$false`.
 
-The **StartIfOnBattery** parameter sets the value of the StartIfOnBatteries property of scheduled jobs to `$true`.
+The **StartIfOnBattery** parameter sets the value of the StartIfOnBatteries property of scheduled
+jobs to `$true`.
 
 ```yaml
 Type: System.Management.Automation.SwitchParameter
@@ -479,7 +489,8 @@ Accept wildcard characters: False
 
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
 -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose,
--WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+-WarningAction, and -WarningVariable. For more information, see
+[about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## INPUTS
 

reference/5.1/PSScheduledJob/Register-ScheduledJob.md

@@ -85,7 +85,7 @@ This example creates a scheduled job on the local computer.
 ```powershell
 Register-ScheduledJob -Name "Archive-Scripts" -ScriptBlock {
   Get-ChildItem $HOME\*.ps1 -Recurse |
-    Copy-Item -Destination "\\Server\Share\PSScriptArchive"
+  Copy-Item -Destination "\\Server\Share\PSScriptArchive"
 }
 ```
 
@@ -141,7 +141,13 @@ $O = @{
   StartIfNotIdle=$false
   MultipleInstancePolicy="Queue"
 }
-Register-ScheduledJob -Trigger $T -ScheduledJobOption $O -Name UpdateVersion -FilePath "\\Srv01\Scripts\Update-Version.ps1"
+$registerScheduledJobSplat = @{
+    Trigger = $T
+    ScheduledJobOption = $O
+    Name = 'UpdateVersion'
+    FilePath = "\\Srv01\Scripts\Update-Version.ps1"
+}
+Register-ScheduledJob @registerScheduledJobSplat
 ```
 
 ### Example 4: Create scheduled jobs on remote computers

reference/5.1/PSScheduledJob/Remove-JobTrigger.md

@@ -48,7 +48,8 @@ job triggers to delete. By default, `Remove-JobTrigger` deletes all job triggers
 that is included in Windows PowerShell.
 
 For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module. Import
-the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
+the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see
+[about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
 
 This cmdlet was introduced in Windows PowerShell 3.0.
 
@@ -73,9 +74,11 @@ This command deletes only the third trigger (ID = 3) from the BackupArchive sche
 ### Example 3: Delete AtStartup job triggers from all scheduled jobs
 
 ```powershell
-function Delete-AtStartup
-{
-    Get-ScheduledJob | Get-JobTrigger | Where-Object {$_.Frequency -eq "AtStartup"} | ForEach-Object { Remove-JobTrigger -InputObject $_.JobDefinition -TriggerId $_.Id}
+function Delete-AtStartup {
+    Get-ScheduledJob |
+        Get-JobTrigger |
+        Where-Object {$_.Frequency -eq "AtStartup"} |
+        ForEach-Object { Remove-JobTrigger -InputObject $_.JobDefinition -TriggerId $_.Id}
 }
 ```
 
@@ -194,7 +197,8 @@ Accept wildcard characters: False
 
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
 -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose,
--WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+-WarningAction, and -WarningVariable. For more information, see
+[about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## INPUTS
 

reference/5.1/PSScheduledJob/Set-JobTrigger.md

@@ -106,7 +106,8 @@ Id         Frequency       Time                   DaysOfWeek              Enable
 ```
 
 ```powershell
-Get-JobTrigger -Name "Inventory" -TriggerId 2 | Set-JobTrigger -Weekly -WeeksInterval 4 -DaysOfWeek Monday -At "12:00 AM"
+Get-JobTrigger -Name "Inventory" -TriggerId 2 |
+    Set-JobTrigger -Weekly -WeeksInterval 4 -DaysOfWeek Monday -At "12:00 AM"
 ```
 
 ```Output
@@ -131,7 +132,12 @@ This command is not required; it is included only to show the effect of the trig
 ### Example 3: Change the user on a remote job trigger
 
 ```powershell
-Invoke-Command -ComputerName "Server01" -ScriptBlock {Get-ScheduledJob | Get-JobTrigger | Where-Object {$_.User} | Set-JobTrigger -User "Domain01/Admin02"}
+Invoke-Command -ComputerName "Server01" -ScriptBlock {
+    Get-ScheduledJob |
+        Get-JobTrigger |
+        Where-Object {$_.User} |
+        Set-JobTrigger -User "Domain01/Admin02"
+}
 ```
 
 This command changes the user in all **AtLogon** job triggers of scheduled jobs on the Server01
@@ -181,8 +187,10 @@ JobDefinition      : Microsoft.PowerShell.ScheduledJob.ScheduledJobDefinition
 ```
 
 ```powershell
-Get-JobTrigger -Name "SecurityCheck" -TriggerId 3 | Set-JobTrigger -RepetitionInterval (New-TimeSpan -Minutes 90)
-Get-JobTrigger -Name "SecurityCheck" -TriggerId 3 | Format-List -Property *
+Get-JobTrigger -Name "SecurityCheck" -TriggerId 3 |
+    Set-JobTrigger -RepetitionInterval (New-TimeSpan -Minutes 90)
+Get-JobTrigger -Name "SecurityCheck" -TriggerId 3 |
+    Format-List -Property *
 ```
 
 ```Output

reference/5.1/PSScheduledJob/Set-ScheduledJob.md

@@ -67,7 +67,8 @@ as a template for other jobs.
 that is included in Windows PowerShell.
 
 For more information about Scheduled Jobs, see the About topics in the PSScheduledJob module. Import
-the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
+the PSScheduledJob module and then type: `Get-Help about_Scheduled*` or see
+[about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
 
 This cmdlet was introduced in Windows PowerShell 3.0.
 
@@ -88,7 +89,8 @@ Id         Name            Triggers        Command
 ```
 
 ```powershell
-Get-ScheduledJob -Name "Inventory" | Set-ScheduledJob -FilePath "C:\Scripts\Get-FullInventory.ps1" -PassThru
+Get-ScheduledJob -Name "Inventory" |
+    Set-ScheduledJob -FilePath "C:\Scripts\Get-FullInventory.ps1" -PassThru
 ```
 
 ```Output
@@ -120,7 +122,8 @@ operator (`|`) sends the job to the `Set-ScheduledJob` cmdlet to change it. The
 cmdlet uses the **ClearExecutionHistory** parameter to delete the execution history and saved
 results.
 
-For more information about the execution history and saved job results of scheduled jobs, see [about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
+For more information about the execution history and saved job results of scheduled jobs, see
+[about_Scheduled_Jobs](About/about_Scheduled_Jobs.md).
 
 ### Example 3: Change scheduled jobs on a remote computer
 
@@ -170,7 +173,8 @@ for this parameter are:
 - `Negotiate`
 - `NegotiateWithImplicitCredential`
 
-The default value is `Default`. For more information about the values of this parameter, see [AuthenticationMechanism Enumeration](/dotnet/api/system.management.automation.runspaces.authenticationmechanism)
+The default value is `Default`. For more information about the values of this parameter, see
+[AuthenticationMechanism Enumeration](/dotnet/api/system.management.automation.runspaces.authenticationmechanism)
 in the PowerShell SDK.
 
 > [!CAUTION]
@@ -518,7 +522,8 @@ Accept wildcard characters: False
 
 This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
 -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose,
--WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
+-WarningAction, and -WarningVariable. For more information, see
+[about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## INPUTS
 

reference/5.1/PSWorkflow/About/about_ActivityCommonParameters.md

@@ -72,8 +72,7 @@ For example, the following commands add a process object to the service object
 in the `$x` variable.
 
 ```powershell
-workflow Test-Workflow
-{
+workflow Test-Workflow {
     $x = Get-Service
     $x = Get-Process -AppendOutput $true
 }
@@ -84,8 +83,7 @@ can also use the `+=` assignment operator to add output to the value of a
 variable, as shown in the following example.
 
 ```powershell
-workflow Test-Workflow
-{
+workflow Test-Workflow {
     $x = Get-Service
     $x += Get-Process
 }
@@ -334,8 +332,7 @@ in a variable. Then, use the variable as the value of the **PSDebug** parameter
 of one or more activities, as shown in the following example.
 
 ```powershell
-workflow Test-Workflow
-{
+workflow Test-Workflow {
     $debugCollection = New-Object -Type `
     System.Management.Automation.PSDataCollection[System.Management.Automation.DebugRecord]
     inlinescript {\Server01\Share01\Get-AssetData.ps1} -PSDebug $debugCollection -Debug $true
@@ -380,15 +377,13 @@ in a variable. Then, use the variable as the value of the **PSError** parameter
 of one or more activities, as shown in the following example.
 
 ```powershell
-workflow Test-Workflow
-{
+workflow Test-Workflow {
    $typeName = "System.Management.Automation.PSDataCollection"
    $typeName += '[System.Management.Automation.ErrorRecord]'
    $ec = New-Object $typeName
    inlinescript {\Server01\Share01\Get-AssetData.ps1} -PSError $ec
    inlinescript {\Server01\Share01\Set-AssetData.ps1} -PSError $ec
-   if ($ec.Count -gt 2)
-   {
+   if ($ec.Count -gt 2) {
       # Do Some Work.
    }
 }
@@ -537,8 +532,7 @@ the workflow. When you run the workflow with input, that input is used by the
 activity.
 
 ```powershell
-workflow Test-Workflow
-{
+workflow Test-Workflow {
     Get-Service -UseDefaultInput $true
 }
 
@@ -600,25 +594,17 @@ parameters to run a `Get-EventLog` activity only on computers it a particular
 domain.
 
 ```powershell
-workflow Test-Workflow
-{
+workflow Test-Workflow {
     $UserDomain = Get-Content -Path '.\UserComputers.txt'
     $Log = (Get-EventLog -LogName "Windows PowerShell" `
       -PSComputerName $UserDomain)
 
-    if ($Log)
-    {
+    if ($Log) {
         # Do Work Here.
     }
 }
 ```
 
-<!--
-# KEYWORDS
-[about_Activity_Common_Parameters](about_Activity_Common_Parameters.md)
-[about_Activity_Parameters](about_Activity_Parameters.md)
-[about_ActivityParameters]()about_ActivityParameters.md) -->
-
 ## See Also
 
 - [about_Workflows](about_workflows.md)

reference/5.1/PSWorkflow/About/about_Checkpoint-Workflow.md

@@ -23,8 +23,7 @@ The Checkpoint-Workflow activity is valid only in a workflow.
 ### SYNTAX
 
 ```
-workflow <Verb-Noun>
-{
+workflow <Verb-Noun> {
     Checkpoint-Workflow
 }
 ```
@@ -72,14 +71,12 @@ The following workflow includes a call to the Checkpoint-Workflow activity after
 long-running function and a script that share data.
 
 ```powershell
-workflow Test-Workflow
-{
+workflow Test-Workflow {
     $a = Invoke-LongRunningFunction
     inlinescript { \\Server\Share\Get-DataPacks.ps1 $Using:a}
     Checkpoint-Workflow
 
-    Invoke-LongRunningFunction
-    {
+    Invoke-LongRunningFunction {
         ...
     }
 }

reference/5.1/PSWorkflow/About/about_Foreach-Parallel.md

@@ -26,8 +26,7 @@ each item in the collection.
 ### SYNTAX
 
 ```
-foreach -Parallel ($<item> in $<collection>)
-{
+foreach -Parallel ($<item> in $<collection>) {
     [<Activity1>]
     [<Activity2>]
     ...
@@ -59,8 +58,7 @@ the disks that the `Get-Disk` activity gets. The commands in the
 parallel. The disks might be processed concurrently and in any order.
 
 ```powershell
-workflow Test-Workflow
-{
+workflow Test-Workflow {
     $Disks = Get-Disk
 
     # The disks are processed in parallel.
@@ -81,8 +79,7 @@ parallel. The parallel commands and the `foreach -Parallel` loop run
 concurrently.
 
 ```powershell
-workflow Test-Workflow
-{
+workflow Test-Workflow {
     #Run commands in parallel.
     parallel
     {

reference/5.1/PSWorkflow/About/about_InlineScript.md

@@ -136,8 +136,7 @@ in PowerShell but aren't valid in workflows. For example, the `New-Object`
 cmdlet with the **ComObject** parameter.
 
 ```powershell
-workflow Test-Workflow
-{
+workflow Test-Workflow {
   $ie = inlinescript {
     $ie = New-Object -ComObject InternetExplorer.Application -Property @{navigate2="www.microsoft.com"}
 

reference/5.1/PSWorkflow/About/about_Parallel.md

@@ -18,10 +18,8 @@ The `parallel` keyword runs workflow activities in parallel. This keyword is val
 ### SYNTAX
 
 ```
-workflow <Verb-Noun>
-{
-     parallel
-     {
+workflow <Verb-Noun> {
+     parallel {
           [<Activity>]
           [<Activity>]
         ...
@@ -36,10 +34,8 @@ The commands in a `parallel` script block can run concurrently. The order in whi
 For example, the following workflow includes a `parallel` script block that runs activities that get processes and services on the computer. Because the Get-Process and Get-Service commands are independent of each other, they can run concurrently and in any order.
 
 ```powershell
-workflow Test-Workflow
-{
-    parallel
-    {
+workflow Test-Workflow {
+    parallel {
          Get-Process
          Get-Service
     }