remove highbit chars

reference/3.0/CimCmdlets/Get-CimAssociatedInstance.md

@@ -27,79 +27,79 @@ Get-CimAssociatedInstance [[-Association] <String>] [-ResultClassName <String>]
 ```
 
 ## DESCRIPTION
-The Get-CimAssociatedInstance cmdlet retrieves the CIM instances connected to a specific CIM instance, called the source instance, by an association.
+The Get-CimAssociatedInstance cmdlet retrieves the CIM instances connected to a specific CIM
+instance, called the source instance, by an association.
 
-In an association, each CIM instance has a named role and the same CIM instance can participate in an association in different roles.
+In an association, each CIM instance has a named role and the same CIM instance can participate in
+an association in different roles.
 
-If the InputObject parameter is not specified, the cmdlet works in one of the following ways: 
+If the InputObject parameter is not specified, the cmdlet works in one of the following ways:
 
---If neither the ComputerName parameter nor the CimSession parameter is specified, then this cmdlet works on local Windows Management Instrumentation (WMI) using a Component Object Model (COM) session. 
---If either the ComputerName parameter or the CimSession parameter is specified, then this cmdlet works against the CIM server specified by either the ComputerName parameter or the CimSession parameter.
+- If neither the ComputerName parameter nor the CimSession parameter is specified, then this cmdlet
+  works on local Windows Management Instrumentation (WMI) using a Component Object Model (COM)
+  session.
+- If either the ComputerName parameter or the CimSession parameter is specified, then this cmdlet
+  works against the CIM server specified by either the ComputerName parameter or the CimSession
+  parameter.
 
 ## EXAMPLES
 
 ### Example 1: Get all the associated instances of a specific instance
 ```
 PS C:\>$disk = Get-CimInstance -ClassName Win32_LogicalDisk -KeyOnly
 
-
 PS C:\>Get-CimAssociatedInstance -InputObject $disk[1]
 ```
 
-This set of commands retrieves the instances of the class named Win32_LogicalDisk and stores the information in a variable named $disk using the Get-CimInstance cmdlet.
-The first logical disk instance in the variable is then used as the input object for the Get-CimAssociatedInstance cmdlet to get all the associated CIM instances of the specified CIM instance.
+This set of commands retrieves the instances of the class named Win32_LogicalDisk and stores the
+information in a variable named $disk using the Get-CimInstance cmdlet. The first logical disk
+instance in the variable is then used as the input object for the Get-CimAssociatedInstance cmdlet
+to get all the associated CIM instances of the specified CIM instance.
 
 ### Example 2: Get all the associated instances of a specific type
 ```
 PS C:\>$disk = Get-CimInstance -ClassName Win32_LogicalDisk -KeyOnly
 
-
 PS C:\>Get-CimAssociatedInstance -InputObject $disk[1] -ResultClass Win32_DiskPartition
 ```
 
-This set of commands retrieves all of the instances of the class named Win32_LogicalDisk and stores them in a variable named $disk.
-The first logical disk instance in the variable is then used as the input object for the Get-CimAssociatedInstance cmdlet to get all the associated instances that are associated through the specified association class Win32_DiskPartition.
+This set of commands retrieves all of the instances of the class named Win32_LogicalDisk and stores
+them in a variable named $disk. The first logical disk instance in the variable is then used as the
+input object for the Get-CimAssociatedInstance cmdlet to get all the associated instances that are
+associated through the specified association class Win32_DiskPartition.
 
 ### Example 3: Get all the associated instances through qualifier of a specific class
 ```
-PS C:\>$s = Get-CimInstance -Query "Select * from Win32_Service where name like ꞌWinmgmtꞌ"
-
-
+PS C:\>$s = Get-CimInstance -Query "Select * from Win32_Service where name like 'Winmgmt'"
 
 PS C:\>Get-CimClass -ClassName *Service* -Qualifier "Association"
 
