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

Author: rvandenbedem

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

@@ -9,7 +9,7 @@ ms.custom: engagement-fy23
 
 # Migrate Microsoft SQL Server Standalone to Azure VMware Solution
 
-In this article, you’ll learn how to migrate Microsoft SQL Server standalone to Azure VMware Solution. 
+In this article, you learn how to migrate Microsoft SQL Server standalone to Azure VMware Solution. 
 
 When migrating Microsoft SQL Server Standalone to Azure VMware Solution, VMware HCX offers two migration profiles that can be used:
 
@@ -36,15 +36,15 @@ Microsoft SQL Server (2019 and 2022) were tested with Windows Server (2019 and 2
 
 ## Downtime considerations
 
-Predicting downtime during a migration will depend upon the size of the database to be migrated and the speed of the private network connection to Azure cloud. Migration of SQL Server standalone instance does not require database downtime since it will be done using the VMware HCX vMotion mechanism. We recommend the migration during off-peak hours with an pre-approved change window.
+Predicting downtime during a migration depends upon the size of the database to be migrated and the speed of the private network connection to Azure cloud. Migration of SQL Server standalone instance doesn't require database downtime since it will be done using the VMware HCX vMotion mechanism. We recommend the migration during off-peak hours with an pre-approved change window.
 
 This table indicates the estimated downtime for each Microsoft SQL Server topology.
 
 | **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 will be shut down and migrated using VMware HCX Cold Migration. Downtime duration depends upon database size and private network speed to Azure cloud. |
+| **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
 
@@ -53,19 +53,17 @@ This table indicates the estimated downtime for each Microsoft SQL Server topolo
    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 if you want to place the VM in a specific folder, this is not mandatory but is recommended to separate the different workloads in your Azure VMware Solution private cloud.
+   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** and the migration will start. 
+   a. 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.  
 
-   
-
     :::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":::  
 
 ## Next steps