3/24/2025 PM Publish

reference/5.1/CimCmdlets/Get-CimAssociatedInstance.md

@@ -57,7 +57,7 @@ $disk = Get-CimInstance -ClassName Win32_LogicalDisk -KeyOnly
 Get-CimAssociatedInstance -InputObject $disk[1]
 ```
 
-This set of commands retrieves the instances of the class named Win32_LogicalDisk and stores the
+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.
@@ -200,7 +200,7 @@ Accept wildcard characters: False
 
 ### -Namespace
 
-Specifies the namespace for the CIM operation. The default namespace is root/cimv2.
+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 PowerShell gets a list of
@@ -254,11 +254,11 @@ A URI consists of a prefix and a path to a resource. For example:
 By default, if you don't 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
+**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 get an error, because the DCOM protocol doesn't support the
-**ResourceURI** parameter.
+**ResourceUri** parameter.
 
 If both the **ResourceUri** parameter and the **Filter** parameter are specified, the **Filter**
 parameter is ignored.
@@ -284,7 +284,7 @@ name.
 By default, the value of this parameter is null, and all associated CIM instances are returned.
 
 You can filter the association results to match a specific class name. Filtering happens on the
-server. If this parameter isn't specified, `Get-CIMAssociatedInstance` returns all existing
+server. If this parameter isn't specified, `Get-CimAssociatedInstance` returns all existing
 associations. For example, if class A is associated with classes B, C and D, then this parameter can
 be used to restrict the output to a specific type (B, C or D).
 

reference/5.1/CimCmdlets/Get-CimClass.md

@@ -41,18 +41,18 @@ instance, CIM classes do not contain the CIM session or computer name from which
 
 ### Example 1: Get all the class definitions
 
-This example gets all the class definitions under the namespace **root/cimv2**.
+This example gets all the class definitions under the namespace **root/CIMV2**.
 
 ```powershell
 Get-CimClass
 ```
 
 ### Example 2: Get the classes with a specific name
 
-This example gets the classes that contain the word **disk** in their names.
+This example gets the classes that contain the word **Disk** in their names.
 
 ```powershell
-Get-CimClass -ClassName *disk*
+Get-CimClass -ClassName *Disk*
 ```
 
 ### Example 3: Get the classes with a specific method name
@@ -85,26 +85,26 @@ Get-CimClass -ClassName Win32*Disk* -QualifierName Association
 ### Example 6: Get the class definitions from a specific namespace
 
 This example gets the class definitions that contain the word **Net** in their names from the
-specified namespace **root/standardCimv2**.
+specified namespace **root/StandardCimv2**.
 
 ```powershell
-Get-CimClass -Namespace root/standardCimv2 -ClassName *Net*
+Get-CimClass -Namespace root/StandardCimv2 -ClassName *Net*
 ```
 
 ### Example 7: Get the class definitions from a remote server
 
-This example gets the class definitions that contain the word **disk** in their names from the
+This example gets the class definitions that contain the word **Disk** in their names from the
 specified remote servers **Server01** and **Server02**.
 
 ```powershell
-Get-CimClass -ClassName *disk* -ComputerName Server01, Server02
+Get-CimClass -ClassName *Disk* -ComputerName Server01, Server02
 ```
 
 ### Example 8: Get the classes by using a CIM session
 
 ```powershell
 $s = New-CimSession -ComputerName Server01, Server02
-Get-CimClass -ClassName *disk* -CimSession $s
+Get-CimClass -ClassName *Disk* -CimSession $s
 ```
 
 This set of commands creates a session with multiple computers and stores it into a variable `$s`
@@ -193,7 +193,7 @@ Accept wildcard characters: True
 
 ### -Namespace
 
-Specifies the namespace for CIM operation. The default namespace is **root/cimv2**. You can use tab
+Specifies the namespace for CIM operation. The default namespace is **root/CIMV2**. 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.
 

reference/5.1/CimCmdlets/Get-CimInstance.md

@@ -111,7 +111,7 @@ Get-CimInstance -ClassName Win32_Process
 
 ### Example 2: Get a list of namespaces from a WMI server
 
-This example retrieves a list of namespaces under the **Root** namespace on a WMI server.
+This example retrieves a list of namespaces under the **root** namespace on a WMI server.
 
 ```powershell
 Get-CimInstance -Namespace root -ClassName __Namespace
