Markdown and PS Styles

reference/7.5/Microsoft.PowerShell.Core/Add-History.md

@@ -31,7 +31,8 @@ about the session history, see [about_History](About/about_History.md).
 
 The session history is managed separately from the history maintained by the **PSReadLine** module.
 Both histories are available in sessions where **PSReadLine** is loaded. This cmdlet only works with
-the session history. For more information see, [about_PSReadLine](../PSReadLine/About/about_PSReadLine.md).
+the session history. For more information see,
+[about_PSReadLine](../PSReadLine/About/about_PSReadLine.md).
 
 You can use the `Get-History` cmdlet to get the commands and pass them to `Add-History`, or you can
 export the commands to a CSV or XML file, then import the commands, and pass the imported file to
@@ -122,9 +123,9 @@ PowerShell. The `Add-History` cmdlet then adds the commands in the file to the s
 
 ### -InputObject
 
-Specifies an array of entries to add to the history as **HistoryInfo** object to the session history.
-You can use this parameter to submit a **HistoryInfo** object, such as the ones that are returned by
-the `Get-History`, `Import-Clixml`, or `Import-Csv` cmdlets, to `Add-History`.
+Specifies an array of entries to add to the history as **HistoryInfo** object to the session
+history. You can use this parameter to submit a **HistoryInfo** object, such as the ones that are
+returned by the `Get-History`, `Import-Clixml`, or `Import-Csv` cmdlets, to `Add-History`.
 
 ```yaml
 Type: System.Management.Automation.PSObject[]

reference/7.5/Microsoft.PowerShell.Core/Clear-History.md

@@ -256,7 +256,8 @@ wildcards to match commands in the PowerShell session history displayed by `Get-
 enter more than one string, `Clear-History` deletes commands that match any of the strings. The
 **CommandLine** parameter can be used with **Count**.
 
-For strings with a space, use single quotations. For more information, see [about_Quoting_Rules](About/about_Quoting_Rules.md).
+For strings with a space, use single quotations. For more information, see
+[about_Quoting_Rules](About/about_Quoting_Rules.md).
 
 ```yaml
 Type: System.String[]
@@ -400,7 +401,8 @@ information, see [about_History](About/about_History.md).
 
 The session history is managed separately from the history maintained by the **PSReadLine** module.
 Both histories are available in sessions where **PSReadLine** is loaded. This cmdlet only works with
-the session history. For more information see, [about_PSReadLine](../PSReadLine/About/about_PSReadLine.md).
+the session history. For more information see,
+[about_PSReadLine](../PSReadLine/About/about_PSReadLine.md).
 
 ## RELATED LINKS
 

reference/7.5/Microsoft.PowerShell.Core/Disable-ExperimentalFeature.md

@@ -32,9 +32,9 @@ This cmdlet was introduced in PowerShell 6.2.
 
 ### Example 1: Disable an experimental feature
 
-In this example, if this experimental feature was previously enabled, then the `powershell.config.json`
-file is updated for the user to not enable that feature once PowerShell is restarted.
-Upon success nothing is output to the pipeline and only a warning message is displayed.
+In this example, if this experimental feature was previously enabled, then the
+`powershell.config.json` file is updated for the user to not enable that feature once PowerShell is
+restarted. Upon success nothing is output to the pipeline and only a warning message is displayed.
 
 ```powershell
 Disable-ExperimentalFeature -Name PSImplicitRemotingBatching
@@ -142,6 +142,6 @@ Changes to state of an experimental feature only take effect on restart of Power
 
 [Get-ExperimentalFeature](Get-ExperimentalFeature.md)
 
-[about_Experimental_Features](/powershell/module/microsoft.powershell.core/about/about_experimental_features)
+[about_Experimental_Features](About/about_Experimental_Features.md)
 
 [Using Experimental Features](/powershell/scripting/learn/experimental-features)

reference/7.5/Microsoft.PowerShell.Core/Disable-PSRemoting.md

@@ -57,7 +57,8 @@ option.
 
 ### Example 1: Prevent remote access to all PowerShell session configurations
 