-
-
 PS C:\>$c.CimClasName
 Win32_LoadOrderGroupServiceDependencies
-
-
 Win32_DependentService
-
-
 Win32_SystemServices
-
-
 Win32_LoadOrderGroupServiceMembers
-
-
 Win32_ServiceSpecificationService
 
-
 PS C:\>Get-CimAssociatedInstance -InputObject $s -Association Win32_DependentService
 ```
 
-This set of commands retrieves the services that depend on Windows Management Instrumentation (WMI) service and stores them in a variable named $s.
-The association class name for the Win32_DependentService is retrieved using the Get-CimClass cmdlet by specifying Association as the qualifier and is then passed with $s to the Get-CimAssociatedInstance cmdlet to get all the associated instances of the retrieved association class.
+This set of commands retrieves the services that depend on Windows Management Instrumentation (WMI)
+service and stores them in a variable named $s. The association class name for the
+Win32_DependentService is retrieved using the Get-CimClass cmdlet by specifying Association as the
+qualifier and is then passed with $s to the Get-CimAssociatedInstance cmdlet to get all the
+associated instances of the retrieved association class.
 
 ## PARAMETERS
 
 ### -Association
 Specifies the name of the association class.
 
-If you do not specify this parameter, the cmdlet returns all existing association objects irrespective of their type.
+If you do not specify this parameter, the cmdlet returns all existing association objects
+irrespective of their type.
 
-For example, if class A is associated with class B through two associations, AB1 and AB2, then this parameter can be used to specify the type of association, either AB1 or AB2.
+For example, if class A is associated with class B through two associations, AB1 and AB2, then this
+parameter can be used to specify the type of association, either AB1 or AB2.
 
 ```yaml
 Type: String
@@ -114,9 +114,9 @@ Accept wildcard characters: False
 ```
 
 ### -CimSession
-Runs the command using the specified CIM session.
-Enter a variable that contains the CIM session, or a command that creates or gets the CIM session, such as New-CimSession or Get-CimSession.
-For more information, see about_CimSessions.
+Runs the command using the specified CIM session. Enter a variable that contains the CIM session, or
+a command that creates or gets the CIM session, such as New-CimSession or Get-CimSession. For more
+information, see about_CimSessions.
 
 ```yaml
 Type: CimSession[]
@@ -134,11 +134,14 @@ Accept wildcard characters: False
 Specifies the name of the computer on which you want to run the CIM operation.
 You can specify a fully qualified domain name (FQDN) or a NetBIOS name.
 
-If you specify this parameter, the cmdlet creates a temporary session to the specified computer using the WsMan protocol.
+If you specify this parameter, the cmdlet creates a temporary session to the specified computer
+using the WsMan protocol.
 
-If you do not specify this parameter, the cmdlet performs the operation on the local computer using Component Object Model (COM).
+If you do not specify this parameter, the cmdlet performs the operation on the local computer using
+Component Object Model (COM).
 
-If multiple operations are being performed on the same computer, connecting using a CIM session gives better performance.
+If multiple operations are being performed on the same computer, connecting using a CIM session
+gives better performance.
 
 ```yaml
 Type: String[]
@@ -189,7 +192,10 @@ Accept wildcard characters: False
 Specifies the namespace for the CIM operation.
 
 The default namespace is root/cimv2.
-NOTE: You can use tab completion to browse the list of namespaces, because Windows PowerShell gets a list of namespaces from the local WMI server to provide the list of namespaces.
+
+> [!NOTE]
+> You can use tab completion to browse the list of namespaces, because Windows PowerShell gets a
+> list of namespaces from the local WMI server to provide the list of namespaces.
 
 ```yaml
 Type: String
@@ -206,9 +212,12 @@ Accept wildcard characters: False
 ### -OperationTimeoutSec
 Specifies the amount of time that the cmdlet waits for a response from the computer.
 
