Fix automatic variable case (#11837)

surfingoldelephant · web-flow · commit 744ca8ef3938 · 2025-02-24T13:49:32.000-06:00
diff --git a/reference/5.1/ISE/Get-IseSnippet.md b/reference/5.1/ISE/Get-IseSnippet.md
@@ -100,14 +100,14 @@ This example displays the title and description of all snippets in the session,
 snippets, user-defined snippets, and imported snippets.
 
 ```powershell
-$PSISE.CurrentPowerShellTab.Snippets | Format-Table DisplayTitle, Description
+$psISE.CurrentPowerShellTab.Snippets | Format-Table DisplayTitle, Description
 ```
 
-The `$PSISE` variable represents the Windows PowerShell ISE host program. The
-**CurrentPowerShellTab** property of the `$PSISE` variable represent the current session. The
+The `$psISE` variable represents the Windows PowerShell ISE host program. The
+**CurrentPowerShellTab** property of the `$psISE` variable represent the current session. The
 **Snippets** property represents snippets in the current session.
 
-The `$PSISE.CurrentPowerShellTab.Snippets` command returns a
+The `$psISE.CurrentPowerShellTab.Snippets` command returns a
 **Microsoft.PowerShell.Host.ISE.ISESnippet** object that represents a snippet, unlike the
 `Get-IseSnippet` cmdlet. `Get-IseSnippet` returns a file object (System.Io.FileInfo) that represents
 a snippet file.
diff --git a/reference/5.1/ISE/Import-IseSnippet.md b/reference/5.1/ISE/Import-IseSnippet.md
@@ -92,7 +92,7 @@ you don't need to run a command like this because modules that have snippets wil
 ```powershell
 ($env:PSModulePath).split(";") |
   ForEach-Object {dir $_\*\Snippets\*.Snippets.ps1xml -ErrorAction SilentlyContinue} |
-    ForEach-Object {$psise.CurrentPowerShellTab.Snippets.Load($_)}
+    ForEach-Object {$psISE.CurrentPowerShellTab.Snippets.Load($_)}
 ```
 
 ### Example 5: Copy all module snippets
diff --git a/reference/5.1/ISE/New-IseSnippet.md b/reference/5.1/ISE/New-IseSnippet.md
@@ -244,7 +244,7 @@ For more information about Windows PowerShell execution policies, see
   Windows PowerShell ISE.
 - To delete a snippet that you added, delete the snippet file.
 - You cannot delete a built-in snippet, but you can hide all built-in snippets by using the
-  "$psise.Options.ShowDefaultSnippets=$false" command.
+  "$psISE.Options.ShowDefaultSnippets=$false" command.
 - You can create a snippet that has the same name as a built-in snippet. Both snippets appear in the
   snippet menu in Windows PowerShell ISE.
 
diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_Eventlogs.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_Eventlogs.md
@@ -165,7 +165,7 @@ following command sequence.
 
 ```powershell
 $m = Get-PSSnapin Microsoft.PowerShell.Core
-$m.LogPipelineExecutionDetails = $True
+$m.LogPipelineExecutionDetails = $true
 ```
 
 To disable logging, use the same command sequence to set the property value to
diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_Format.ps1xml.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_Format.ps1xml.md
@@ -149,7 +149,7 @@ The next command copies the file contents to a new file,
 `MyDotNetTypes.Format.ps1xml`.
 
 ```powershell
-Copy-Item $PSHome\DotNetTypes.format.ps1xml MyDotNetTypes.Format.ps1xml
+Copy-Item $PSHOME\DotNetTypes.format.ps1xml MyDotNetTypes.Format.ps1xml
 ```
 
 Open the `MyDotNetTypes.Format.ps1xml` file in any XML or text editor, such as
@@ -451,7 +451,7 @@ $Parms = @{
   Pattern = "System.IO.DirectoryInfo"
 }
 Select-String @Parms
-Copy-Item $PSHome\FileSystem.format.ps1xml .\MyFileSystem.Format.ps1xml
+Copy-Item $PSHOME\FileSystem.format.ps1xml .\MyFileSystem.Format.ps1xml
 Update-FormatData -PrependPath $PSHOME\Format\MyFileSystem.Format.ps1xml
 ```
 
diff --git a/reference/5.1/Microsoft.PowerShell.Core/About/about_Preference_Variables.md b/reference/5.1/Microsoft.PowerShell.Core/About/about_Preference_Variables.md
@@ -34,10 +34,10 @@ The following table lists the preference variables and their default values.
 | [`$InformationPreference`][07]         | [`SilentlyContinue`][54]                                         |
 | [`$LogCommandHealthEvent`][08]         | `$false` (not logged)                                            |
 | [`$LogCommandLifecycleEvent`][08]      | `$false` (not logged)                                            |
-| [`$LogEngineHealthEvent`][08]          | `$True` (logged)                                                 |
-| [`$LogEngineLifecycleEvent`][08]       | `$True` (logged)                                                 |
-| [`$LogProviderLifecycleEvent`][08]     | `$True` (logged)                                                 |
-| [`$LogProviderHealthEvent`][08]        | `$True` (logged)                                                 |
+| [`$LogEngineHealthEvent`][08]          | `$true` (logged)                                                 |
+| [`$LogEngineLifecycleEvent`][08]       | `$true` (logged)                                                 |
+| [`$LogProviderLifecycleEvent`][08]     | `$true` (logged)                                                 |
+| [`$LogProviderHealthEvent`][08]        | `$true` (logged)                                                 |
 | [`$MaximumAliasCount`][09]             | `4096`                                                           |
 | [`$MaximumDriveCount`][10]             | `4096`                                                           |
 | [`$MaximumErrorCount`][11]             | `256`                                                            |
@@ -48,12 +48,12 @@ The following table lists the preference variables and their default values.
 | [`$OutputEncoding`][16]                | [`ASCIIEncoding`][60] object                                     |
 | [`$ProgressPreference`][17]            | [`Continue`][54]                                                 |
 | [`$PSDefaultParameterValues`][18]      | `@{}` (empty hash table)                                         |
-| [`$PSEmailServer`][19]                 | `$Null` (none)                                                   |
+| [`$PSEmailServer`][19]                 | `$null` (none)                                                   |
 | [`$PSModuleAutoLoadingPreference`][20] | `All`                                                            |
 | [`$PSSessionApplicationName`][21]      | `'wsman'`                                                        |
 | [`$PSSessionConfigurationName`][22]    | `'http://schemas.microsoft.com/powershell/Microsoft.PowerShell'` |
 | [`$PSSessionOption`][23]               | [`PSSessionOption`][59] object                                   |
-| [`$Transcript`][24]                    | `$Null` (none)                                                   |
+| [`$Transcript`][24]                    | `$null` (none)                                                   |
 | [`$VerbosePreference`][25]             | [`SilentlyContinue`][54]                                         |
 | [`$WarningPreference`][26]             | [`Continue`][54]                                                 |
 | [`$WhatIfPreference`][27]              | `$false`                                                         |
diff --git a/reference/5.1/Microsoft.PowerShell.Core/Export-Console.md b/reference/5.1/Microsoft.PowerShell.Core/Export-Console.md
@@ -36,11 +36,11 @@ For more information about Windows PowerShell snap-ins, see [about_PSSnapins](Ab
 ### Example 1: Export the names of snap-ins in the current session
 
 ```
-PS C:\> Export-Console -Path $pshome\Consoles\ConsoleS1.psc1
+PS C:\> Export-Console -Path $PSHOME\Consoles\ConsoleS1.psc1
 ```
 
 This command exports the names of Windows PowerShell snap-ins in the current session to the
-`ConsoleS1.psc1` file in the Consoles folder of the Windows PowerShell installation folder, `$pshome`.
+`ConsoleS1.psc1` file in the Consoles folder of the Windows PowerShell installation folder, `$PSHOME`.
 
 ### Example 2: Export the names of snap-ins to the most recent console file
 
diff --git a/reference/5.1/Microsoft.PowerShell.Management/Test-ComputerSecureChannel.md b/reference/5.1/Microsoft.PowerShell.Management/Test-ComputerSecureChannel.md
@@ -27,7 +27,7 @@ The `Test-ComputerSecureChannel` cmdlet verifies that the channel between the lo
 domain is working correctly by checking the status of its trust relationships. If a connection
 fails, you can use the **Repair** parameter to try to restore it.
 
-`Test-ComputerSecureChannel` returns $True if the channel is working correctly and $false if it is
+`Test-ComputerSecureChannel` returns $true if the channel is working correctly and $false if it is
 not. This result lets you use the cmdlet in conditional statements in functions and scripts. To get
 more detailed test results, use the **Verbose** parameter.
 
@@ -200,7 +200,7 @@ You cannot pipe input to this cmdlet.
 
 ### System.Boolean
 
-This cmdlet returns `$True` if the connection is working correctly and `$false` if it is not.
+This cmdlet returns `$true` if the connection is working correctly and `$false` if it is not.
 
 ## NOTES
 
diff --git a/reference/5.1/Microsoft.PowerShell.Utility/Get-Host.md b/reference/5.1/Microsoft.PowerShell.Utility/Get-Host.md
@@ -225,7 +225,7 @@ interchangeably.
 
 This command uses the **PrivateData** property of `$Host` as its ErrorBackgroundColor property. To
 see all of the properties of the object in the `$Host`.PrivateData property, type
-`$host.PrivateData | format-list *`.
+`$Host.PrivateData | format-list *`.
 
 ## PARAMETERS
 
diff --git a/reference/5.1/Microsoft.PowerShell.Utility/Invoke-RestMethod.md b/reference/5.1/Microsoft.PowerShell.Utility/Invoke-RestMethod.md
@@ -84,7 +84,7 @@ $Cred = Get-Credential
 
 # Next, allow the use of self-signed SSL certificates.
 
-[System.Net.ServicePointManager]::ServerCertificateValidationCallback = { $True }
+[System.Net.ServicePointManager]::ServerCertificateValidationCallback = { $true }
 
 # Create variables to store the values consumed by the Invoke-RestMethod command.
 # The search variable contents are later embedded in the body variable.
diff --git a/reference/5.1/Microsoft.PowerShell.Utility/Update-FormatData.md b/reference/5.1/Microsoft.PowerShell.Utility/Update-FormatData.md
@@ -32,7 +32,7 @@ Formatting files are text files in XML format with the `format.ps1xml` file name
 formatting data in the files defines the display of Microsoft .NET Framework objects in the session.
 
 When Windows PowerShell starts, it loads the format data from the formatting files in the PowerShell
-installation directory (`$pshome`) into the session. You can use `Update-FormatData` to reload the
+installation directory (`$PSHOME`) into the session. You can use `Update-FormatData` to reload the
 formatting data into the current session without restarting PowerShell. This is useful when you have
 added or changed a formatting file, but do not want to interrupt the session.
 
diff --git a/reference/5.1/PSDiagnostics/Set-LogProperties.md b/reference/5.1/PSDiagnostics/Set-LogProperties.md
@@ -32,7 +32,7 @@ You must run this cmdlet from an elevated PowerShell session.
 
 ```powershell
 $logDetails = Get-LogProperties 'Windows PowerShell'
-$logDetails.Retention = $True
+$logDetails.Retention = $true
 Set-LogProperties -LogDetails $logDetails
 Get-LogProperties 'Windows PowerShell'
 ```
diff --git a/reference/5.1/PSReadLine/About/about_PSReadLine.md b/reference/5.1/PSReadLine/About/about_PSReadLine.md
@@ -124,7 +124,7 @@ APIs are documented in [about_PSReadLine_Functions][02].
 
 PSReadLine maintains a history file containing all the commands and data you've
 entered from the command line. The history files are a file named
-`$($host.Name)_history.txt`. On Windows systems the history file is stored at
+`$($Host.Name)_history.txt`. On Windows systems the history file is stored at
 `$env:APPDATA\Microsoft\Windows\PowerShell\PSReadLine`.
 
 The history can contain sensitive data including passwords. PSReadLine attempts
diff --git a/reference/5.1/PSReadLine/Set-PSReadLineOption.md b/reference/5.1/PSReadLine/Set-PSReadLineOption.md
@@ -208,7 +208,7 @@ For example, the following example creates a prompt that contains the current pa
 greater-than character (`>`) and a space.
 
 ```powershell
-function prompt { "PS $pwd> " }`
+function prompt { "PS $PWD> " }`
 Set-PSReadLineOption -PromptText '> ' # change the '>' character red
 Set-PSReadLineOption -PromptText '> ', 'X ' # replace the '>' character with a red 'X'
 ```
diff --git a/reference/5.1/PSScheduledJob/Disable-JobTrigger.md b/reference/5.1/PSScheduledJob/Disable-JobTrigger.md
@@ -30,7 +30,7 @@ triggers to `Disable-JobTrigger` or use its **InputObject** parameter.
 
 To disable a job trigger, the `Disable-JobTrigger` cmdlet sets the Enabled property of the job
 trigger to `$false`. To re-enable the job trigger, use the `Enable-JobTrigger` cmdlet, which sets
-the **Enabled** property of the job trigger to $True. Disabling a job trigger does not disable the
+the **Enabled** property of the job trigger to $true. Disabling a job trigger does not disable the
 scheduled job, such as is done by the `Disable-ScheduledJob` cmdlet, but if you disable all job
 triggers, the effect is the same as disabling the scheduled job.
 
diff --git a/reference/5.1/PSScheduledJob/Get-ScheduledJobOption.md b/reference/5.1/PSScheduledJob/Get-ScheduledJobOption.md
@@ -87,7 +87,7 @@ Get-ScheduledJob | Get-ScheduledJobOption | Where {$_.RunElevated -and !$_.Waket
     ForEach-Object {$_.JobDefinition}
 ```
 
-The first command gets job options in which the RunElevated property has a value of $True and the
+The first command gets job options in which the RunElevated property has a value of $true and the
 **RunWithoutNetwork** property has a value of `$false`. The output shows the **JobOptions** object
 that was selected.
 
diff --git a/reference/5.1/PSScheduledJob/New-ScheduledJobOption.md b/reference/5.1/PSScheduledJob/New-ScheduledJobOption.md
@@ -500,7 +500,7 @@ This cmdlet returns a **ScheduledJobOptions** object representing the created op
   **ScheduledJobOption** parameter can also take a hash table value that specifies the properties of
   the **ScheduledJobOptions** object and their values, such as:
 
-  `@{ShowInTaskScheduler=$false; RunElevated=$True; IdleDuration="00:05"}`
+  `@{ShowInTaskScheduler=$false; RunElevated=$true; IdleDuration="00:05"}`
 
 ## RELATED LINKS
 
diff --git a/reference/5.1/PSScheduledJob/Register-ScheduledJob.md b/reference/5.1/PSScheduledJob/Register-ScheduledJob.md
@@ -464,7 +464,7 @@ options, including the default values, see `New-ScheduledJobOption`.
 To submit a hash table, use the following keys. In the following hash table, the keys are shown with
 their default values.
 
-`@{StartIfOnBattery=$false; StopIfGoingOnBattery=$True; WakeToRun=$false; StartIfNotIdle=$false; IdleDuration="00:10:00"; IdleTimeout="01:00:00"; StopIfGoingOffIdle=$True; RestartOnIdleResume=$false; ShowInTaskScheduler=$True; RunElevated=$false; RunWithoutNetwork=$false; DoNotAllowDemandStart=$false; MultipleInstancePolicy="IgnoreNew"}`
+`@{StartIfOnBattery=$false; StopIfGoingOnBattery=$true; WakeToRun=$false; StartIfNotIdle=$false; IdleDuration="00:10:00"; IdleTimeout="01:00:00"; StopIfGoingOffIdle=$true; RestartOnIdleResume=$false; ShowInTaskScheduler=$true; RunElevated=$false; RunWithoutNetwork=$false; DoNotAllowDemandStart=$false; MultipleInstancePolicy="IgnoreNew"}`
 
 ```yaml
 Type: Microsoft.PowerShell.ScheduledJob.ScheduledJobOptions
diff --git a/reference/5.1/PSScheduledJob/Set-ScheduledJob.md b/reference/5.1/PSScheduledJob/Set-ScheduledJob.md
@@ -443,7 +443,7 @@ options, including the default values, see `New-ScheduledJobOption`.
 To submit a hash table, use the following keys.
 In the following hash table, the keys are shown with their default values.
 
-`@{# Power SettingsStartIfOnBattery=$false;StopIfGoingOnBattery=$True; WakeToRun=$false; # Idle SettingsStartIfNotIdle=$false; IdleDuration="00:10:00"; IdleTimeout="01:00:00"; StopIfGoingOffIdle=$True; RestartOnIdleResume=$false;# Security settingsShowInTaskScheduler=$TrueRunElevated=$false;# MiscRunWithoutNetwork=$false;DoNotAllowDemandStart=$false;MultipleInstancePolicy=IgnoreNew# Can be IgnoreNew, Parallel, Queue, StopExisting}`
+`@{# Power SettingsStartIfOnBattery=$false;StopIfGoingOnBattery=$true; WakeToRun=$false; # Idle SettingsStartIfNotIdle=$false; IdleDuration="00:10:00"; IdleTimeout="01:00:00"; StopIfGoingOffIdle=$true; RestartOnIdleResume=$false;# Security settingsShowInTaskScheduler=$trueRunElevated=$false;# MiscRunWithoutNetwork=$false;DoNotAllowDemandStart=$false;MultipleInstancePolicy=IgnoreNew# Can be IgnoreNew, Parallel, Queue, StopExisting}`
 
 ```yaml
 Type: Microsoft.PowerShell.ScheduledJob.ScheduledJobOptions
diff --git a/reference/5.1/PSScheduledJob/Set-ScheduledJobOption.md b/reference/5.1/PSScheduledJob/Set-ScheduledJobOption.md
@@ -103,7 +103,7 @@ DeployPackage scheduled job. The output shows that the WakeToRun and RunElevated
 to `$false`.
 
 The second command uses the `Set-ScheduledJobOpton` cmdlet to change the job options so the values
-of the WakeToRun and RunWithoutNetwork properties are $True. The command uses the **PassThru**
+of the WakeToRun and RunWithoutNetwork properties are $true. The command uses the **PassThru**
 parameter to return the trigger after the change.
 
 This command is not required; it is included only to show the effect of the option change.
@@ -236,7 +236,7 @@ Enter a timespan object, such as one generated by the `New-TimeSpan` cmdlet, or
 `<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
+scheduled jobs is set to $true and Windows PowerShell ignores the **IdleDuration** and
 **IdleTimeout** values.
 
 ```yaml
diff --git a/reference/5.1/PSWorkflow/About/about_ActivityCommonParameters.md b/reference/5.1/PSWorkflow/About/about_ActivityCommonParameters.md
@@ -64,7 +64,7 @@ This section describes the activity common parameters.
 
 #### AppendOutput \<Boolean\>
 
-A value of `$True` adds the output of the activity to the value of the variable.
+A value of `$true` adds the output of the activity to the value of the variable.
 A value of `$false` has no effect. By default, assigning a value to a variable
 replaces the variable value.
 
@@ -144,7 +144,7 @@ piping objects to the activity one at a time.
 
 #### MergeErrorToOutput \<Boolean\>
 
-A value of `$True` adds errors to the output stream. A value of `$false` has
+A value of `$true` adds errors to the output stream. A value of `$false` has
 no effect. Use this parameter with the **Parallel** and `ForEach -Parallel`
 keywords to collect errors and output from multiple parallel commands
 in a single collection.
@@ -169,14 +169,14 @@ affected target computer.
 
 #### PSAllowRedirection \<Boolean\>
 
-A value of `$True` allows redirection of the connection to the target computers.
+A value of `$true` allows redirection of the connection to the target computers.
 A value of `$false` has no effect. This activity common parameter is also a
 workflow common parameter.
 
 When you use the **PSConnectionURI** parameter, the remote destination can return
 an instruction to redirect to a different URI. By default, Windows PowerShell
 does not redirect connections, but you can use the **PSAllowRedirection** parameter
-with a value of `$True` to allow redirection of the connection to the target
+with a value of `$true` to allow redirection of the connection to the target
 computer.
 
 You can also limit the number of times that the connection is redirected by
@@ -338,8 +338,8 @@ 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
-    InlineScript {\Server01\Share01\Set-AssetData.ps1} -PSDebug $debugCollection -Debug $True
+    InlineScript {\Server01\Share01\Get-AssetData.ps1} -PSDebug $debugCollection -Debug $true
+    InlineScript {\Server01\Share01\Set-AssetData.ps1} -PSDebug $debugCollection -Debug $true
     if ($debugCollection -like "Missing") { ...}
 }
 ```
@@ -362,7 +362,7 @@ Valid values:
 - (Default) If omitted, and you have also not added the
   **PSDisableSerialization** parameter to an activity, objects are serialized.
 
-- `$True`. Directs all activities within a workflow to return
+- `$true`. Directs all activities within a workflow to return
   "live" (not serialized) objects. The resulting objects have methods, as well
   as properties, but they cannot be saved when a checkpoint is taken.
 - `$false`. Workflow objects are serialized.
@@ -411,7 +411,7 @@ Valid values:
 - (Default) If you omit this parameter, no checkpoints are added. Checkpoints
   are taken based on the settings for the workflow.
 
-- `$True`. Takes a checkpoint after the activity completes. This checkpoint is
+- `$true`. Takes a checkpoint after the activity completes. This checkpoint is
   in addition to any checkpoints that are specified in the workflow.
 
 - `$false`. No checkpoints are added. Checkpoints are taken only when specified
@@ -499,7 +499,7 @@ For more information about the `$PSSessionOption` preference variable, see
 
 #### PSUseSSL \<Boolean\>
 
-A value of `$True` uses the Secure Sockets Layer (SSL) protocol to establish a
+A value of `$true` uses the Secure Sockets Layer (SSL) protocol to establish a
 connection to the target computer. By default, SSL is not used. A value of
 `$false` has no effect. This activity common parameter is also a workflow common
 parameter.
@@ -539,7 +539,7 @@ activity.
 ```powershell
 workflow Test-Workflow
 {
-    Get-Service -UseDefaultInput $True
+    Get-Service -UseDefaultInput $true
 }
 
 PS C:> Test-Workflow -InputObject WinRm
diff --git a/reference/5.1/PSWorkflow/About/about_WorkflowCommonParameters.md b/reference/5.1/PSWorkflow/About/about_WorkflowCommonParameters.md
@@ -288,7 +288,7 @@ Valid values:
   and end of the workflow, in addition to any checkpoints that are specified in
   the workflow.
 
-- `$True`. Adds a checkpoint to the beginning and end of the workflow and a
+- `$true`. Adds a checkpoint to the beginning and end of the workflow and a
   checkpoint after each activity, in addition to any checkpoints that are
   specified in the workflow.
 
diff --git a/reference/5.1/PSWorkflow/About/about_Workflows.md b/reference/5.1/PSWorkflow/About/about_Workflows.md
@@ -240,7 +240,7 @@ workflows that don't define persistence points.
 
 ```powershell
 Invoke-Command -Session $ws {
-  Test-Workflow -PSComputerName Server01, Server02 -PSPersist:$True
+  Test-Workflow -PSComputerName Server01, Server02 -PSPersist:$true
 }
 ```
 
diff --git a/reference/7.4/PSDiagnostics/Set-LogProperties.md b/reference/7.4/PSDiagnostics/Set-LogProperties.md
@@ -34,7 +34,7 @@ You must run this cmdlet from an elevated PowerShell session.
 
 ```powershell
 $logDetails = Get-LogProperties 'Windows PowerShell'
-$logDetails.Retention = $True
+$logDetails.Retention = $true
 Set-LogProperties -LogDetails $logDetails
 Get-LogProperties 'Windows PowerShell'
 ```
diff --git a/reference/7.4/PSReadLine/About/about_PSReadLine.md b/reference/7.4/PSReadLine/About/about_PSReadLine.md
diff --git a/reference/7.4/PSReadLine/Set-PSReadLineOption.md b/reference/7.4/PSReadLine/Set-PSReadLineOption.md
diff --git a/reference/7.4/ThreadJob/Start-ThreadJob.md b/reference/7.4/ThreadJob/Start-ThreadJob.md
diff --git a/reference/7.5/PSDiagnostics/Set-LogProperties.md b/reference/7.5/PSDiagnostics/Set-LogProperties.md
diff --git a/reference/7.5/PSReadLine/About/about_PSReadLine.md b/reference/7.5/PSReadLine/About/about_PSReadLine.md
diff --git a/reference/7.5/PSReadLine/Set-PSReadLineOption.md b/reference/7.5/PSReadLine/Set-PSReadLineOption.md
diff --git a/reference/7.5/ThreadJob/Start-ThreadJob.md b/reference/7.5/ThreadJob/Start-ThreadJob.md
diff --git a/reference/7.6/PSDiagnostics/Set-LogProperties.md b/reference/7.6/PSDiagnostics/Set-LogProperties.md
diff --git a/reference/7.6/PSReadLine/About/about_PSReadLine.md b/reference/7.6/PSReadLine/About/about_PSReadLine.md
diff --git a/reference/7.6/PSReadLine/Set-PSReadLineOption.md b/reference/7.6/PSReadLine/Set-PSReadLineOption.md
diff --git a/reference/7.6/ThreadJob/Start-ThreadJob.md b/reference/7.6/ThreadJob/Start-ThreadJob.md