-This example prevents remote access to all PowerShell session endpoint configurations on the computer.
+This example prevents remote access to all PowerShell session endpoint configurations on the
+computer.
 
 ```powershell
 Disable-PSRemoting
@@ -537,9 +538,9 @@ This cmdlet is only available on Windows platforms.
   following changes manually.
 
   1. Stop and disable the WinRM service.
-  2. Delete the listener that accepts requests on any IP address.
-  3. Disable the firewall exceptions for WS-Management communications.
-  4. Restore the value of the LocalAccountTokenFilterPolicy to 0, which restricts remote access to
+  1. Delete the listener that accepts requests on any IP address.
+  1. Disable the firewall exceptions for WS-Management communications.
+  1. Restore the value of the LocalAccountTokenFilterPolicy to 0, which restricts remote access to
      members of the Administrators group on the computer.
 
 - A session endpoint configuration is a group of settings that define the environment for a session.

reference/7.5/Microsoft.PowerShell.Core/Disconnect-PSSession.md

@@ -193,7 +193,7 @@ and in the session configuration on the remote computer. Values set for the sess
 over values set in the session configuration, but session values cannot exceed quotas set in the
 session configuration, such as the **MaxIdleTimeoutMs** value.
 
-```
+```powershell
 PS> $Timeout = New-PSSessionOption -IdleTimeout 172800000
 PS> $s = New-PSSession -Computer Server01 -Name ITTask -SessionOption $Timeout
 PS> Disconnect-PSSession -Session $s

reference/7.5/Microsoft.PowerShell.Core/Enable-ExperimentalFeature.md

@@ -32,9 +32,9 @@ This cmdlet was introduced in PowerShell 6.2.
 
 ### Example 1: Enable an experimental feature
 
-In this example, if this experimental feature was previously disabled, then the `powershell.config.json`
-file is updated for the user to enable that feature once PowerShell is restarted.
-Upon success nothing is output to the pipeline and only a warning message is displayed.
+In this example, if this experimental feature was previously disabled, then the
+`powershell.config.json` file is updated for the user to enable that feature once PowerShell is
+restarted. Upon success nothing is output to the pipeline and only a warning message is displayed.
 
 ```powershell
 Enable-ExperimentalFeature PSImplicitRemotingBatching
@@ -117,7 +117,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
 
@@ -141,6 +142,6 @@ Changes to state of an experimental feature only take effect on restart of Power
 
 [Get-ExperimentalFeature](Get-ExperimentalFeature.md)
 
-[about_Experimental_Features](/powershell/module/microsoft.powershell.core/about/about_experimental_features)
+[about_Experimental_Features](About/about_Experimental_Features.md)
 
 [Using Experimental Features](/powershell/scripting/learn/experimental-features)

reference/7.5/Microsoft.PowerShell.Core/Enable-PSRemoting.md

@@ -83,8 +83,8 @@ option. This cmdlet is not available on Linux or macOS versions of PowerShell.
 
 For more information about using PowerShell remoting, see the following articles:
 
-- [about_Remote_Requirements](about/about_Remote_Requirements.md)
-- [about_Remote](about/about_Remote.md)
+- [about_Remote_Requirements](About/about_Remote_Requirements.md)
+- [about_Remote](About/about_Remote.md)
 
 ## EXAMPLES
 

reference/7.5/Microsoft.PowerShell.Core/Enable-PSSessionConfiguration.md

@@ -229,7 +229,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/7.5/Microsoft.PowerShell.Core/Export-ModuleMember.md

@@ -201,7 +201,8 @@ Accept wildcard characters: True
 
 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/7.5/Microsoft.PowerShell.Core/Get-Command.md

@@ -764,12 +764,12 @@ PowerShell includes the following aliases for `Get-Command`:
 - When more than one command that has the same name is available to the session, `Get-Command`
   returns the command that runs when you type the command name. To get commands that have the same
   name, listed in run order, use the **All** parameter. For more information, see
-  [about_Command_Precedence](../Microsoft.PowerShell.Core/About/about_Command_Precedence.md).
+  [about_Command_Precedence](About/about_Command_Precedence.md).
 - When a module is imported automatically, the effect is the same as using the `Import-Module`
   cmdlet. The module can add commands, types and formatting files, and run scripts in the session.
   To enable, disable, and configuration automatic importing of modules, use the
   `$PSModuleAutoLoadingPreference` preference variable. For more information, see
-  [about_Preference_Variables](../Microsoft.PowerShell.Core/About/about_Preference_Variables.md).
+  [about_Preference_Variables](About/about_Preference_Variables.md).
 
 ## RELATED LINKS
 

reference/7.5/Microsoft.PowerShell.Core/Get-ExperimentalFeature.md

@@ -63,7 +63,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
 
@@ -84,6 +85,6 @@ name is specified.
 
 [Enable-ExperimentalFeature](Enable-ExperimentalFeature.md)
 
-[about_Experimental_Features](/powershell/module/microsoft.powershell.core/about/about_experimental_features)
+[about_Experimental_Features](About/about_Experimental_Features.md)
 
 [Using Experimental Features](/powershell/scripting/learn/experimental-features)

reference/7.5/Microsoft.PowerShell.Core/Get-Help.md

@@ -100,8 +100,8 @@ fallback locale, it looks for help articles in English, **en-US**, before it ret
 message or displaying autogenerated help.
 
 For information about the symbols that `Get-Help` displays in the command syntax diagram, see