@@ -144,7 +144,7 @@ a CIM instance to the `Get-CimInstance` cmdlet to get a particular instance.
 ```powershell
 $instance = @{
     ClassName = 'Win32_Process'
-    Namespace = 'root\cimv2'
+    Namespace = 'root/CIMV2'
     Properties = @{
         Handle = 0
     }
@@ -349,7 +349,7 @@ Accept wildcard characters: False
 
 Specifies the namespace of CIM class.
 
-The default namespace is **root/cimv2**. You can use tab completion to browse the list of
+The default namespace is **root/CIMV2**. 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.
 
@@ -463,11 +463,11 @@ A URI consists of a prefix and a path to a resource. For example:
 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
+**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** parameter.
 
 If both the **ResourceUri** parameter and the **Filter** parameter are specified, the **Filter**
 parameter is ignored.

reference/5.1/CimCmdlets/Get-CimSession.md

@@ -94,7 +94,7 @@ Protocol     : WSMAN
 ### Example 3: Get a list of CIM sessions and then format the list
 
 This example gets all CIM sessions in the current PowerShell session and displays a table containing
-only the **ComputerName** and **InstanceID** properties.
+only the **ComputerName** and **InstanceId** properties.
 
 ```powershell
 Get-CimSession | Format-Table -Property ComputerName, InstanceId
@@ -109,7 +109,7 @@ Server02     c0095981-52c5-4e7f-a5bb-c4c680541710
 
 ### Example 4: Get all the CIM sessions that have specific names
 
-This example gets all CIM sessions that have names that begin with **serv**.
+This example gets all CIM sessions that have names that begin with **Serv**.
 
 ```powershell
 Get-CimSession -ComputerName Serv*

reference/5.1/CimCmdlets/Invoke-CimMethod.md

@@ -154,12 +154,12 @@ Invoke-CimMethod -ClassName Win32_Process -MethodName "Create" -Arguments @{
 
 ### Example 4: Client-side validation
 
-This example performs client-side validation for the **xyz** method by passing a **CimClass** object
+This example performs client-side validation for the **Foo** method by passing a **CimClass** object
 to `Invoke-CimMethod`.
 
 ```powershell
 $c = Get-CimClass -ClassName Win32_Process
