Update migrate-sql-server-standalone-cluster.md

Fixed instruction numbering.

Author: rvandenbedem

articles/azure-vmware/migrate-sql-server-standalone-cluster.md

@@ -3,7 +3,7 @@ title: Migrate Microsoft SQL Server Standalone to Azure VMware Solution
 description: Learn how to migrate Microsoft SQL Server Standalone to Azure VMware Solution.
 ms.topic: how-to
 ms.service: azure-vmware
-ms.date: 3/17/2023
+ms.date: 3/20/2023
 ms.custom: engagement-fy23
 ---
 
@@ -42,27 +42,27 @@ This table indicates the estimated downtime for each Microsoft SQL Server topolo
 
 | **Scenario** | **Downtime expected** | **Notes** |
 |:---|:-----|:-----|
-| **Standalone instance** | LOW | Migration is done using VMware vMotion, the DB is available during migration time, but it isn't recommended to commit any critical data during it. |
-| **Always-On Availability Group** | LOW | The primary replica will always be available during the migration of the first secondary replica and the secondary replica will become the primary after the initial failover to Azure. |
-| **Failover Cluster Instance** | HIGH | All nodes of the cluster are shutdown and migrated using VMware HCX Cold Migration. Downtime duration depends upon database size and private network speed to Azure cloud. |
+| **Standalone instance** | Low | Migration is done using VMware vMotion, the DB is available during migration time, but it isn't recommended to commit any critical data during it. |
+| **Always-On Availability Group** | Low | The primary replica will always be available during the migration of the first secondary replica and the secondary replica will become the primary after the initial failover to Azure. |
+| **Failover Cluster Instance** | High | All nodes of the cluster are shutdown and migrated using VMware HCX Cold Migration. Downtime duration depends upon database size and private network speed to Azure cloud. |
 
 ## Migrate Microsoft SQL Server standalone
 
 1. Log into your on-premises **vCenter Server** and access the VMware HCX plugin. 
 1. Under **Services** select **Migration** > **Migrate**. 
-   a. Select the Microsoft SQL Server virtual machine.
-   a. Set the vSphere cluster in the remote private cloud of the migrated SQL cluster as the **Compute Container**.
-   a. Select the vSAN Datastore as remote storage.
-   a. Select a folder. This isn't mandatory, but we recommended separating the different workloads in your Azure VMware Solution private cloud.
-   a. Keep **Same format as source**.
-   a. Select **vMotion** as Migration profile. 
-   a. In **Extended Options** select **Migrate Custom Attributes**.
-   a. Verify that on-premises network segments have the correct remote stretched segment in Azure VMware Solution.
-   a. Select **Validate** and ensure that all checks are completed with pass status. 
-   a. Select **Go** to start the migration. 
+   - Select the Microsoft SQL Server virtual machine.
+   - Set the vSphere cluster in the remote private cloud of the migrated SQL cluster as the **Compute Container**.
+   - Select the vSAN Datastore as remote storage.
+   - Select a folder. This isn't mandatory, but we recommended separating the different workloads in your Azure VMware Solution private cloud.
+   - Keep **Same format as source**.
+   - Select **vMotion** as Migration profile. 
+   - In **Extended Options** select **Migrate Custom Attributes**.
+   - Verify that on-premises network segments have the correct remote stretched segment in Azure VMware Solution.
+   - Select **Validate** and ensure that all checks are completed with pass status. 
+   - Select **Go** to start the migration. 
 1. After the migration has completed, access the virtual machine using VMware Remote Console in the vSphere Client.
-   a. Verify the network configuration and check connectivity both with on-premises and Azure VMware Solution resources.
-   a. Using SQL Server Management Studio verify you can access the database.  
+   - Verify the network configuration and check connectivity both with on-premises and Azure VMware Solution resources.
+   - Using SQL Server Management Studio verify you can access the database.  
 
     :::image type="content" source="media/sql-server-hybrid-benefit/sql-standalone-1.png" alt-text="Diagram showing a SQL Server Management Studio connection to the migrated database." border="false" lightbox="media/sql-server-hybrid-benefit/sql-standalone-1.png":::