-[about_Command_Syntax](./About/about_Command_Syntax.md). For information about parameter attributes,
-such as **Required** and **Position**, see [about_Parameters](./About/about_Parameters.md).
+[about_Command_Syntax](About/about_Command_Syntax.md). For information about parameter attributes,
+such as **Required** and **Position**, see [about_Parameters](About/about_Parameters.md).
 
 > [!NOTE]
 > In PowerShell 3.0 and PowerShell 4.0, `Get-Help` can't find **About** articles in modules unless
@@ -118,10 +118,10 @@ immediately to the left of a parameter, the function jumps to that parameter's d
 full help topic. When you hit <kbd>Q</kbd> to exit the help view, you are returned to the command
 line at the same cursor position so you can continue typing the command.
 
-When you use the key combination <kbd>Alt</kbd>+<kbd>h</kbd>, the **PSReadLine** `ShowParameterHelp` function
-displays help information for the parameter immediately to the left of the cursor. The help text is
-displayed below the command line. This allows you to see the description of the parameter and
-continue typing your command.
+When you use the key combination <kbd>Alt</kbd>+<kbd>h</kbd>, the **PSReadLine** `ShowParameterHelp`
+function displays help information for the parameter immediately to the left of the cursor. The help
+text is displayed below the command line. This allows you to see the description of the parameter
+and continue typing your command.
 
 For more information, see [Using dynamic help](/powershell/scripting/learn/shell/dynamic-help).
 
@@ -329,7 +329,7 @@ SYNOPSIS
 ### Example 12: Display help for a script
 
 This example gets help for the `MyScript.ps1 script`. For information about how to write help for
-your functions and scripts, see [about_Comment_Based_Help](./About/about_Comment_Based_Help.md).
+your functions and scripts, see [about_Comment_Based_Help](About/about_Comment_Based_Help.md).
 
 ```powershell
 Get-Help -Name C:\PS-Test\MyScript.ps1
@@ -505,7 +505,7 @@ for cmdlet, function, workflow, and script help articles. You can't use the **On
 with `Get-Help` in a remote session.
 
 For information about supporting this feature in help articles that you write, see
-[about_Comment_Based_Help](./About/about_Comment_Based_Help.md), and
+[about_Comment_Based_Help](About/about_Comment_Based_Help.md), and
 [Supporting Online Help](/powershell/scripting/developer/module/supporting-online-help), and
 [Writing Help for PowerShell Cmdlets](/powershell/scripting/developer/help/writing-help-for-windows-powershell-cmdlets).
 
@@ -554,7 +554,7 @@ To see the custom cmdlet help for a provider path, go to the provider path locat
 the provider path. You can also find custom cmdlet help online in the provider help section of the
 help articles.
 
-For more information about PowerShell providers, see [about_Providers](./About/about_Providers.md).
+For more information about PowerShell providers, see [about_Providers](About/about_Providers.md).
 
 > [!NOTE]
 > The provider for the path specified must have a PowerShell provider help file installed. If no
@@ -691,7 +691,7 @@ following fields:
 
 [about_Command_Syntax](About/about_Command_Syntax.md)
 
-[about_Comment_Based_Help](./About/about_Comment_Based_Help.md)
+[about_Comment_Based_Help](About/about_Comment_Based_Help.md)
 
 [Get-Command](Get-Command.md)
 

reference/7.5/Microsoft.PowerShell.Core/Get-History.md

@@ -31,7 +31,8 @@ features in PowerShell, see [about_History](About/about_History.md).
 
 The session history is managed separately from the history maintained by the **PSReadLine** module.
 Both histories are available in sessions where **PSReadLine** is loaded. This cmdlet only works with
-the session history. For more information see, [about_PSReadLine](../PSReadLine/About/about_PSReadLine.md).
+the session history. For more information, see
+[about_PSReadLine](../PSReadLine/About/about_PSReadLine.md).
 
 ## EXAMPLES
 
@@ -163,7 +164,8 @@ command history, see [about_History](About/about_History.md).
 
 Starting in Windows PowerShell 3.0, the default value of the `$MaximumHistoryCount` preference
 variable is `4096`. In Windows PowerShell 2.0, the default value is `64`. For more information about
-the `$MaximumHistoryCount` variable, see [about_Preference_Variables](About/about_Preference_Variables.md).
+the `$MaximumHistoryCount` variable, see
+[about_Preference_Variables](About/about_Preference_Variables.md).
 
 ## RELATED LINKS
 

reference/7.5/Microsoft.PowerShell.Core/Get-Job.md

@@ -70,7 +70,7 @@ contain the job results. To get the results, use the `Receive-Job` cmdlet.
 A Windows PowerShell background job is a command that runs in the background without interacting
 with the current session. Typically, you use a background job to run a complex command that takes a
 long time to finish. For more information about background jobs in Windows PowerShell, see
-[about_Jobs](./about/about_Jobs.md).
+[about_Jobs](About/about_Jobs.md).
 
 Beginning in Windows PowerShell 3.0, the `Get-Job` cmdlet also gets custom job types, such as
 workflow jobs and instances of scheduled jobs. To find the job type of a job, use the
@@ -146,7 +146,8 @@ Id     Name            PSJobTypeName   State         HasMoreData     Location
 ### Example 4: Get jobs that include a specific command by using the pipeline
 
 Like the command in the previous example, this command gets the jobs on the system that include a
-`Get-Process` command. The command uses a pipeline operator (`|`) to send a PSCustomObject with the NoteProperty **Command**, to the `Get-Job` cmdlet. It is the equivalent of the previous command.
+`Get-Process` command. The command uses a pipeline operator (`|`) to send a PSCustomObject with the
+NoteProperty **Command**, to the `Get-Job` cmdlet. It is the equivalent of the previous command.
 
 ```powershell
 [pscustomobject]@{Command='*Get-Process*'} | Get-Job
