Doc updates

Author: Farha-Bano

articles/azure-arc/vmware-vsphere/enable-guest-management-at-scale.md

@@ -26,15 +26,15 @@ Ensure the following before you install Arc agents at scale for VMware VMs:
 - All the target machines are:
     - Powered on and the resource bridge has network connectivity to the host running the VM.
     - Running a [supported operating system](../servers/prerequisites.md#supported-operating-systems).c
-    - VMware tools are installed on the machines. If VMware tools aren't installed, the enable guest management operation is grayed out in the portal.  
+    - VMware tools are installed on the machines. If VMware tools aren't installed, enable guest management operation is grayed out in the portal.  
         >[!Note]
         >You can use the [out-of-band method](./enable-guest-management-at-scale.md#approach-d-install-arc-agents-at-scale-using-out-of-band-approach) to install Arc agents if VMware tools aren't installed.  
     - Able to connect through the firewall to communicate over the internet, and [these URLs](../servers/network-requirements.md#urls) aren't blocked.
 
    > [!NOTE]
    > If you're using a Linux VM, the account must not prompt for login on sudo commands. To override the prompt, from a terminal, run `sudo visudo`, and add `<username> ALL=(ALL) NOPASSWD:ALL` at the end of the file. Ensure you replace `<username>`. <br> <br>If your VM template has these changes incorporated, you won't need to do this for the VM created from that template.
 
-### Approach A: Install Arc agents at scale from portal
+## Approach A: Install Arc agents at scale from portal
 
 An admin can install agents for multiple machines from the Azure portal if the machines share the same administrator credentials.
 
@@ -56,7 +56,7 @@ An admin can install agents for multiple machines from the Azure portal if the m
 > [!NOTE]
 > For Windows VMs, the account must be part of local administrator group; and for Linux VM, it must be a root account.
 
-### Approach B: Install Arc agents using AzCLI commands
+## Approach B: Install Arc agents using AzCLI commands
 
 The following Azure CLI commands can be used to install Arc agents.  
 
@@ -74,11 +74,11 @@ az connectedvmware vm guest-agent enable --password
                                          [--no-wait]
 ```
 
-### Approach C: Install Arc agents at scale using helper script
+## Approach C: Install Arc agents at scale using helper script
 
 Arc agent installation can be automated using the helper script built using the AzCLI command provided [here](./enable-guest-management-at-scale.md#approach-b-install-arc-agents-using-azcli-commands). Download this [helper script](https://aka.ms/arcvmwarebatchenable) to enable VMs and install Arc agents at scale. In a single ARM deployment, the helper script can enable and install Arc agents on 200 VMs.  
 
-#### Features of the script
+### Features of the script
 
 - Creates a log file (vmware-batch.log) for tracking its operations.
 
@@ -94,15 +94,15 @@ Arc agent installation can be automated using the helper script built using the
 
 Before running this script, install az cli and the connectedvmware extension. 
 
-#### Prerequisites 
+### Prerequisites 
 
 Before running this script, install: 
 
 - Azure CLI from [here](/cli/azure/install-azure-cli).
 
 - The `connectedvmware` extension for Azure CLI: Install it by running `az extension add --name connectedvmware`. 
 
-## Usage 
+### Usage 
 
 1. Download the script to your local machine. 
 
@@ -112,7 +112,7 @@ Before running this script, install:
 
 4. Run the script with the required parameters. For example, `.\arcvmware-batch-enablement.ps1 -VCenterId "<vCenterId>" -EnableGuestManagement -VMCountPerDeployment 3 -DryRun`. Replace `<vCenterId>` with the ARM ID of your vCenter. 
 
-## Parameters
+### Parameters
 
 - `VCenterId`: The ARM ID of the vCenter where the VMs are located. 
 
@@ -122,7 +122,7 @@ Before running this script, install:
 
 - `DryRun`: If this switch is specified, the script will only create the ARM deployment files. Else, the script will also deploy the ARM deployments. 
 
-## Running as a Cron Job 
+### Running as a Cron Job 
 
 You can set up this script to run as a cron job using the Windows Task Scheduler. Here's a sample script to create a scheduled task: 
 
@@ -140,11 +140,11 @@ To unregister the task, run the following command:
 Unregister-ScheduledTask -TaskName "EnableVMs"
 ```
 
-### Approach D: Install Arc agents at scale using out-of-band approach 
+## Approach D: Install Arc agents at scale using out-of-band approach 
 
-Arc agents can be installed directly on machines without relying on VMware tools or APIs. By following the out-of-band approach, initially onboard the machines as Arc-enabled Server resources with Resource type as Microsoft.HybridCompute/machines. After that, perform **Link to vCenter** operation to update the machine's Kind property as VMware, enabling virtual lifecycle operations.  
+Arc agents can be installed directly on machines without relying on VMware tools or APIs. By following the out-of-band approach, first onboard the machines as Arc-enabled Server resources with Resource type as Microsoft.HybridCompute/machines. After that, perform **Link to vCenter** operation to update the machine's Kind property as VMware, enabling virtual lifecycle operations.  
 
-a. **Connect the machines as Arc-enabled Server resources:** Install Arc agents using Arc-enabled Server scripts. 
+1. **Connect the machines as Arc-enabled Server resources:** Install Arc agents using Arc-enabled Server scripts. 
 
 You can use any of the following automation approaches to install Arc agents at scale:
 
@@ -154,7 +154,7 @@ You can use any of the following automation approaches to install Arc agents at
 - [Install Arc agents at scale using Group policy](../servers/onboard-group-policy-powershell.md).
 - [Install Arc agents at scale using Ansible playbook](../servers/onboard-ansible-playbooks.md).
 
-b. **Link Arc-enabled Server resources to the vCenter:** The following commands will update the Kind property of Hybrid Compute machines as **VMware**. Linking the machines to vCenter will enable virtual lifecycle operations and power cycle operations (start, stop, etc.) on the machines.  
+2. **Link Arc-enabled Server resources to the vCenter:** The following commands will update the Kind property of Hybrid Compute machines as **VMware**. Linking the machines to vCenter will enable virtual lifecycle operations and power cycle operations (start, stop, etc.) on the machines.  
 
 - The following command scans all the Arc for Server machines that belong to the vCenter in the specified subscription and links the machines with that vCenter.