Merge pull request MicrosoftDocs#3202 from robinharwood/roharwoo_failoverclusters_text_formatting_4

FailoverClusters BulkFixup (4/4) - Text formatting updates

Author: michaeltlombardi

docset/winserver2022-ps/failoverclusters/Start-ClusterResource.md

@@ -2,7 +2,7 @@
 description: Use this topic to help manage Windows and Windows Server technologies with Windows PowerShell.
 external help file: Microsoft.FailoverClusters.PowerShell.dll-Help.xml
 Module Name: FailoverClusters
-ms.date: 10/21/2022
+ms.date: 11/21/2022
 online version: https://learn.microsoft.com/powershell/module/failoverclusters/start-clusterresource?view=windowsserver2022-ps&wt.mc_id=ps-gethelp
 schema: 2.0.0
 title: Start-ClusterResource
@@ -22,7 +22,7 @@ Start-ClusterResource [[-Name] <String>] [-IgnoreLocked] [-ChooseBestNode] [-Wai
 
 ## DESCRIPTION
 
-The **Start-ClusterResource** cmdlet brings a resource online in a failover cluster. Before the
+The `Start-ClusterResource` cmdlet brings a resource online in a failover cluster. Before the
 resource is brought online, any resources that it depends are brought online.
 
 ## EXAMPLES
@@ -136,7 +136,7 @@ Accept wildcard characters: False
 
 ### -Wait
 
-Specifies the time in seconds to wait for the cmdlet. If the **Wait** parameter is not specified,
+Specifies the time in seconds to wait for the cmdlet. If the **Wait** parameter isn't specified,
 then the cmdlet waits for completion. If `-Wait 0` is specified, then the call is initiated and the
 cmdlet returns without waiting.
 

docset/winserver2022-ps/failoverclusters/Stop-Cluster.md

@@ -2,7 +2,7 @@
 description: Use this topic to help manage Windows and Windows Server technologies with Windows PowerShell.
 external help file: Microsoft.FailoverClusters.PowerShell.dll-Help.xml
 Module Name: FailoverClusters
-ms.date: 10/21/2022
+ms.date: 11/21/2022
 online version: https://learn.microsoft.com/powershell/module/failoverclusters/stop-cluster?view=windowsserver2022-ps&wt.mc_id=ps-gethelp
 schema: 2.0.0
 title: Stop-Cluster
@@ -32,7 +32,7 @@ Stop-Cluster [-Force] [-Wait <Int32>] [-InputObject <PSObject>] [-WhatIf] [-Conf
 
 ## DESCRIPTION
 
-The **Stop-Cluster** cmdlet stops the Cluster service on all nodes in a failover cluster, which will
+The `Stop-Cluster` cmdlet stops the Cluster service on all nodes in a failover cluster, which will
 stop all services and applications configured in the cluster. A node can only function as part of
 the cluster when the Cluster service is running on that node.
 
@@ -126,8 +126,8 @@ Accept wildcard characters: False
 
 ### -Wait
 
-Specifies the time in seconds to wait for the cmdlet. If the *Wait* parameter is not specified, then
-the cmdlet waits for completion. If `-Wait 0` is specified, then the call is initiated and the
+Specifies the time in seconds to wait for the cmdlet. If the **Wait** parameter isn't specified,
+then the cmdlet waits for completion. If `-Wait 0` is specified, then the call is initiated and the
 cmdlet returns without waiting.
 
 ```yaml
@@ -144,7 +144,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-Shows what would happen if the cmdlet runs. The cmdlet is not run.
+Shows what would happen if the cmdlet runs. The cmdlet isn't run.
 
 ```yaml
 Type: SwitchParameter

docset/winserver2022-ps/failoverclusters/Stop-ClusterGroup.md

@@ -2,7 +2,7 @@
 description: Use this topic to help manage Windows and Windows Server technologies with Windows PowerShell.
 external help file: Microsoft.FailoverClusters.PowerShell.dll-Help.xml
 Module Name: FailoverClusters
-ms.date: 10/21/2022
+ms.date: 11/21/2022
 online version: https://learn.microsoft.com/powershell/module/failoverclusters/stop-clustergroup?view=windowsserver2022-ps&wt.mc_id=ps-gethelp
 schema: 2.0.0
 title: Stop-ClusterGroup
@@ -22,7 +22,7 @@ Stop-ClusterGroup [[-Name] <String>] [-IgnoreLocked] [-Wait <Int32>] [-InputObje
 
 ## DESCRIPTION
 
-The **Stop-ClusterGroup** cmdlet stops one or more clustered roles, also known as resource groups,
+The `Stop-ClusterGroup` cmdlet stops one or more clustered roles, also known as resource groups,
 on a failover cluster.
 
 If maintenance on a clustered role is needed, the clustered role can be stopped in an orderly
@@ -110,8 +110,8 @@ Accept wildcard characters: False
 
 ### -Wait
 
-Specifies the time in seconds to wait for the cmdlet. If the *Wait* parameter is not specified, then
-the cmdlet waits for completion. If `-Wait 0` is specified, then the call is initiated and the
+Specifies the time in seconds to wait for the cmdlet. If the **Wait** parameter isn't specified,
+then the cmdlet waits for completion. If `-Wait 0` is specified, then the call is initiated and the
 cmdlet returns without waiting.
 
 ```yaml

docset/winserver2022-ps/failoverclusters/Stop-ClusterNode.md

@@ -2,7 +2,7 @@
 description: Use this topic to help manage Windows and Windows Server technologies with Windows PowerShell.
 external help file: Microsoft.FailoverClusters.PowerShell.dll-Help.xml
 Module Name: FailoverClusters
-ms.date: 10/21/2022
+ms.date: 11/21/2022
 online version: https://learn.microsoft.com/powershell/module/failoverclusters/stop-clusternode?view=windowsserver2022-ps&wt.mc_id=ps-gethelp
 schema: 2.0.0
 title: Stop-ClusterNode
@@ -22,9 +22,9 @@ Stop-ClusterNode [[-Name] <StringCollection>] [-Wait <Int32>] [-InputObject <PSO
 
 ## DESCRIPTION
 
-The **Stop-ClusterNode** cmdlet stops the Cluster service on a node in a failover cluster. If
-stopping the node brings the cluster below quorum, the operation is not permitted. To stop the
-cluster, use the **Stop-Cluster** cmdlet instead.
+The `Stop-ClusterNode` cmdlet stops the Cluster service on a node in a failover cluster. If
+stopping the node brings the cluster below quorum, the operation isn't permitted. To stop the
+cluster, use the `Stop-Cluster` cmdlet instead.
 
 Note: This cmdlet cannot be run remotely without Credential Security Service Provider (CredSSP)
 authentication on the server computer.
@@ -122,8 +122,8 @@ Accept wildcard characters: False
 
 ### -Wait
 
-Specifies the time in seconds to wait for the cmdlet. If the *Wait* parameter is not specified, then
-the cmdlet waits for completion. If `-Wait 0` is specified, then the call is initiated and the
+Specifies the time in seconds to wait for the cmdlet. If the **Wait** parameter isn't specified,
+then the cmdlet waits for completion. If `-Wait 0` is specified, then the call is initiated and the
 cmdlet returns without waiting.
 
 ```yaml
@@ -140,7 +140,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-Shows what would happen if the cmdlet runs. The cmdlet is not run.
+Shows what would happen if the cmdlet runs. The cmdlet isn't run.
 
 ```yaml
 Type: SwitchParameter

docset/winserver2022-ps/failoverclusters/Stop-ClusterResource.md

@@ -2,7 +2,7 @@
 description: Use this topic to help manage Windows and Windows Server technologies with Windows PowerShell.
 external help file: Microsoft.FailoverClusters.PowerShell.dll-Help.xml
 Module Name: FailoverClusters
-ms.date: 10/21/2022
+ms.date: 11/21/2022
 online version: https://learn.microsoft.com/powershell/module/failoverclusters/stop-clusterresource?view=windowsserver2022-ps&wt.mc_id=ps-gethelp
 schema: 2.0.0
 title: Stop-ClusterResource
@@ -22,7 +22,7 @@ Stop-ClusterResource [[-Name] <String>] [-IgnoreLocked] [-Wait <Int32>] [-InputO
 
 ## DESCRIPTION
 
-The **Stop-ClusterResource** cmdlet takes a resource offline in a failover cluster. Before the
+The `Stop-ClusterResource` cmdlet takes a resource offline in a failover cluster. Before the
 resource is taken offline, any resources that depend on it are taken offline.
 
 ## EXAMPLES
@@ -109,8 +109,8 @@ Accept wildcard characters: False
 
 ### -Wait
 
-Specifies the time in seconds to wait for the cmdlet. If the *Wait* parameter is not specified, then
-the cmdlet waits for completion. If `-Wait 0` is specified, then the call is initiated and the
+Specifies the time in seconds to wait for the cmdlet. If the **Wait** parameter isn't specified,
+then the cmdlet waits for completion. If `-Wait 0` is specified, then the call is initiated and the
 cmdlet returns without waiting.
 
 ```yaml

docset/winserver2022-ps/failoverclusters/Suspend-ClusterNode.md

@@ -2,7 +2,7 @@
 description: Use this topic to help manage Windows and Windows Server technologies with Windows PowerShell.
 external help file: Microsoft.FailoverClusters.PowerShell.dll-Help.xml
 Module Name: FailoverClusters
-ms.date: 10/21/2022
+ms.date: 11/21/2022
 online version: https://learn.microsoft.com/powershell/module/failoverclusters/suspend-clusternode?view=windowsserver2022-ps&wt.mc_id=ps-gethelp
 schema: 2.0.0
 title: Suspend-ClusterNode
@@ -23,8 +23,8 @@ Suspend-ClusterNode [[-Name] <StringCollection>] [-Drain] [-ForceDrain] [-Wait]
 
 ## DESCRIPTION
 
-The **Suspend-ClusterNode** cmdlet suspends activity on a failover cluster node, that is, pauses the
-node. If you use the *Drain* parameter, clustered roles currently running on the node will be
+The `Suspend-ClusterNode` cmdlet suspends activity on a failover cluster node, that is, pauses the
+node. If you use the **Drain** parameter, clustered roles currently running on the node will be
 drained before the node is paused.
 
 Pausing, or suspending, a node is usually done when applying software updates to the node. If you
@@ -199,10 +199,10 @@ Accept wildcard characters: False
 
 ### -Wait
 
-Specifies the time in seconds to wait for the cmdlet. If the *Wait* parameter is not specified, then
-the call is initiated and the cmdlet returns without waiting. If specified with no value, then the
-cmdlet waits for completion. If `-Wait 0` is specified, then the call is initiated and the cmdlet
-returns without waiting.
+Specifies the time in seconds to wait for the cmdlet. If the **Wait** parameter isn't specified,
+then the call is initiated and the cmdlet returns without waiting. If specified with no value, then
+the cmdlet waits for completion. If `-Wait 0` is specified, then the call is initiated and the
+cmdlet returns without waiting.
 
 ```yaml
 Type: SwitchParameter
@@ -218,7 +218,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-Shows what would happen if the cmdlet runs. The cmdlet is not run.
+Shows what would happen if the cmdlet runs. The cmdlet isn't run.
 
 ```yaml
 Type: SwitchParameter

docset/winserver2022-ps/failoverclusters/Suspend-ClusterResource.md

@@ -2,7 +2,7 @@
 description: Use this topic to help manage Windows and Windows Server technologies with Windows PowerShell.
 external help file: Microsoft.FailoverClusters.PowerShell.dll-Help.xml
 Module Name: FailoverClusters
-ms.date: 10/21/2022
+ms.date: 11/21/2022
 online version: https://learn.microsoft.com/powershell/module/failoverclusters/suspend-clusterresource?view=windowsserver2022-ps&wt.mc_id=ps-gethelp
 schema: 2.0.0
 title: Suspend-ClusterResource
@@ -23,7 +23,7 @@ Suspend-ClusterResource [[-Name] <String>] [-VolumeName <String>] [-RedirectedAc
 
 ## DESCRIPTION
 
-The **Suspend-ClusterResource** cmdlet turns on maintenance for a disk resource or Cluster Shared
+The `Suspend-ClusterResource` cmdlet turns on maintenance for a disk resource or Cluster Shared
 Volume (CSV) so that a disk maintenance tool can be run without triggering failover.
 
 This cmdlet only applies to disks and CSVs. For Cluster Shared Volumes, turning on maintenance takes
@@ -158,7 +158,7 @@ Accept wildcard characters: False
 ### -VolumeName
 
 Specifies the name of the volume to suspend. This parameter is only applicable to CSVs. If this
-parameter is not specified, then the operation will be performed on all volumes on the CSV.
+parameter isn't specified, then the operation will be performed on all volumes on the CSV.
 
 ```yaml
 Type: String
@@ -174,7 +174,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-Shows what would happen if the cmdlet runs. The cmdlet is not run.
+Shows what would happen if the cmdlet runs. The cmdlet isn't run.
 
 ```yaml
 Type: SwitchParameter

docset/winserver2022-ps/failoverclusters/Test-Cluster.md

@@ -2,7 +2,7 @@
 description: Use this topic to help manage Windows and Windows Server technologies with Windows PowerShell.
 external help file: Microsoft.FailoverClusters.PowerShell.dll-Help.xml
 Module Name: FailoverClusters
-ms.date: 10/21/2022
+ms.date: 11/21/2022
 online version: https://learn.microsoft.com/powershell/module/failoverclusters/test-cluster?view=windowsserver2022-ps&wt.mc_id=ps-gethelp
 schema: 2.0.0
 title: Test-Cluster
@@ -143,19 +143,19 @@ Accept wildcard characters: False
 Specifies the disk number or disks for which to run the cmdlet. If the specified disk is online and
 is assigned to a clustered role or Cluster Shared Volume, you must also specify the **Force**
 parameter to take the disk offline for the duration of the storage tests. Otherwise, the specified
-disk must be offline before the cmdlet is run. If the **Disk** parameter is not specified, storage
+disk must be offline before the cmdlet is run. If the **Disk** parameter isn't specified, storage
 tests run on all disks that are available for use in the cluster or that are in the cluster resource
 offline or failed state.
 
 The acceptable values for this parameter are:
 
-- **Int32, Int64, Uint32, Uint64**. A number that represents a master boot record (MBR) signature of
+- **Int32, Int64, Uint32, or Uint64**. A number that represents a master boot record (MBR) signature of
   the disk.
 - **System.String**. A string that represents a master boot record (MBR) signature of the disk,
   hexadecimal format is supported.
 - **System.String**. A string that represents the GUID of a GPT disk.
 - **ClusterResource**. A cluster resource object that represents a clustered disk.
-- **CimInstance#MSFT_Disk**. An object returned from Get-Disk, from the Windows PowerShell storage
+- **CimInstance#MSFT_Disk**. An object returned from `Get-Disk`, from the Windows PowerShell storage
   module.
 
 ```yaml
@@ -173,8 +173,8 @@ Accept wildcard characters: False
 ### -Force
 
 Runs the cmdlet without prompting for confirmation. By default the cmdlet will ask for confirmation
-from the user before proceeding. When combined with the **Disk** or **Pool** parameters, the disks or
-storage pool is taken offline for the duration of the storage tests.
+from the user before proceeding. When combined with the **Disk** or **Pool** parameters, the disks
+or storage pool is taken offline for the duration of the storage tests.
 
 ```yaml
 Type: SwitchParameter
@@ -278,7 +278,7 @@ storage pool is online and a virtual disk in the storage pool is assigned to a c
 Cluster Shared Volume, you must also specify the **Force** parameter to take the storage pool
 offline for the duration of the storage tests. Otherwise, command will exit with an error. The
 specified storage pool must be taken offline before running the storage tests. If the **Pool**
-parameter is not specified, storage tests run on all storage pools that are available for use in the
+parameter isn't specified, storage tests run on all storage pools that are available for use in the
 cluster or that are in the cluster resource offline or failed state.
 
 The acceptable values for this parameter are:
@@ -318,7 +318,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-Shows what would happen if the cmdlet runs. The cmdlet is not run.
+Shows what would happen if the cmdlet runs. The cmdlet isn't run.
 
 ```yaml
 Type: SwitchParameter

docset/winserver2022-ps/failoverclusters/Test-ClusterResourceFailure.md

@@ -2,7 +2,7 @@
 description: Use this topic to help manage Windows and Windows Server technologies with Windows PowerShell.
 external help file: Microsoft.FailoverClusters.PowerShell.dll-Help.xml
 Module Name: FailoverClusters
-ms.date: 10/21/2022
+ms.date: 11/21/2022
 online version: https://learn.microsoft.com/powershell/module/failoverclusters/test-clusterresourcefailure?view=windowsserver2022-ps&wt.mc_id=ps-gethelp
 schema: 2.0.0
 title: Test-ClusterResourceFailure
@@ -22,7 +22,7 @@ Test-ClusterResourceFailure [[-Name] <String>] [-InputObject <PSObject>] [-Clust
 
 ## DESCRIPTION
 
-The **Test-ClusterResourceFailure** cmdlet simulates a failure of a cluster resource.
+The `Test-ClusterResourceFailure` cmdlet simulates a failure of a cluster resource.
 
 Based on the failover and failback policies, when this cmdlet runs, the Cluster service moves the
 clustered role, or resource group, and attempts to bring the clustered resource online. This cmdlet

docset/winserver2022-ps/failoverclusters/Update-ClusterFunctionalLevel.md

@@ -2,7 +2,7 @@
 description: Use this topic to help manage Windows and Windows Server technologies with Windows PowerShell.
 external help file: Microsoft.FailoverClusters.PowerShell.dll-Help.xml
 Module Name: FailoverClusters
-ms.date: 10/21/2022
+ms.date: 11/21/2022
 online version: https://learn.microsoft.com/powershell/module/failoverclusters/update-clusterfunctionallevel?view=windowsserver2022-ps&wt.mc_id=ps-gethelp
 schema: 2.0.0
 title: Update-ClusterFunctionalLevel
@@ -22,36 +22,36 @@ Update-ClusterFunctionalLevel [-Force] [-WhatIf] [-InputObject <PSObject>] [-Clu
 
 ## DESCRIPTION
 
-The **Update-ClusterFunctionalLevel** cmdlet updates the functional level of a mixed-version
+The `Update-ClusterFunctionalLevel` cmdlet updates the functional level of a mixed-version
 cluster. You can update the cluster after all nodes have been updated.
 
 Starting with Windows Server 2016, you can add a node that runs a more recent version of the Windows
 operating system into a cluster of nodes that run a previous version of the Windows operating
-system. To add a cluster node, use the **Add-ClusterNode** cmdlet.
+system. To add a cluster node, use the `Add-ClusterNode` cmdlet.
 
 After you add a node that runs a different version of the Windows operating system, the cluster
 becomes a mixed-version cluster. You can implement a mixed-version cluster to continue to run while
 you upgrade the operating system on each node in the cluster.
 
-We recommend that you upgrade all nodes in the cluster within a month. We do not recommend using a
+We recommend that you upgrade all nodes in the cluster within a month. We don't recommend using a
 mixed-version cluster permanently.
 
 You can use this cmdlet to support a rolling operating system upgrade for a cluster. If you use
 cluster that runs Hyper-V in which all the nodes run Windows Server 2012 R2, you can upgrade the
 nodes of that cluster without downtime for your virtual machines.
 
-First, drain one cluster node by specifying the *Drain* parameter of the **Suspend-ClusterNode**
+First, drain one cluster node by specifying the **Drain** parameter of the `Suspend-ClusterNode`
 cmdlet. This cmdlet causes all virtual machines to live-migrate to one of the other hosts.
 
-Next, remove the host from the cluster by using the **Remove-ClusterNode** cmdlet.
+Next, remove the host from the cluster by using the `Remove-ClusterNode` cmdlet.
 
-Next, install a new version of the operating system. Do not perform an upgrade or in-place
+Next, install a new version of the operating system. Don't perform an upgrade or in-place
 installation.
 
 Next, add the Hyper-V role and the **Failover Clustering** feature by using the
-**Install-WindowsFeature** cmdlet. For more information, type `Get-Help Install-WindowsFeature`.
+`Install-WindowsFeature` cmdlet. For more information, type `Get-Help Install-WindowsFeature`.
 
-Finally, add the node into the cluster by using the **Add-ClusterNode** cmdlet.
+Finally, add the node into the cluster by using the `Add-ClusterNode` cmdlet.
 
 Repeat these steps for each node of the cluster.
 
@@ -67,7 +67,7 @@ cluster_17
 ```
 
 This command tests whether an update would finish successfully. Because the command includes the
-*WhatIf* common parameter, the command does not perform the update.
+**WhatIf** common parameter, the command doesn't perform the update.
 
 ### Example 2: Update a cluster functional level
 
@@ -135,7 +135,7 @@ Accept wildcard characters: False
 
 ### -WhatIf
 
-Shows what would happen if the cmdlet runs. The cmdlet is not run.
+Shows what would happen if the cmdlet runs. The cmdlet isn't run.
 
 ```yaml
 Type: SwitchParameter