test PR

Author: v-nithyamu

articles/migrate/prepare-for-migration.md

@@ -16,11 +16,11 @@ This article describes how to prepare on-premises machines before you migrate th
 In this article, you:
 > [!div class="checklist"]
 > * Review migration limitations.
-> * Select a method for migrating VMware vSphere VMs
+> * Select a method for migrating VMware vSphere VMs.
 > * Check hypervisor and operating system requirements for machines you want to migrate.
 > * Review URL and port access for machines you want to migrate.
 > * Review changes you might need to make before you begin migration.
-> * Check Azure VMs requirements for migrated machines
+> * Check Azure VMs requirements for migrated machines.
 > * Prepare machines so you can connect to the Azure VMs after migration.
 
 
@@ -36,7 +36,7 @@ The table summarizes discovery, assessment, and migration limits for Azure Migra
 
 ## Select a VMware vSphere migration method
 
-If you're migrating VMware vSphere VMs to Azure, [compare](server-migrate-overview.md#compare-migration-methods) the agentless and agent-based migration methods, to decide what works for you.
+If you're migrating VMware vSphere VMs to Azure, [compare](server-migrate-overview.md#compare-migration-methods) the agentless and agent-based migration methods, to decide what works best for you.
 
 ## Verify hypervisor requirements
 

articles/migrate/replicate-using-expressroute.md

@@ -4,7 +4,7 @@ description: Use Azure ExpressRoute for replication with the Migration and moder
 author: vijain
 ms.author: vijain
 ms.topic: how-to
-ms.date: 12/12/2022
+ms.date: 24/04/2023
 ms.custom: engagement-fy23
 ---
 
@@ -131,9 +131,8 @@ To manually create a private DNS zone:
     1. On the **Create private DNS zone** page, fill in the required details. Enter the name of the private DNS zone as **_privatelink_.blob.core.windows.net**.
     1. On the **Review + create** tab, review and create the DNS zone.
 
-1. Link the private DNS zone to your virtual network.
-
-    The private DNS zone you created must be linked to the virtual network that the private endpoint is attached to.
+1. Link the private DNS zone to your virtual network. 
+   The private DNS zone you created must be linked to the virtual network that the private endpoint is attached to.
 
     1. Go to the private DNS zone created in the previous step, and go to virtual network links on the left side of the page. Select **+ Add**.
     1. Fill in the required details. The **Subscription** and **Virtual network** fields must be filled with the corresponding details of the virtual network where your private endpoint is attached. The other fields can be left as is.