From 483df7a43b591170088e38dfb6cabdb550307936 Mon Sep 17 00:00:00 2001
From: jodeffen <153466573+jodeffen@users.noreply.github.com>
Date: Tue, 30 Jul 2024 13:39:47 -0400
Subject: [PATCH] Correction on wording used in troubleshooting steps.

Step 2 stated to run a command on every disk but, the only command was "Get-ClusterGroup". The command to run on the disks is actually in Step 3. Fixed the wording in the instructions to be more clear.
---
 .../storage/storage-spaces/troubleshooting-storage-spaces.md  | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/WindowsServerDocs/storage/storage-spaces/troubleshooting-storage-spaces.md b/WindowsServerDocs/storage/storage-spaces/troubleshooting-storage-spaces.md
index dc0f460419..1aaec57494 100644
--- a/WindowsServerDocs/storage/storage-spaces/troubleshooting-storage-spaces.md
+++ b/WindowsServerDocs/storage/storage-spaces/troubleshooting-storage-spaces.md
@@ -53,13 +53,13 @@ To fix this issue, follow these steps:
    Remove-ClusterSharedVolume -Name "CSV Name"
    ```
 
-1. On the node that owns the Available Storage group, run the following command on every disk that's in a no redundancy state. To identify which node the Available Storage group is on, you can run this command:
+1. Identify which node the “Available Storage” group is on using the following command:
 
    ```powershell
    Get-ClusterGroup
    ```
 
-1. Set the disk recovery action and then start the disk(s).
+1. On the node that owns the Available Storage group, run the following commands on every disk that’s in a No Redundancy state. This commands will set the disk recovery action and then start the disk(s).
    ```powershell
    Get-ClusterResource "Physical Disk Resource Name" | Set-ClusterParameter -Name DiskRecoveryAction -Value 1
    Start-ClusterResource -Name "Physical Disk Resource Name"