-By default, the value of this parameter is 0, which means that the cmdlet uses the default timeout value for the server.
+By default, the value of this parameter is 0, which means that the cmdlet uses the default timeout
+value for the server.
 
-If the OperationTimeoutSec parameter is set to a value less than the robust connection retry timeout of 3 minutes, network failures that last more than the value of the OperationTimeoutSec parameter are not recoverable, because the operation on the server times out before the client can reconnect.
+If the OperationTimeoutSec parameter is set to a value less than the robust connection retry timeout
+of 3 minutes, network failures that last more than the value of the OperationTimeoutSec parameter
+are not recoverable, because the operation on the server times out before the client can reconnect.
 
 ```yaml
 Type: UInt32
@@ -223,21 +232,26 @@ Accept wildcard characters: False
 ```
 
 ### -ResourceUri
-Specifies the resource uniform resource identifier (URI) of the resource class or instance.
-The URI is used to identify a specific type of resource, such as disks or processes, on a computer.
+Specifies the resource uniform resource identifier (URI) of the resource class or instance. The URI
+is used to identify a specific type of resource, such as disks or processes, on a computer.
 
 A URI consists of a prefix and a path to a resource.
 For example:
 
-http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_LogicalDisk
-http://intel.com/wbem/wscim/1/amt-schema/1/AMT_GeneralSettings
+- `http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_LogicalDisk`
+- `http://intel.com/wbem/wscim/1/amt-schema/1/AMT_GeneralSettings`
 
-By default, if you do not specify this parameter, the DMTF standard resource URI http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/ is used and the class name is appended to it.
+By default, if you do not specify this parameter, the DMTF standard resource URI
+`http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/` is used and the class name is appended to it.
 
-ResourceURI can only be used with CIM sessions created using the WSMan protocol, or when specifying the ComputerName parameter, which creates a CIM session using WSMan.
-If you specify this parameter without specifying the ComputerName parameter, or if you specify a CIM session created using DCOM protocol, you will get an error, because the DCOM protocol does not support the ResourceURI parameter.
+ResourceURI can only be used with CIM sessions created using the WSMan protocol, or when specifying
+the ComputerName parameter, which creates a CIM session using WSMan. If you specify this parameter
+without specifying the ComputerName parameter, or if you specify a CIM session created using DCOM
+protocol, you will get an error, because the DCOM protocol does not support the ResourceURI
+parameter.
 
-If both the ResourceUri parameter and the Filter parameter are specified, the Filter parameter is ignored.
+If both the ResourceUri parameter and the Filter parameter are specified, the Filter parameter is
+ignored.
 
 ```yaml
 Type: Uri
@@ -276,8 +290,9 @@ Accept wildcard characters: False
 ```
 
 ### CommonParameters
-This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable.
-For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216).
+This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
+-InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose,
+-WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).
 
 ## INPUTS
 

reference/3.0/CimCmdlets/Get-CimSession.md

@@ -33,7 +33,7 @@ Get-CimSession -Name <String[]> [<CommonParameters>]
 ```
 
 ## DESCRIPTION
-The Get-CimSession cmdlet gets the CIM session objects created in the current Windows PowerShell® session.
+The Get-CimSession cmdlet gets the CIM session objects created in the current Windows PowerShell session.
 
 If used without any parameters, the cmdlet gets all of the CIM sessions created in the current Windows PowerShell session.
 You can use the parameters of Get-CimSession to get the sessions that are for particular computers, or you can identify sessions by their names, IDs, or instance IDs.

reference/3.0/CimCmdlets/Invoke-CimMethod.md

@@ -104,19 +104,20 @@ If the InputObject parameter is specified, the cmdlet works in one of the follow
 
 ## EXAMPLES
 
-### Example 1: Invoke a method
+### Example 1: Invoke a method> [!NOTE]
+> Information the user should notice even if skimming
 
 ```powershell
