diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_Command_Syntax.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_Command_Syntax.md index fc6511b16e35..31f150348197 100644 --- a/reference/7.5/Microsoft.PowerShell.Core/About/about_Command_Syntax.md +++ b/reference/7.5/Microsoft.PowerShell.Core/About/about_Command_Syntax.md @@ -166,7 +166,7 @@ The syntax diagrams use the following symbols: The placeholder inside the angle brackets identifies the .NET type of the value that a parameter takes. For example, to use the **Name** parameter of - the `Get-Command ` cmdlet, you replace the `` with one or more + the `Get-Command` cmdlet, you replace the `` with one or more strings separated by commas (`,`). diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md index 73e3dc742f4f..fcf44d9f3ecf 100644 --- a/reference/7.5/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md +++ b/reference/7.5/Microsoft.PowerShell.Core/About/about_Functions_Advanced_Parameters.md @@ -659,7 +659,7 @@ Both arguments are optional. If you don't specify any arguments, then ### PSTypeName attribute -You can't use extended type names in a type declaration. The *PSTypeName** +You can't use extended type names in a type declaration. The **PSTypeName** attribute allows you to restrict the type of the parameter to the extended type. diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_If.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_If.md index 8d9bbc25c298..ebf167924c90 100644 --- a/reference/7.5/Microsoft.PowerShell.Core/About/about_If.md +++ b/reference/7.5/Microsoft.PowerShell.Core/About/about_If.md @@ -133,7 +133,6 @@ $service.Status -eq 'Running' ? (Stop-Service $service) : (Start-Service $servic In this example, if the service is running, it's stopped, and if its status is not **Running**, it's started. - If a ``, ``, or `` expression calls a command, you must wrap it in parentheses. If you don't, PowerShell raises an argument exception for the command in the `` expression and parsing diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_Path_Syntax.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_Path_Syntax.md index 648faca39dd7..27dc1e3f268c 100644 --- a/reference/7.5/Microsoft.PowerShell.Core/About/about_Path_Syntax.md +++ b/reference/7.5/Microsoft.PowerShell.Core/About/about_Path_Syntax.md @@ -87,7 +87,7 @@ The following examples are based on the current working directory being set to When using a path in a command, you can use a fully qualified path or a relative one. For example, suppose that your current working directory is `C:\Windows`. The following `Get-ChildItem` command retrieves all items in the -`C:\TechDocs `directory: +`C:\TechDocs` directory: ```powershell Get-ChildItem \TechDocs diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_Providers.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_Providers.md index 047e7ba86703..a6bb6877baf3 100644 --- a/reference/7.5/Microsoft.PowerShell.Core/About/about_Providers.md +++ b/reference/7.5/Microsoft.PowerShell.Core/About/about_Providers.md @@ -233,7 +233,7 @@ drive:\location\child-location\... ``` For example, to change your location to the `HKLM\Software` registry key, type -a `Set-Location `command, such as: +a `Set-Location` command, such as: ```powershell Set-Location HKLM:\SOFTWARE\ diff --git a/reference/7.5/Microsoft.PowerShell.Core/About/about_Ref.md b/reference/7.5/Microsoft.PowerShell.Core/About/about_Ref.md index 616429b8bfc6..8fcfc9f73b2c 100644 --- a/reference/7.5/Microsoft.PowerShell.Core/About/about_Ref.md +++ b/reference/7.5/Microsoft.PowerShell.Core/About/about_Ref.md @@ -16,9 +16,9 @@ of a variable that is passed to it. ## Long description -You can pass variables to functions *by reference* or *by value*. +You can pass variables to functions _by reference_ or _by value_. -When you pass a variable *by value*, you are passing a copy of the data. +When you pass a variable _by value_, you are passing a copy of the data. In the following example, the function changes the value of the variable passed to it. In PowerShell, integers are value types so they are passed by value. @@ -41,9 +41,9 @@ $var In the following example, a variable containing a `Hashtable` is passed to a function. `Hashtable` is an object type so by default it is passed to the -function *by reference*. +function _by reference_. -When passing a variable *by reference*, the function can change the data and +When passing a variable _by reference_, the function can change the data and that change persists after the function executes. ```powershell diff --git a/reference/7.5/Microsoft.PowerShell.Diagnostics/Get-WinEvent.md b/reference/7.5/Microsoft.PowerShell.Diagnostics/Get-WinEvent.md index 119e5cdc8cc2..6ce408bf425a 100644 --- a/reference/7.5/Microsoft.PowerShell.Diagnostics/Get-WinEvent.md +++ b/reference/7.5/Microsoft.PowerShell.Diagnostics/Get-WinEvent.md @@ -500,7 +500,7 @@ from newest to oldest. Event Tracing for Windows (ETW) writes events to the log as events occur. The events are stored in the order of oldest to newest. An archived ETW file is saved as an `.etl` such as **TraceLog.etl**. -The events are listed in the order in which they are written to the log, so the *Oldest* parameter +The events are listed in the order in which they are written to the log, so the `Oldest` parameter is required. ```powershell diff --git a/reference/7.5/Microsoft.PowerShell.Management/Join-Path.md b/reference/7.5/Microsoft.PowerShell.Management/Join-Path.md index f6873c7aecad..1eb6b610a68f 100644 --- a/reference/7.5/Microsoft.PowerShell.Management/Join-Path.md +++ b/reference/7.5/Microsoft.PowerShell.Management/Join-Path.md @@ -140,7 +140,7 @@ In this example, no parameter names are used, thus "a" binds to `Path`, "b" to ` ### -AdditionalChildPath -Specifies additional elements to append to the value of the *Path* parameter. The `ChildPath` +Specifies additional elements to append to the value of the `Path` parameter. The `ChildPath` parameter is still mandatory and must be specified as well. This parameter is specified with the `ValueFromRemainingArguments` property which enables diff --git a/reference/7.5/Microsoft.PowerShell.Management/Set-Item.md b/reference/7.5/Microsoft.PowerShell.Management/Set-Item.md index fdc05685d805..517430ebcb4a 100644 --- a/reference/7.5/Microsoft.PowerShell.Management/Set-Item.md +++ b/reference/7.5/Microsoft.PowerShell.Management/Set-Item.md @@ -171,7 +171,7 @@ Forces the cmdlet to set items that cannot otherwise be changed, such as read-on variables. The cmdlet cannot change constant aliases or variables. Implementation varies from provider to provider. For more information, see [about_Providers](../Microsoft.PowerShell.Core/About/about_Providers.md). -Even using the *Force* parameter, the cmdlet cannot override security restrictions. +Even using the `Force` parameter, the cmdlet cannot override security restrictions. ```yaml Type: System.Management.Automation.SwitchParameter diff --git a/reference/7.5/Microsoft.PowerShell.Security/Set-ExecutionPolicy.md b/reference/7.5/Microsoft.PowerShell.Security/Set-ExecutionPolicy.md index 41a88e13b5b0..93332faa86ae 100644 --- a/reference/7.5/Microsoft.PowerShell.Security/Set-ExecutionPolicy.md +++ b/reference/7.5/Microsoft.PowerShell.Security/Set-ExecutionPolicy.md @@ -235,7 +235,7 @@ policy. The policy is set for the default scope, `LocalMachine`. The `Get-ExecutionPolicy` cmdlet shows that `RemoteSigned` is the effective execution policy for the current PowerShell session. -The `Start-ActivityTracker.ps1 script is executed from the current directory. The script is blocked +The `Start-ActivityTracker.ps1` script is executed from the current directory. The script is blocked by `RemoteSigned` because the script isn't digitally signed. For this example, the script's code was reviewed and verified as safe to run. The `Unblock-File` diff --git a/reference/7.5/Microsoft.PowerShell.Utility/Measure-Object.md b/reference/7.5/Microsoft.PowerShell.Utility/Measure-Object.md index f761b1339e38..bffbdd2d8d96 100644 --- a/reference/7.5/Microsoft.PowerShell.Utility/Measure-Object.md +++ b/reference/7.5/Microsoft.PowerShell.Utility/Measure-Object.md @@ -244,7 +244,7 @@ Property : num ### Example 11: Measure the Standard Deviation Beginning in PowerShell 6, `Measure-Object` supports the `-StandardDeviation` parameter. The -following example determines the *standard deviation* for the CPU used by all processes. A large +following example determines the _standard deviation_ for the CPU used by all processes. A large deviation would indicate a small number of processes consuming the most CPU. ```powershell @@ -344,7 +344,7 @@ Accept wildcard characters: False Indicates that the cmdlet counts the number of characters in the input objects. > [!NOTE] -> The **Word**, **Char** and **Line** switches count *inside* each input object, as well as *across* +> The **Word**, **Char** and **Line** switches count _inside_ each input object, as well as _across_ > input objects. See Example 7. ```yaml @@ -404,7 +404,7 @@ Accept wildcard characters: False Indicates that the cmdlet counts the number of lines in the input objects. > [!NOTE] -> The **Word**, **Char** and **Line** switches count *inside* each input object, as well as *across* +> The **Word**, **Char** and **Line** switches count _inside_ each input object, as well as _across_ > input objects. See Example 7. ```yaml @@ -509,7 +509,7 @@ Accept wildcard characters: False Indicates that the cmdlet counts the number of words in the input objects. > [!NOTE] -> The **Word**, **Char** and **Line** switches count *inside* each input object, as well as *across* +> The **Word**, **Char** and **Line** switches count _inside_ each input object, as well as _across_ > input objects. See Example 7. ```yaml diff --git a/reference/7.5/Microsoft.PowerShell.Utility/Out-String.md b/reference/7.5/Microsoft.PowerShell.Utility/Out-String.md index 8484da6c4837..a7e0f0296abb 100644 --- a/reference/7.5/Microsoft.PowerShell.Utility/Out-String.md +++ b/reference/7.5/Microsoft.PowerShell.Utility/Out-String.md @@ -112,7 +112,7 @@ parameter to find matches for the text **gcm**. > If you omit the **Stream** parameter, the command displays all the aliases because `Select-String` > finds the text **gcm** in the single string that `Out-String` returns. -### Example 3: Use the Width parameter to prevent truncation. +### Example 3: Use the Width parameter to prevent truncation While most output from `Out-String` is wrapped to the next line, there are scenarios where the output is truncated by the formatting system before being passed to `Out-String`. You can avoid diff --git a/reference/7.5/Microsoft.PowerShell.Utility/Unblock-File.md b/reference/7.5/Microsoft.PowerShell.Utility/Unblock-File.md index aa90e98d091c..dd703be53143 100644 --- a/reference/7.5/Microsoft.PowerShell.Utility/Unblock-File.md +++ b/reference/7.5/Microsoft.PowerShell.Utility/Unblock-File.md @@ -70,7 +70,7 @@ PS C:\> dir C:\Downloads\*PowerShell* | Unblock-File This command shows how to find and unblock PowerShell scripts. -The first command uses the **Stream** parameter of the *Get-Item* cmdlet get files with the +The first command uses the **Stream** parameter of the `Get-Item` cmdlet get files with the **Zone.Identifier** stream. The second command shows what happens when you run a blocked script in a PowerShell session in which diff --git a/reference/7.5/Microsoft.PowerShell.Utility/Wait-Debugger.md b/reference/7.5/Microsoft.PowerShell.Utility/Wait-Debugger.md index 12f36c330446..7cb359e2be8f 100644 --- a/reference/7.5/Microsoft.PowerShell.Utility/Wait-Debugger.md +++ b/reference/7.5/Microsoft.PowerShell.Utility/Wait-Debugger.md @@ -94,6 +94,7 @@ line 13. In this example, the `Wait-Debugger` command was inserted in the `CopyFile` method of a DSC resource. This is similar to using `Enable-RunspaceDebug -BreakAll` in a DSC resource but breaks at a specific point in the script. + ``` [DscResource()] class FileResource diff --git a/reference/7.5/Microsoft.WSMan.Management/About/about_WSMan_Provider.md b/reference/7.5/Microsoft.WSMan.Management/About/about_WSMan_Provider.md index 1048dad0e3a9..2f24913b6dd1 100644 --- a/reference/7.5/Microsoft.WSMan.Management/About/about_WSMan_Provider.md +++ b/reference/7.5/Microsoft.WSMan.Management/About/about_WSMan_Provider.md @@ -198,7 +198,7 @@ Set-Item WSMAN:\localhost\Client\TrustedHosts *.domain2.com -Concatenate The `New-Item` cmdlet creates items within a provider drive. Each provider has different item types that you can create. In the `WSMAN:` drive, you can -create *Listeners* which you configure to receive and respond to remote +create _Listeners_ which you configure to receive and respond to remote requests. The following command creates a new HTTP listener using the `New-Item` cmdlet. @@ -300,7 +300,7 @@ of the following: ### Capability \ -When working with *Plug-ins* this parameter specifies an operation that is +When working with _Plug-ins_ this parameter specifies an operation that is supported on this Uniform Resource Identifier (URI). You have to create one entry for each type of operation that the URI supports. You can specify any valid attributes for a given operation, if the operation supports it.