@@ -244,7 +245,7 @@ parameter. It then gets the job using the `Get-Job` command on the S2 computer u
 The sample output shows the results of the `Get-Job` command. On the S2 computer, the job
 appears to be a local job. The computer name is localhost and the job type is a background job.
 For more information about how to run background jobs on remote computers, see
-[about_Remote_Jobs](./about/about_Remote_Jobs.md).
+[about_Remote_Jobs](About/about_Remote_Jobs.md).
 
 ```powershell
 Start-Job -ScriptBlock {Get-EventLog -LogName System}
@@ -298,8 +299,8 @@ error. In this case, the user forgot to use the Run as administrator option when
 PowerShell.Because background jobs use the remoting features of Windows PowerShell, the computer
 must be configured for remoting to run a job, even when the job runs on the local computer.For
 information about requirements for remoting in Windows PowerShell, see
-[about_Remote_Requirements](./about/about_Remote_Requirements.md). For troubleshooting tips, see
-[about_Remote_Troubleshooting](./about/about_Remote_Troubleshooting.md).
+[about_Remote_Requirements](About/about_Remote_Requirements.md). For troubleshooting tips, see
+[about_Remote_Troubleshooting](About/about_Remote_Troubleshooting.md).
 
 ```powershell
 PS> Start-Job -ScriptBlock {Get-Process}
@@ -415,7 +416,7 @@ Access is denied.
 ```
 
 For more information, see the
-[about_Remote_Troubleshooting](./about/about_Remote_Troubleshooting.md) Help topic.
+[about_Remote_Troubleshooting](About/about_Remote_Troubleshooting.md) Help topic.
 
 ## PARAMETERS
 

reference/7.5/Microsoft.PowerShell.Core/Get-Module.md

@@ -122,7 +122,7 @@ This command gets all of the exported files for all available modules.
 
 ```powershell
 $FullyQualifiedName = @{ModuleName="Microsoft.PowerShell.Management";ModuleVersion="3.1.0.0"}
-Get-Module -FullyQualifiedName $FullyQualifiedName | Format-Table -Property Name,Version
+Get-Module -FullyQualifiedName $FullyQualifiedName | Format-Table -Property Name, Version
 ```
 
 ```Output
@@ -249,7 +249,7 @@ information about a module, its requirements, and its contents.
 
 ```powershell
 # First command
-$m = Get-Module -list -Name BitsTransfer
+$m = Get-Module -List -Name BitsTransfer
 
 # Second command
 Get-Content $m.Path

reference/7.5/Microsoft.PowerShell.Core/Get-PSHostProcessInfo.md

@@ -122,7 +122,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/7.5/Microsoft.PowerShell.Core/Get-PSSession.md

@@ -132,7 +132,7 @@ command runs when you use the **ComputerName** or **ConnectionUri** parameters.
 > in the current session. The **ComputerName** parameter gets sessions that were created in the
 > current session and connect to the specified computer.
 
-For more information about PowerShell sessions, see [about_PSSessions](about/about_PSSessions.md).
+For more information about PowerShell sessions, see [about_PSSessions](About/about_PSSessions.md).
 
 ## EXAMPLES
 
@@ -684,8 +684,8 @@ values for this parameter are: `All`, `Opened`, `Disconnected`, `Closed`, and `B
 value is `All`.
 
 The session state value is relative to the current sessions. Sessions that were not created in the
-current sessions and are not connected to the current session have a state of `Disconnected` even when
-they are connected to a different session.
+current sessions and are not connected to the current session have a state of `Disconnected` even
+when they are connected to a different session.
 
 The state of a session is stored in the **State** property of the session.