-PS C:\>Invoke-CimMethod -Query ꞌselect * from Win32_Process where name like "notepad%"ꞌ -MethodName "Terminate"
+PS C:\>Invoke-CimMethod -Query 'select * from Win32_Process where name like "notepad%"' -MethodName "Terminate"
 ```
 
 This command invokes the method named Terminate on the CIM class named Win32_Process. The CIM class
-is retrieved by the query "Select * from Win32_Process where name like ꞌnotepad%ꞌ".
+is retrieved by the query "Select * from Win32_Process where name like 'notepad%'".
 
 ### Example 2: Invoke a method using CIM instance object
 
 ```powershell
-PS C:\>$x = Get-CimInstance -Query ꞌSelect * from Win32_Process where name like "notepad%"ꞌ
+PS C:\>$x = Get-CimInstance -Query 'Select * from Win32_Process where name like "notepad%"'
 PS C:\>Invoke-CimMethod -InputObject $x -MethodName GetOwner
 ```
 
@@ -135,7 +136,7 @@ This command invokes the static method Create on the class named Win32_Process,
 ### Example 4: Invoke a method using arguments
 
 ```powershell
-PS C:\>Invoke-CimMethod -ClassName Win32_Process -MethodName "Create" -Arguments @{ CommandLine = ꞌnotepad.exeꞌ; CurrentDirectory = "C:\windows\system32" }
+PS C:\>Invoke-CimMethod -ClassName Win32_Process -MethodName "Create" -Arguments @{ CommandLine = 'notepad.exe'; CurrentDirectory = "C:\windows\system32" }
 ```
 
 This command invokes the method named Create by using the Arguments parameter.
@@ -144,7 +145,7 @@ This command invokes the method named Create by using the Arguments parameter.
 
 ```powershell
 PS C:\>$c = Get-CimClass -ClassName Win32_Process
-PS C:\>Invoke-CimMethod -CimClass $c -MethodName "xyz" -Arguments @{ CommandLine = ꞌnotepad.exeꞌ }
+PS C:\>Invoke-CimMethod -CimClass $c -MethodName "xyz" -Arguments @{ CommandLine = 'notepad.exe' }
 ```
 
 This set of commands performs client-side validation for the method named xyz by passing a CimClass

reference/3.0/CimCmdlets/Remove-CimInstance.md

@@ -41,16 +41,16 @@ The Remove-CimInstance cmdlet removes a CIM instance from a CIM server.
 
 You can specify the CIM instance to remove by using either a CIM instance object retrieved by the Get-CimInstance cmdlet, or by specifying a query.
 
-If the InputObject parameter is not specified, the cmdlet works in one of the following ways: 
+If the InputObject parameter is not specified, the cmdlet works in one of the following ways:
 
---If neither the ComputerName parameter nor the CimSession parameter is specified, then this cmdlet works on local Windows Management Instrumentation (WMI) using a Component Object Model (COM) session. 
+--If neither the ComputerName parameter nor the CimSession parameter is specified, then this cmdlet works on local Windows Management Instrumentation (WMI) using a Component Object Model (COM) session.
 --If either the ComputerName parameter or the CimSession parameter is specified, then this cmdlet works against the CIM server specified by either the ComputerName parameter or the CimSession parameter.
 
 ## EXAMPLES
 
 ### Example 1: Remove the CIM instance
 ```
-PS C:\>Remove-CimInstance -Query 'Select * from Win32_Environment where name LIKE "testvar%"ꞌ
+PS C:\>Remove-CimInstance -Query 'Select * from Win32_Environment where name LIKE "testvar%"'
 ```
 
 This command removes the CIM instances that start with the character string testvar from the class named Win32_Environment using the Query parameter.
@@ -125,7 +125,7 @@ Accept wildcard characters: False
 ```
 
 ### -InputObject
