Merge pull request #235724 from v-nithyamu/19APR-TESTPR

Typos and Language edits_25April

Author: prmerger-automator[bot]

articles/migrate/concepts-business-case-calculation.md

@@ -85,7 +85,7 @@ It covers which servers are ideal for cloud, servers that can be decommissioned
     - **Idle servers**: These servers were on but didn't deliver business value by having their CPU and memory utilization below 5% and network utilization below 2%.
 - **Decommission**: These servers were expected to deliver business value, but didn't and can be decommissioned on-premises and recommended to not migrate to Azure:
     - **Zombie**: The CPU, memory and network utilization were 0% with no performance data collection issues.
-- These servers were on but do not have adequate metrics available:
+- These servers were on but don't have adequate metrics available:
     - **Unknown**: Many servers can land in this section if the discovery is still ongoing or has some unaddressed discovery issues.
 
 ## What comprises a business case?
@@ -103,17 +103,17 @@ There are four major reports that you need to review:
 
 ## What's in a business case?
 
-Here's what's included in a Business case:
+Here's what's included in a business case:
 
 ### Total cost of ownership (steady state)
 
 #### On-premises cost
 
-Cost components for running on-premises servers. For TCO calculations, a one year cost is computed for following heads:
+Cost components for running on-premises servers. For TCO calculations, an annual cost is computed for the following heads:
 
  **Cost heads** | **Category** | **Component** | **Logic** |
  --- | --- | --- | --- |
-| Compute | Hardware | Server Hardware (Host machines) | Total hardware acquisition cost is calculated using a cost per core linear regression formula : Cost per core = 16.232*(Hyperthreaded core: memory in GB ratio) + 113.87. Hyperthreaded cores = 2*(cores) 
+| Compute | Hardware | Server Hardware (Host machines) | Total hardware acquisition cost is calculated using a cost per core linear regression formula: Cost per core = 16.232*(Hyperthreaded core: memory in GB ratio) + 113.87. Hyperthreaded cores = 2*(cores) 
 |     | Software - SQL Server licensing | License cost | Calculated per two core pack license pricing of 2019 Enterprise or Standard. |
 |     |     | Software Assurance | Calculated per year as in settings. |
 |     | Software - Windows Server licensing | License cost | Calculated per two corepack license pricing of Windows Server. |

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

@@ -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.