Apply suggestions from johndowns review

Co-authored-by: John Downs <[email protected]>

Author: Court72

articles/azure-netapp-files/replication.md

@@ -28,7 +28,7 @@ Azure NetApp Files supports cross-zone replication, which relies on availability
 Azure [availability zones](../reliability/availability-zones-overview.md) are physically separate locations within each supporting Azure region that are tolerant to local failures. Failures can range from software and hardware failures to events such as earthquakes, floods, and fires. Redundancy and logical isolation of Azure services achieve this tolerance to failures. To ensure resiliency, a minimum of three separate availability zones are present in all [availability zone-enabled regions](../reliability/regions-list.md).
 
 >[!IMPORTANT]
-> Availability zones are known as *logical zones*. Each datacenter is assigned to a physical zone. [Physical zones are mapped to logical zones in your Azure subscription](/azure/reliability/availability-zones-overview#physical-and-logical-availability-zones), and the mapping is different with different subscriptions. Azure subscriptions are automatically assigned this mapping when a subscription is created. Azure NetApp Files aligns with the generic logical-to-physical availability zone mapping for all Azure services for the subscription.
+> When you configure the availability zone for a volume, you actually configure its *logical zone*. Each datacenter is assigned to a physical zone. [Physical zones are mapped to logical zones in your Azure subscription](/azure/reliability/availability-zones-overview#physical-and-logical-availability-zones), and the mapping is different with different subscriptions. Azure subscriptions are automatically assigned this mapping when a subscription is created. Azure NetApp Files aligns with the generic logical-to-physical availability zone mapping for all Azure services for the subscription.
 
 To learn more about availability zones in Azure NetApp Files, see [Reliability in Azure NetApp Files](../reliability/reliability-netapp-files.md).
 

articles/reliability/reliability-netapp-files.md

@@ -98,7 +98,7 @@ You need to separately configure volume placement and cross-zone replication.
 
 ### Normal operations
 
-This section describes what to expect when Azure NetApp Files volumes are configured to deploy into multiple availability zones, cross-zone replication is enabled, and all availability zones are operational.
+This section describes what to expect when multiple Azure NetApp Files volumes are deployed into separate availability zones, cross-zone replication is enabled, and all availability zones are operational.
 
 - **Traffic routing between zones:** Incoming requests are routed to the specific volume, which is located in the availability zone that you select.
 
@@ -109,7 +109,7 @@ This section describes what to expect when Azure NetApp Files volumes are config
 
 ### Zone-down experience
 
-This section describes what to expect when Azure NetApp Files volumes are configured to deploy into multiple availability zones, cross-zone replication is enabled, and there's an availability zone outage.
+This section describes what to expect when multiple Azure NetApp Files volumes are deployed into separate availability zones, cross-zone replication is enabled, and there's an availability zone outage.
 
 - **Detection and response:** You're responsible for detecting the loss of an availability zone and initiating a failover.
 
@@ -133,7 +133,7 @@ This section describes what to expect when Azure NetApp Files volumes are config
 
 - **Traffic rerouting:** You're responsible for redirecting your application traffic to connect to the newly active destination volume. For more information, see [fail over to the destination volume](../azure-netapp-files/cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
 
-### Failback
+### Zone recovery
 
 Failback is a manual process that requires you to perform a resync operation, reestablish the replication, and remount the source volume for the client to access. For more information, see [Manage disaster recovery by using Azure NetApp Files](../azure-netapp-files/cross-region-replication-manage-disaster-recovery.md).
 
@@ -225,7 +225,7 @@ For most solutions, you shouldn't rely exclusively on backups. Instead, use the
 
 ## Service-level agreement
 
-The service-level agreement (SLA) for Azure NetApp Files describes the expected availability of the service and the conditions that must be met to achieve that availability expectation. For more information, see [SLAs for online services](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services).
+[!INCLUDE [SLA description](includes/reliability-sla-include.md)]
 
 ## Related content