remove highbit chars v5 (#4103)

* remove highbit chars v5

* fix build errors

Author: sdwheeler

reference/4.0/ISE/Import-IseSnippet.md

@@ -37,14 +37,14 @@ To view and use the imported snippets, from the Windows PowerShell ISEEdit menu,
 Imported snippets are available only in the current session.
 To import the snippets into all Windows PowerShell ISE sessions, add an **Import-IseSnippet** command to your Windows PowerShell profile or copy the snippet files to your local snippets directory ($home\Documents\WindowsPowershell\Snippets).
 
-To be imported, the snippets must be properly formatted in the snippet XML for Windows PowerShell ISE snippets and saved in Snippet.ps1xml files.
+To import snippets, they must be properly formatted in the snippet XML for Windows PowerShell ISE snippets and saved in Snippet.ps1xml files.
 To create eligible snippets, use the New-IseSnippet cmdlet.
 New-IseSnippet creates a \<SnippetTitle\>.Snippets.ps1xml file in the $home\Documents\WindowsPowerShell\Snippets directory.
 You can move or copy the snippets to the Snippets directory of a Windows PowerShell module, or to any other directory.
 
-NOTE: The Get-IseSnippet cmdlet, which gets user-created snippets in the local snippets directory, does not get imported snippets.
+The Get-IseSnippet cmdlet, which gets user-created snippets in the local snippets directory, does not get imported snippets.
 
-This cmdlet is introduced in Windows PowerShell 3.0.
+This cmdlet was introduced in Windows PowerShell 3.0.
 
 ## EXAMPLES
 
@@ -198,4 +198,6 @@ This cmdlet does not generate output.
 
 [Get-IseSnippet](Get-IseSnippet.md)
 
-[New-IseSnippet](New-IseSnippet.md)
+[New-IseSnippet](New-IseSnippet.md)
+
+[about_Execution_Policies](../Microsoft.PowerShell.Core/About/about_Execution_Policies.md)

reference/4.0/ISE/New-IseSnippet.md

@@ -34,17 +34,15 @@ To see  snippets in Windows PowerShell ISE, from the **Edit** menu, select **Sta
 The **New-ISESnippet** cmdlet creates a \<Title\>.Snippets.ps1xml file in the $home\Documents\WindowsPowerShell\Snippets directory with the title that you specify.
 To include a snippet file in a module that you are authoring, add the snippet file to a Snippets subdirectory of your module directory.
 
-Note: You cannot use user-created snippets in a session in which the execution policy is AllSigned or Restricted.
-For more information, see the Notes section.
+You cannot use user-created snippets in a session in which the execution policy is **Restricted** or **AllSigned**.
 
-This cmdlet is introduced in Windows PowerShell 3.0.
+This cmdlet was introduced in Windows PowerShell 3.0.
 
 ## EXAMPLES
 
-### Example 1
-
-```powershell
-New-IseSnippet -Title Comment-BasedHelp -Description "A template for comment-based help." -Text "<#
+### Example 1: Create a Comment-BasedHelp snippet
+```
+PS C:\> New-IseSnippet -Title Comment-BasedHelp -Description "A template for comment-based help." -Text "<#
     .SYNOPSIS
     .DESCRIPTION
     .PARAMETER  <Parameter-Name>
@@ -58,34 +56,33 @@ New-IseSnippet -Title Comment-BasedHelp -Description "A template for comment-bas
 This command creates a Comment-BasedHelp snippet for Windows PowerShell ISE.
 It creates a file named "Comment-BasedHelp.snippets.ps1xml" in the user's Snippets directory ($home\Documents\WindowsPowerShell\Snippets).
 
-### Example 2
-
-```powershell
-$m = @'
+### Example 2: Create a mandatory snippet
+```
+PS C:\> $M = @'
 Param
 (
   [parameter(Mandatory=$true)]
   [String[]]
   $<ParameterName>
 )
 '@
-New-IseSnippet -Text $m -Title Mandatory -Description "Adds a mandatory function parameter." -Author "Kim Akers, Fabrikam Corp." -Force
+
+PS C:\> New-ISESnippet -Text $M -Title Mandatory -Description "Adds a mandatory function parameter." -Author "Patti Fuller, Fabrikam Corp." -Force
 ```
 
-These commands create a Mandatory snippet for Windows PowerShell ISE.
-The first command saves the snippet text in the $m variable.
+This example creates a Mandatory snippet for Windows PowerShell ISE.
+The first command saves the snippet text in the $M variable.
 The second command uses the **New-ISESnippet** cmdlet to create the snippet.
 The command uses the **Force** parameter to overwrite a previous snippet with the same name.
 
-### Example 3
-
-```powershell
-Copy-Item $home\Documents\WindowsPowerShell\Snippets\Mandatory.Snippets.ps1xml -Destination \\Server\Share
+### Example 3: Copy a mandatory snippet from a folder to a destination folder
+```
+PS C:\> Copy-Item "$Home\Documents\WindowsPowerShell\Snippets\Mandatory.Snippets.ps1xml" -Destination "\\Server\Share"
 ```
 
 This command uses the Copy-Item cmdlet to copy the Mandatory snippet from the folder where **New-ISESnippet** places it to the Server\Share file share.
 
-Because the Snippets.ps1xml files that **New-ISESnippet** creates are text (XML) files, you can use the Item cmdlets to get, changes, move, rename, and copy them.
+Because the Snippets.ps1xml files that **New-ISESnippet** creates are text (XML) files, you can use the **Item** cmdlets to get, changes, move, rename, and copy them.
 
 ## PARAMETERS
 

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

@@ -48,30 +48,32 @@ The **Enable-PSRemoting** cmdlet performs the following operations:
 
 To run this cmdlet, start Windows PowerShell with the "Run as administrator" option.
 
-CAUTION: On systems that have both Windows PowerShell 3.0 and the Windows PowerShell 2.0 engine, do not use Windows PowerShell 2.0 to run the **Enable-PSRemoting** and Disable-PSRemoting cmdlets.
-The commands might appear to succeed, but the remoting is not configured correctly.
-Remote commands, and later attempts to enable and disable remoting, are likely to fail.
+> [!CAUTION]
+> On systems that have both Windows PowerShell 3.0 and the Windows PowerShell 2.0 engine, do not use
+> Windows PowerShell 2.0 to run the **Enable-PSRemoting** and Disable-PSRemoting cmdlets. The commands
+> might appear to succeed, but the remoting is not configured correctly. Remote commands, and later
+> attempts to enable and disable remoting, are likely to fail.
 
 ## EXAMPLES
 
-### Example 1
+### Example 1: Configure a computer to receive remote commands
 
 ```powershell
 Enable-PSRemoting
 ```
 
 This command configures the computer to receive remote commands.
 
-### Example 2
+### Example 2: Configure a computer to receive remote commands without a confirmation prompt
 
 ```powershell
 Enable-PSRemoting -Force
 ```
 
 This command configures the computer to receive remote commands.
-It uses the Force parameter to suppress the user prompts.
+It uses the *Force* parameter to suppress the user prompts.
 
-### Example 3
+### Example 3: Allow remote access on clients
 
 ```powershell
 Enable-PSRemoting -SkipNetworkProfileCheck -Force
@@ -90,7 +92,8 @@ The command uses the Force parameter to suppress confirmation messages.
 The **SkipNetworkProfileCheck** parameter has no effect on server version of Windows, which allow remote access from public networks in the same local subnet by default.
 
 The second command eliminates the subnet restriction.
-The command uses the **Set-NetFirewallRule** cmdlet in the **NetSecurity** module to add a firewall rule that allows remote access from public networks from any remote location, including locations in different subnets.
+The command uses the **Set-NetFirewallRule** cmdlet in the **NetSecurity** module to add a firewall rule that allows remote access from public networks from any remote location.
+This includes locations in different subnets.
 
 ## PARAMETERS
 
@@ -136,9 +139,8 @@ This parameter has no effect on server versions of Windows, which, by default, h
 If the local subnet firewall rule is disabled on a server version of Windows, **Enable-PSRemoting** re-enables it, regardless of the value of this parameter.
 
 To remove the local subnet restriction and enable remote access from all locations on public networks, use the **Set-NetFirewallRule** cmdlet in the **NetSecurity** module.
-For more information, see Notes and Examples.
 
-This parameter is introduced in Windows PowerShell 3.0.
+This parameter was introduced in Windows PowerShell 3.0.
 
 ```yaml
 Type: SwitchParameter
@@ -183,7 +185,7 @@ You cannot pipe input to this cmdlet.
 
 ### System.String
 
-Enable-PSRemoting returns strings that describe its results.
+This cmdlet returns strings that describe its results.
 
 ## NOTES
 

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

@@ -213,7 +213,7 @@ Name         ModuleType Path
 BitsTransfer   Manifest C:\Windows\system32\WindowsPowerShell\v1.0\Modules\BitsTransfer\BitsTransfer.psd1
 ```
 
-This command gets all module files (imported and available) and groups them by module name.
+This command gets all module files, both imported and available, and then groups them by module name.
 This lets you see the module files that each script is exporting.
 
 ### Example 7: Display the contents of a module manifest
@@ -353,7 +353,7 @@ The default value is the namespace of the Module Discovery WMI provider.
 
 Use this parameter to get CIM modules from computers and devices that are not running a Windows operating system.
 
-This parameter is introduced in Windows PowerShell 3.0.
+This parameter was introduced in Windows PowerShell 3.0.
 
 ```yaml
 Type: String
@@ -372,9 +372,9 @@ Accept wildcard characters: False
 Specifies an alternate location for CIM modules.
 The default value is the resource URI of the Module Discovery WMI provider on the remote computer.
 
-Use this parameter to get CIM modules from computers and devices that are not running a Windows operating system.
+Use this parameter to get CIM modules from computers and devices that are not running the Windows operating system.
 
-This parameter is introduced in Windows PowerShell 3.0.
+This parameter was introduced in Windows PowerShell 3.0.
 
 ```yaml
 Type: Uri
@@ -394,9 +394,9 @@ Specifies a CIM session on the remote computer.
 Enter a variable that contains the CIM session or a command that gets the CIM session, such as a [Get-CimSession](https://docs.microsoft.com/powershell/module/cimcmdlets/get-cimsession) command.
 
 `Get-Module` uses the CIM session connection to get modules from the remote computer.
-When you import the module (by using the `Import-Module` cmdlet) and use the commands from the imported module in the current session, the commands actually run on the remote computer.
+When you import the module by using the `Import-Module` cmdlet and use the commands from the imported module in the current session, the commands actually run on the remote computer.
 
-You can use this parameter to get modules from computers and devices that are not running a Windows operating system, and Windows computers that have Windows PowerShell, but do not have Windows PowerShell remoting enabled.
+You can use this parameter to get modules from computers and devices that are not running the Windows operating system, and computers that have Windows PowerShell, but do not have Windows PowerShell remoting enabled.
 
 The **CimSession** parameter gets all modules in the **CIMSession**.
 However, you can import only CIM-based and Cmdlet Definition XML (CDXML)-based modules.
@@ -415,15 +415,16 @@ Accept wildcard characters: False
 
 ### -FullyQualifiedName
 
-Gets modules with names that are specified in the form of **ModuleSpecification** objects (described in the Remarks section of [ModuleSpecification Constructor (Hashtable)](https://msdn.microsoft.com/library/jj136290) in the MSDN library).
+Specifies names of modules in the form of **ModuleSpecification** objects.
+These objects are described in the Remarks section of [ModuleSpecification Constructor (Hashtable)](https://msdn.microsoft.com/library/jj136290) in the MSDN library.
 For example, the **FullyQualifiedName** parameter accepts a module name that is specified in the following formats:
 
 - @{ModuleName = "modulename"; ModuleVersion = "version_number"}
 - @{ModuleName = "modulename"; ModuleVersion = "version_number"; Guid = "GUID"}
 
 **ModuleName** and **ModuleVersion** are required, but **Guid** is optional.
 
-You cannot specify the **FullyQualifiedName** parameter in the same command as a **Name** parameter; the two parameters are mutually exclusive.
+You cannot specify the **FullyQualifiedName** parameter in the same command as a **Name** parameter.
 
 ```yaml
 Type: ModuleSpecification[]
@@ -432,7 +433,7 @@ Aliases:
 
 Required: False
 Position: Named
-Default value: All imported or available modules.
+Default value: None
 Accept pipeline input: True (ByPropertyName)
 Accept wildcard characters: False
 ```
@@ -470,12 +471,13 @@ Accept wildcard characters: False
 
 ### -Name
 
-Gets only modules with the specified names or name patterns.
-Wildcards are permitted.
+Specifies names or name patterns of modules that this cmdlet gets.
+Wildcard characters are permitted.
 You can also pipe the names to `Get-Module`.
-You cannot specify the **FullyQualifiedName** parameter in the same command as a **Name** parameter; the two parameters are mutually exclusive.
+You cannot specify the **FullyQualifiedName** parameter in the same command as a **Name** parameter.
 
-The **Name** parameter cannot accept a module GUID as a value; to return modules by specifying a GUID, use the **FullyQualifiedName** parameter instead of the **Name** parameter.
+**Name** cannot accept a module GUID as a value.
+To return modules by specifying a GUID, use **FullyQualifiedName** instead.
 
 ```yaml
 Type: String[]
@@ -484,7 +486,7 @@ Aliases:
 
 Required: False
 Position: 0
-Default value: All imported or available modules.
+Default value: None
 Accept pipeline input: True (ByValue)
 Accept wildcard characters: False
 ```
@@ -498,7 +500,7 @@ When the session is connected to a remote computer, the **ListAvailable** parame
 
 A `Get-Module` command with the **PSSession** parameter is equivalent to using the `Invoke-Command` cmdlet to run a `Get-Module -ListAvailable` command in a **PSSession**.
 
-This parameter is introduced in Windows PowerShell 3.0.
+This parameter was introduced in Windows PowerShell 3.0.
 
 ```yaml
 Type: PSSession
@@ -522,7 +524,7 @@ This parameter is designed for development and testing scenarios in which the co
 
 When the **Refresh** parameter is used in a command, the **ListAvailable** parameter is required.
 
-This parameter is introduced in Windows PowerShell 3.0.
+This parameter was introduced in Windows PowerShell 3.0.
 
 ```yaml
 Type: SwitchParameter
@@ -544,14 +546,14 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
 
 ### System.String
 
-You can pipe module names to `Get-Module`.
+You can pipe module names to this cmdlet.
 
 ## OUTPUTS
 
 ### System.Management.Automation.PSModuleInfo
 
-`Get-Module` returns objects that represent modules.
-When you use the **ListAvailable** parameter, `Get-Module` returns a **ModuleInfoGrouping** object, which is a type of **PSModuleInfo** object that has the same properties and methods.
+This cmdlet returns objects that represent modules.
+When you specify the **ListAvailable** parameter, `Get-Module` returns a **ModuleInfoGrouping** object, which is a type of **PSModuleInfo** object that has the same properties and methods.
 
 ## NOTES
 
@@ -568,9 +570,10 @@ When you use the **ListAvailable** parameter, `Get-Module` returns a **ModuleInf
 
 - To use the CIM session feature, the remote computer must have WS-Management remoting and Windows Management Instrumentation (WMI), which is the Microsoft implementation of the Common Information Model (CIM) standard. The computer must also have the Module Discovery WMI provider or an alternate WMI provider that has the same basic features.
 
-  You can use the CIM session feature on computers that are not running a Windows operating system and on Windows computers that have Windows PowerShell, but do not have Windows PowerShell remoting enabled.
+  You can use the CIM session feature on computers that are not running the Windows operating system and on Windows computers that have Windows PowerShell, but do not have Windows PowerShell remoting enabled.
 
-  You can also use the CIM parameters to get CIM modules from computers that have Windows PowerShell remoting enabled, including the local computer.
+  You can also use the CIM parameters to get CIM modules from computers that have Windows PowerShell remoting enabled.
+This includes the local computer.
 When you create a CIM session on the local computer, Windows PowerShell uses DCOM, instead of WMI, to create the session.
 
 ## RELATED LINKS

reference/4.0/Microsoft.PowerShell.Core/Invoke-Command.md

@@ -61,16 +61,6 @@ Invoke-Command [[-ComputerName] <String[]>] [-Credential <PSCredential>] [-Port
 
 ### Uri
 
-```
-Invoke-Command [-Credential <PSCredential>] [-ConfigurationName <String>] [-ThrottleLimit <Int32>]
- [[-ConnectionUri] <Uri[]>] [-AsJob] [-InDisconnectedSession] [-HideComputerName] [-JobName <String>]
- [-ScriptBlock] <ScriptBlock> [-AllowRedirection] [-SessionOption <PSSessionOption>]
- [-Authentication <AuthenticationMechanism>] [-EnableNetworkAccess] [-InputObject <PSObject>]
- [-ArgumentList <Object[]>] [-CertificateThumbprint <String>] [<CommonParameters>]
-```
-
-### Uri
-
 ```
 Invoke-Command [-Credential <PSCredential>] [-ConfigurationName <String>] [-ThrottleLimit <Int32>]
  [[-ConnectionUri] <Uri[]>] [-AsJob] [-InDisconnectedSession] [-HideComputerName] [-JobName <String>]