-Specifies a CIM instance object to be removed from the CIM server. 
+Specifies a CIM instance object to be removed from the CIM server.
 Note: The input object passed to the cmdlet is not changed, only the instance in the CIM server is removed.
 
 ```yaml
@@ -143,7 +143,7 @@ Accept wildcard characters: False
 ### -Namespace
 Specifies the namespace for the CIM operation.
 
-The default namespace is root/cimv2. 
+The default namespace is root/cimv2.
 NOTE: You can use tab completion to browse the list of namespaces, because PowerShell gets a list of namespaces from the local WMI server to provide the list of namespaces.
 
 ```yaml
@@ -220,13 +220,13 @@ Specifies the resource uniform resource identifier (URI) of the resource class o
 The URI is used to identify a specific type of resource, such as disks or processes, on a computer.
 
 A URI consists of a prefix and a path to a resource.
-For example: 
+For example:
 
 http://schemas.microsoft.com/wbem/wsman/1/wmi/root/cimv2/Win32_LogicalDisk
 http://intel.com/wbem/wscim/1/amt-schema/1/AMT_GeneralSettings
 
 
-                        
+
 By default, if you do not specify this parameter, the DMTF standard resource URI http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/ is used and the class name is appended to it.
 
 ResourceURI can only be used with CIM sessions created using the WSMan protocol, or when specifying the ComputerName parameter, which creates a CIM session using WSMan.

reference/3.0/ISE/ISE.md

@@ -13,7 +13,7 @@ Module Name:  ISE
 
 ## Description
 
-This section contains the help topics for the cmdlets that are installed with the Windows PowerShell® Integrated Scripting Environment (ISE) module.
+This section contains the help topics for the cmdlets that are installed with the Windows PowerShell Integrated Scripting Environment (ISE) module.
 The Windows PowerShell ISE module contains cmdlets that add features to Windows PowerShell ISE.
 
 ## ISE Cmdlets

reference/3.0/ISE/Import-IseSnippet.md

@@ -30,7 +30,7 @@ Import-IseSnippet [-Recurse] -Module <String> [-ListAvailable] [<CommonParameter
 
 The **Import-IseSnippet** cmdlet imports reusable text "snippets" from a module or a directory into the current session.
 The snippets are immediately available for use in Windows PowerShell ISE.
-This cmdlet works only in Windows PowerShell® Integrated Scripting Environment (ISE).
+This cmdlet works only in Windows PowerShell Integrated Scripting Environment (ISE).
 
 To view and use the imported snippets, from the Windows PowerShell ISEEdit menu, click Start Snippets or press Ctrl + J.
 

reference/3.0/Microsoft.PowerShell.Core/About/about_Automatic_Variables.md

@@ -270,7 +270,7 @@ can use it in scripts like the following one, which would not work if `$null`
 were ignored.
 
 ```powershell
-$calendar = @($null, $null, “Meeting”, $null, $null, “Team Lunch”, $null)
+$calendar = @($null, $null, "Meeting", $null, $null, "Team Lunch", $null)
 $days = "Sunday","Monday","Tuesday","Wednesday","Thursday",
         "Friday","Saturday"
 $currentDay = 0

reference/3.0/Microsoft.PowerShell.Core/About/about_CommonParameters.md

@@ -188,7 +188,7 @@ Valid values:
 
 - Suspend: Automatically suspends a workflow job after a Write-Information
   command is carried out, to allow users to see the messages before
-  continuing. The workflow can be resumed at the user’s discretion.
+  continuing. The workflow can be resumed at the user's discretion.
 
 - SilentlyContinue: No effect. The informational messages are not (Default)
   displayed, and the script continues without interruption.

reference/3.0/Microsoft.PowerShell.Core/About/about_PSSnapins.md

@@ -9,7 +9,7 @@ title:  about_PSSnapins
 
 ## SHORT DESCRIPTION
 
-Describes  Windows PowerShell® snap-ins and shows how to use and manage them.
+Describes  Windows PowerShell snap-ins and shows how to use and manage them.
 
 ## LONG DESCRIPTION