spell checked

Author: jjaygbay

articles/azure-vmware/use-hcx-run-commands.md

@@ -8,27 +8,27 @@ ms.date: 04/11/2023
 ---
 
 # Use HCX Run Commands
-In this article you learn how to use HCX run commands. Use run commands to perform operations that would normally require elevated privileges through a collection of PowerShell cmdlets. This document outlines the available HCX run commands and how to use them. 
+In this article, you learn how to use HCX run commands. Use run commands to perform operations that would normally require elevated privileges through a collection of PowerShell cmdlets. This document outlines the available HCX run commands and how to use them. 
 
 This article describes two HCX commands: **Restart HCX Manager** and **Scale HCX Manager**. 
 
 ## Restart HCX Manage 
 
-This Command checks for active HCX migrations and replications. If none are found, it will restart the HCX cloud manager (HCX VM's guest OS). 
+This Command checks for active HCX migrations and replications. If none are found, it restarts the HCX cloud manager (HCX VM's guest OS). 
 
-1. Navigate to the run Command blade on in an AVS private cloud on the azure portal.
+1. Navigate to the run Command panel in an Azure VMware private cloud on the Azure portal.
 
    :::image type="content" source="media/hcx-commands/run-command-private-cloud.png" alt-text="Diagram that  lists all available Run command packages and Run commands." border="false" lightbox="media/hcx-commands/run-command-private-cloud.png":::        
 
 1. Select the **Microsoft.AVS.Management** package dropdown menu and select the **Restart-HcxManager** command. 
 1. Set parameters and select **Run**. 
 Optional run command parameters.   
 
-    If the parameters are used incorrectly, they can halt active migrations and replications as well as cause other issues. Brief description of each parameter with an example of when teach should be used.  
+    If the parameters are used incorrectly, they can halt active migrations, and replications and cause other issues. Brief description of each parameter with an example of when teach should be used.  
 
-    **Hard Reboot Parameter** - Restarts the virtual machine instead of the default of a GuestOS Reboot. This is like pulling the power plug on a machine. We do not want to risk disk corruption so this should only be used if a normal reboot fails, and we have exhausted all other options.  
+    **Hard Reboot Parameter** - Restarts the virtual machine instead of the default of a GuestOS Reboot. This command is like pulling the power plug on a machine. We don't want to risk disk corruption so this should only be used if a normal reboot fails, and we have exhausted all other options.  
 
-    **Force Parameter** - If there are ANY active HCX migrations/replications, this param will avoid the check for active HCX migrations/replications. If the Virtual machine is in a powered off state, this parameter will power the machine on.  
+    **Force Parameter** - If there are ANY active HCX migrations/replications, this parameter avoids the check for active HCX migrations/replications. If the Virtual machine is in a powered off state, this parameter powers the machine on.  
 
     **Scenario 1**: A customer has a migration that has been stuck in an active state for weeks and they need a restart of HCX for a separate issue. Without this parameter, the script will fail due to the detection of the active migration. 
     Scenario 2: The HCX Manager is powered off and the customer would like to power it back on.
@@ -38,14 +38,14 @@ Optional run command parameters.
 1. Wait for command to finish. It may take few minutes for the HCX appliance to come online. 
 
 ## Scale HCX manager  
-Use the Scale HCX manager run command to increase the resource allocation of your HCX Manager virtual machine to 8 vCPUs and 24 GB RAM from the default setting of 4 vCPUs and 12 GB RAM, facilitating scalability. 
+Use the Scale HCX manager run command to increase the resource allocation of your HCX Manager virtual machine to 8 vCPUs and 24-GB RAM from the default setting of 4 vCPUs and 12-GB RAM, ensuring scalability. 
 
 **Scenario**: Mobility Optimize Networking (MON) requires HCX  Scalability. For more details on [MON scaling](https://kb.vmware.com/s/article/88401)  
 
 >[!NOTE] 
 > HCX cloud manager will be rebooted during this operation, and this may affect any ongoing migration processes. 
 
-1. Navigate to the run Command blade on in an AVS private cloud on the azure portal. 
+1. Navigate to the run Command panel on in an AVS private cloud on the Azure portal. 
 
 1. Select the **Microsoft.AVS.Management** package dropdown menu and select the ``Set-HcxScaledCpuAndMemorySetting`` command.
 
@@ -58,7 +58,7 @@ Use the Scale HCX manager run command to increase the resource allocation of you
     >[!NOTE]
     > If this required parameter is set to false that cmdlet execution will fail. 
 
-1. Click **Run** to execute.  
+1. Select **Run** to execute.  
 This process may take between 10-15 minutes.  
 
 > [!NOTE]: