Update common-questions-server-migration.md

Author: rayne-wiselman

articles/migrate/common-questions-server-migration.md

@@ -7,55 +7,55 @@ ms.date: 02/17/2020
 
 # Azure Migrate Server Migration: Common questions
 
-This article answers common questions about the Azure Migrate:Server Migration. If you have further queries after reading this article, review these articles:
+This article answers common questions about the Azure Migrate:Server Migration tool. If you more questions after reading this article, review these articles:
 
 - [General questions](resources-faq.md) about Azure Migrate.
 - [Questions](common-questions-appliance.md) about the Azure Migrate appliance.
 - [Questions](common-questions-discovery-assessment.md) about the discovery, assessment, and dependency visualization.
-- Post quesitons on the Azure Migrate forum](https://aka.ms/AzureMigrateForum).
+- Post questions on the [Azure Migrate forum](https://aka.ms/AzureMigrateForum).
 
 
 ## How does agentless VMware replication work?
 
-The agentless replication method for VMware uses VMware snapshots, and VMware changed block tracking (CBT).
+The agentless replication method for VMware uses VMware snapshots, and VMware Changed Block Tracking (CBT).
 
-1. An initial replication cycle is scheduled when the user starts replication. In the initial replication cycle, a snapshot of the VM is taken, and this snapshot is used to replicate the VMs VMDKs (disks). 
-2. After the initial replication cycle is completed, delta replication cycles are scheduled periodically.
-    - In the delta replication cycle, a snapshot is taken, and data blocks that have changed since the previous replication cycle are replicated.
-    - VMware change block tracking is used to determine blocks that have changed since the last cycle.
-    - The frequency of the periodic replication cycles is automatically managed by the service depending on how many other VMs/disks are concurrently replicating off the same datastore. In ideal conditions it will eventually converge to 1 cycle per hour per VM.
+1. When you start replication, an initial replication cycle is scheduled. In the initial cycle, a snapshot of the VM is taken. This snapshot is used to replicate the VMs VMDKs (disks). 
+2. After the initial replication cycle finishes, delta replication cycles are scheduled periodically.
+    - During delta replication, a snapshot is taken, and data blocks that have changed since the previous replication cycle are replicated.
+    - VMware CBT is used to determine blocks that have changed since the last cycle.
+    - The frequency of the periodic replication cycles is automatically managed by the Azure Migrate, depending on how many other VMs/disks are concurrently replicating from the same datastore. In ideal conditions, replication eventually converges to one cycle per hour for each VM.
 
-When you migrate, an on-demand replication cycle is scheduled for the VM to capture any remaining data. You can choose to Shut down the VM as part of the migration to ensure zero data loss and application consistency.
+When you migrate, an on-demand replication cycle is scheduled for the machine, to capture any remaining data. You can choose to shut down the machine during migration, to ensure zero data loss and application consistency.
 
-## Why is the resynchronization option not exposed in agentless stack?
+## Why isn't resynchronization exposed?
 
-In agentless stack, in every delta cycle, we transfer the diff between the current snapshot and the previous snapshot that we had taken. Since it is always a diff between snapshots, this gives the advantage of folding the data (i.e. if a particular sector is written 'n' times between the snapshots, we only need to transfer the last write, as we are interested only in the last sync). This is different from the agent-based stack in which we track every write and apply them. This means every delta cycle is a resynchronization. Hence, there is no resynchronization option exposed. 
+During agentless migration, in every delta cycle the difference between the current snapshot and the previously taken snapshot is written. Since it's always the difference between snapshots, folding data in. So that if a particular sector is written N times between snapshots, only the last write needs to be transferred, as we are interested only in the last sync. This differs from agent-based replication, where we track and apply every write. This means every delta cycle is a resynchronization. Hence, there is no resynchronization option exposed. If ever the disks aren't synchronized because of a failure, it's fixed in the next cycle. 
 
-If ever the disks are out of sync because of a failure, it is fixed in the next cycle. 
+## How does churn rate impact agentless replication?
 
-## What is the impact of churn rate if I use agentless replication?
-
-Since the stack is dependent on the data being folded, more than the churn rate, the churn pattern is what matters in this stack. A pattern in which a file is being written again and again doesn’t have much impact. However, a pattern in which every other sector is written will cause high churn in the next cycle. Since we minimize the amount of data we transfer, we allow the data to fold as much as possible before scheduling the next cycle.  
+Since agentless replication folds date, the chun pattern is more important that the churn rate. When a file is written again and again, the rate doesn’t have much impact. However, a pattern in which every other sector is written causes high churn in the next cycle. Since we minimize the amount of data we transfer, we allow the data to fold as much as possible before scheduling the next cycle.  
 
 ## How frequently is a replication cycle scheduled?
 
-The formula to schedule the next replication cycle is this: (Previous cycle time / 2) or 1 hour whichever is higher. For example, if a VM took four hours for a delta cycle, we'll schedule its next cycle in 2 hours and not in the next hour. This is different when the cycle is immediately after IR, where we schedule the first delta cycle immediately.
+The formula to schedule the next replication cycle: (Previous cycle time / 2) or 1 hourw, hichever is higher.
+
+For example, if a VM takes four hours for a delta cycle, the next cycle is scheduled in two hours, and not in the next hour. This is differs immediately after initial replication, where the first delta cycle is scheduled immediately.
 
-## What is the impact on performance of vCenter Server or ESXi host while using agentless replication?
+## How does agentless replication impact VMware servers?
 
-Since agentless replication uses snapshots, there will be IOPs consumption on storage, and customers will need some IOPs headroom on the storage. We don’t recommend using this stack on storage/IOPs constrained environment.
+There is some performance mpact on vCenter Server/ESXi hosts. Since agentless replication uses snapshots, it consumes IOPs on storage, and some IOPS storage bandwidth is needed. We don’t recommend using agentless replication if there are constraints on storage/IOPs in your environment.
 
-## Does agentless migration stack support migration of UEFI VMs to Azure Gen 2 VMs?
+## Can I do agentless migration of UEFI VMs to Azure Gen 2?
 
-No, you must use Azure Site Recovery to migrate these VMs to Gen 2 Azure VMs. 
+No. Use Azure Site Recovery to migrate these VMs to Gen 2 Azure VMs. 
 
-## Can I pin my VMs to Azure Availability Zones when I migrate?
+## Can I pin VMs to Azure Availability Zones when I migrate?
 
-No, support for Azure Availability Zones is not there.
+No, Azure Availability Zones aren't supported.
 
 ## Which transport protocol is used by Azure Migrate during replication?
 
-Azure Migrate uses Network Block Device (NBD) protocol with SSL encryption.
+Azure Migrate usesthe  Network Block Device (NBD) protocol with SSL encryption.
 
 ## What is the minimum vCenter Server version required for migration?
 
@@ -65,10 +65,10 @@ You need to have at least vCenter Server 5.5 and VMware vSphere ESXi host versio
 
 No. Azure Migrate supports migration only to managed disks (standard HDD, premium SSD).
 
-## How many VMs can replicate simultaneously using agentless VMware stack?
-
-Currently, customers can migrate 100 VMs per vCenter Server simultaneously. This can be done in batches of 10 VMs.
+## How many VMs can I replicate together with agentless migration?
 
+Currently, you can nmigrate 100 VMs per vCenter Server simultaneously. Migrate in batches of 10 VMs.
+