Fixed review changes

Author: SharmisthaRai

articles/site-recovery/how-to-enable-replication-proximity-placement-groups.md

@@ -1,5 +1,5 @@
 ---
-title: Replicate Azure VMs running in Proximity Placement Groups with Azure Site Recovery 
+title: Replicate Azure VMs running in Proximity Placement Groups
 description: Learn how to replicate Azure VMs running in Proximity Placement Groups using Azure Site Recovery.
 author: Sharmistha-Rai
 manager: gaggupta
@@ -8,21 +8,21 @@ ms.date: 05/25/2020
 
 ---
 
-# Replicate Azure VMs running in Proximity Placement Groups to another region
+# Replicate Azure virtual machines running in Proximity Placement Groups to another region
 
 This article describes how to replicate, failover and failback virtual machines running in a Proximity Placement Group to a secondary region.
 
 [Proximity Placement Groups](https://docs.microsoft.com/azure/virtual-machines/windows/proximity-placement-groups-portal) is an Azure Virtual Machine logical grouping capability that you can use to decrease the inter-VM network latency associated with your applications. When the VMs are deployed within the same proximity placement group, they are physically located as close as possible to each other. Proximity placement groups are particularly useful to address the requirements of latency-sensitive workloads.
 
-## Disaster recovery with proximity placement groups
+## Disaster recovery with Proximity Placement Groups
 
 In a typical scenario, you may have your virtual machines running in a proximity placement group to avoid the network latency between the various tiers of your application. While this can provide your application optimal network latency, you would like to protect these applications using Site Recovery for any region level failure. Site Recovery replicates the data from one region to another Azure region and brings up the machines in disaster recovery region in an event of failover.
 
 ## Considerations
 
-1. The best effort will be to failover/failback the virtual machines into a proximity placement group. However, if VM is unable to be brought up inside Proximity Placement during failover/failback, then failover/failback will still happen, and virtual machines will be created outside of a proximity placement group.
-2. If an Availability Set is pinned to a Proximity Placement Group and during failover/failback VMs in the availability set have an allocation constraint, then the virtual machines will be created outside of both the availability set and proximity placement group.
-3. Site Recovery for Proximity Placement Groups is not supported for unmanaged disks.
+- The best effort will be to failover/failback the virtual machines into a proximity placement group. However, if VM is unable to be brought up inside Proximity Placement during failover/failback, then failover/failback will still happen, and virtual machines will be created outside of a proximity placement group.
+-  If an Availability Set is pinned to a Proximity Placement Group and during failover/failback VMs in the availability set have an allocation constraint, then the virtual machines will be created outside of both the availability set and proximity placement group.
+-  Site Recovery for Proximity Placement Groups is not supported for unmanaged disks.
 
 ## Prerequisites
 
@@ -36,7 +36,7 @@ In a typical scenario, you may have your virtual machines running in a proximity
 2. Get the details of the virtual machine you’re planning to replicate as mentioned [here](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-powershell#get-details-of-the-virtual-machine-to-be-replicated).
 3. [Create](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-powershell#create-a-recovery-services-vault) your recovery services vault and [set](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-powershell#set-the-vault-context) the vault context.
 4. Prepare the vault to start replication virtual machine. This involves creating a [service fabric object](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-powershell#create-a-site-recovery-fabric-object-to-represent-the-primary-source-region) for both primary and recovery regions.
-5. [Create](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-powershell#create-a-site-recovery-protection-container-in-the-primary-fabric) a site recovery protection container, for both the primary and recovery fabrics.
+5. [Create](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-powershell#create-a-site-recovery-protection-container-in-the-primary-fabric) a Site Recovery protection container, for both the primary and recovery fabrics.
 6. [Create](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-powershell#create-a-replication-policy) a replication policy.
 7. Create a protection container mapping between primary and recovery protection container using [these](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-powershell#create-a-protection-container-mapping-between-the-primary-and-recovery-protection-container) steps and a protection container mapping for failback as mentioned [here](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-powershell#create-a-protection-container-mapping-for-failback-reverse-replication-after-a-failover).
 8. Create cache storage account by following [these](https://docs.microsoft.com/azure/site-recovery/azure-to-azure-powershell#create-cache-storage-account-and-target-storage-account) steps.