-Invoke-CimMethod -CimClass $c -MethodName "xyz" -Arguments @{CommandLine='notepad.exe'}
+Invoke-CimMethod -CimClass $c -MethodName "Foo" -Arguments @{CommandLine='notepad.exe'}
 ```
 
 ## PARAMETERS
@@ -300,7 +300,7 @@ Accept wildcard characters: False
 
 ### -Namespace
 
-Specifies the namespace for the CIM operation. The default namespace is **root/cimv2**. You can use
+Specifies the namespace for the CIM operation. The default namespace is **root/CIMV2**. 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.
 
@@ -392,12 +392,12 @@ A URI consists of a prefix and a path to a resource. For example:
 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
+**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.
 
 When you specify this parameter without specifying the **ComputerName** parameter, or when you
 specify a CIM session created using DCOM protocol, you get an error. The DCOM protocol does not
-support the **ResourceURI** parameter.
+support the **ResourceUri** parameter.
 
 If both the **ResourceUri** parameter and the **Filter** parameter are specified, the **Filter**
 parameter is ignored.

reference/5.1/CimCmdlets/New-CimInstance.md

@@ -73,8 +73,8 @@ instance on the local computer.
 
 ### Example 1: Create an instance of a CIM class
 
-This example creates an instance of a CIM Class named win32_environment in the root/cimv2 namespace
-on the computer.
+This example creates an instance of a CIM Class named **Win32_Environment** in the **root/CIMV2**
+namespace on the computer.
 
 ```powershell
 $prop = @{
@@ -276,7 +276,7 @@ Accept wildcard characters: False
 
 ### -Namespace
 
-Specifies the namespace of the class for the new instance. The default namespace is **root/cimv2**.
+Specifies the namespace of the class for the new instance. The default namespace is **root/CIMV2**.
 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.
 
@@ -348,11 +348,11 @@ A URI consists of a prefix and a path to a resource. For example:
 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
+**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** parameter.
 
 If both the **ResourceUri** parameter and the **Filter** parameter are specified, the **Filter**
 parameter is ignored.

reference/5.1/CimCmdlets/New-CimSession.md

@@ -109,7 +109,7 @@ New-CimSession -ComputerName Server01 -Port 1234
 This example creates a CIM session using the Distributed COM (DCOM) protocol instead of WSMan.
 
 ```powershell
-$SessionOption = New-CimSessionOption -Protocol DCOM
+$SessionOption = New-CimSessionOption -Protocol Dcom
 New-CimSession -ComputerName Server1 -SessionOption $SessionOption
 ```
 

reference/5.1/CimCmdlets/New-CimSessionOption.md

@@ -60,7 +60,7 @@ named `$so`. The contents of the variable are then passed to the `New-CimSession
 options defined in the variable.
 
 ```powershell
-$so = New-CimSessionOption -Protocol DCOM
+$so = New-CimSessionOption -Protocol Dcom
 New-CimSession -ComputerName Server01 -SessionOption $so
 ```
 
@@ -85,7 +85,7 @@ New-CimSessionOption @option
 ### Example 3: Create a CIM session options object with the culture specified
 
 ```powershell
-New-CimSessionOption -Culture Fr-Fr -Protocol Wsman
+New-CimSessionOption -Culture fr-FR -Protocol Wsman
 ```
 
 This example specifies the culture that is used for the CIM session. By default, the culture of the
@@ -99,7 +99,7 @@ client is used when performing operations. However, the default culture can be o
 Specifies the user interface culture to use for the CIM session. Specify the value for this
 parameter using one of the following formats:
 
-- A culture name in `<languagecode2>-<country/regioncode2>` format such as "EN-US".
+- A culture name in `<languagecode2>-<country/regioncode2>` format such as "en-US".
 - A variable that contains a **CultureInfo** object.
 - A command that gets a **CultureInfo** object, such as
   [Get-Culture](../Microsoft.PowerShell.Utility/Get-Culture.md)
@@ -266,7 +266,7 @@ Accept wildcard characters: False
 
 ### -Protocol
 
-Specifies the protocol to use. The acceptable values for this parameter are: **DCOM**, **Default**,
+Specifies the protocol to use. The acceptable values for this parameter are: **Dcom**, **Default**,
 or **Wsman**.
 
 ```yaml
@@ -425,7 +425,7 @@ Accept wildcard characters: False
 Specifies the user interface culture to use for the CIM session. Specify the value for this
 parameter using one of the following formats:
 
-- A culture name in `<languagecode2>-<country/regioncode2>` format such as "EN-US".
+- A culture name in `<languagecode2>-<country/regioncode2>` format such as "en-US".
 - A variable that contains a CultureInfo object.
 - A command that gets a CultureInfo object, such as `Get-Culture`.
 

reference/5.1/CimCmdlets/Register-CimIndicationEvent.md

@@ -269,7 +269,7 @@ Accept wildcard characters: False
 
 ### -Namespace
 
-Specifies the namespace for the CIM operation. The default namespace is **root/cimv2**. You can use
+Specifies the namespace for the CIM operation. The default namespace is **root/CIMV2**. 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.
 

reference/5.1/CimCmdlets/Remove-CimInstance.md

@@ -153,7 +153,7 @@ Accept wildcard characters: False
 
 ### -Namespace
 
-Specifies the namespace for the CIM operation. The default namespace is `root/cimv2`. You can use
+Specifies the namespace for the CIM operation. The default namespace is **root/CIMV2**. 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.
 
@@ -244,11 +244,11 @@ A URI consists of a prefix and a path to a resource. For example:
 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 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 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.

reference/5.1/CimCmdlets/Set-CimInstance.md

@@ -234,9 +234,9 @@ Accept wildcard characters: False
 
 ### -Namespace
 
-Specifies the namespace for the CIM operation. The default namespace is root/cimv2. 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.
+Specifies the namespace for the CIM operation. The default namespace is **root/CIMV2**. 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
 Type: System.String
@@ -360,11 +360,11 @@ A URI consists of a prefix and a path to a resource. For example:
 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.

reference/5.1/ISE/Get-IseSnippet.md

@@ -71,7 +71,7 @@ function Parse-Snippet {
   foreach ($SnippetFile in $SnippetFiles) {
      Write-Host ""
      $Title = Select-Xml -Path $SnippetFile.FullName -Namespace $SnippetNamespace -XPath "//x:Title" |
-       ForEach-Object {$_.Node.InnerXML}
+       ForEach-Object {$_.Node.InnerXml}
      $Text = Select-Xml -Path $SnippetFile.FullName -Namespace $SnippetNamespace -XPath "//x:Script" |
        ForEach-Object {$_.Node.InnerText}
      Write-Host "Title: $Title"
@@ -83,10 +83,10 @@ function Parse-Snippet {
 ```Output
 Title: Mandatory
 Text:
-Param
+param
 (
-  [parameter(Mandatory=True)]
-  [String[]]
+  [Parameter(Mandatory=True)]
+  [string[]]
   $<ParameterName>
 )
 
@@ -138,7 +138,7 @@ This cmdlet returns a file object representing the snippet file.
 
 ## NOTES
 
-- The `New-IseSnippet` cmdlet stores new user-created snippets in unsigned .ps1xml files. As such,
+- The `New-IseSnippet` cmdlet stores new user-created snippets in unsigned `.ps1xml` files. As such,
   Windows PowerShell cannot add them to a session in which the execution policy is **AllSigned** or
   **Restricted**. In a **Restricted** or **AllSigned** session, you can create, get, and import
   unsigned user-created snippets, but you cannot use them in the session.