acrolinx

Author: b-ahibbard

articles/azure-netapp-files/cross-region-replication-create-peering.md

@@ -15,9 +15,9 @@ Azure NetApp Files supports [cross-region](cross-region-replication-introduction
 Setting up replication peering enables you to asynchronously replicate data from an Azure NetApp Files volume (source) to another Azure NetApp Files volume (destination). You can create volume replication between regions (the source and destination volumes reside in different regions, this is known as cross-region replication), or within a region where the replication is established to a different zone in the same region (this is known as cross-zone replication).  
 
 >[!NOTE] 
->During normal operation, the destination volume in an Azure NetApp Files replication relationship is available for read-only access. The destination volume becomes available for read-write operations when the replication is stopped. Any subsequent changes to the destination volume need to be synchronized with the source volume with a [reverse-resync operation](cross-region-replication-manage-disaster-recovery.md#resync-replication), after after which the normal replication can be resumed. 
+>During normal operation, the destination volume in an Azure NetApp Files replication relationship is available for read-only access. The destination volume becomes available for read-write operations when the replication is stopped. Any subsequent changes to the destination volume need to be synchronized with the source volume with a [reverse-resync operation](cross-region-replication-manage-disaster-recovery.md#resync-replication), after which the normal replication can be resumed. 
 
-Replication is permitted between different subscriptions under the same tenant ID. Replication across tenants isn't supported. Replication is supported with capacity pools of the same and different service levels. For example, the source volume can be in an Ultra service level capacity pool, and the destination volume can be in a Standard service level capacity pool. You can use this flexibility to reduce cost for the recovery volume if a lower service level is acceptable. If the recovery volume requires a higher service level, you can dynamically move the volume to a capacity pool with a higher service leve without interruption to the service. 
+Replication is permitted between different subscriptions under the same tenant ID. Replication across tenants isn't supported. Replication is supported with capacity pools of the same and different service levels. For example, the source volume can be in an Ultra service level capacity pool, and the destination volume can be in a Standard service level capacity pool. You can use this flexibility to reduce cost for the recovery volume if a lower service level is acceptable. If the recovery volume requires a higher service level, you can dynamically move the volume to a capacity pool with a higher service level without interruption to the service. 
 
 Before you begin, review the [requirements and considerations for cross-region replication](cross-region-replication-requirements-considerations.md) and [cross-zone replication](cross-zone-replication-requirements-considerations.md).
 
@@ -51,7 +51,7 @@ You need to obtain the resource ID of the source volume that you want to replica
 1. Go to the source volume, and select **Properties** under Settings to display the source volume resource ID.   
     ![Locate source volume resource ID](./media/cross-region-replication-create-peering/cross-region-replication-source-volume-resource-id.png)
  
-2. Copy the resource ID to the clipboard.  You will need it later.
+2. Copy the resource ID to the clipboard. The ID is required in a later step.
 
 ## Create the data replication volume (the destination volume)