resolve comments

Author: b-ahibbard

articles/azure-netapp-files/application-volume-group-oracle-introduction.md

@@ -46,15 +46,15 @@ Application volume group for Oracle helps you simplify the deployment process an
 * Creation of separate storage endpoints (with different IP addresses) for data and log volumes.   
     This deployment method provides better performance and throughput for the Oracle database.
 * Customer-managed keys support increased security and compliance. 
-* [Cross-zone](cross-zone-replication-introduction.md) and [cross-region](replication.md) replication provide efficient storage-based data replication without load on compute infrastructure and a layer of protection for disaster recovery. This feature currently is in preview and only supported with the [REST API](configure-application-volume-oracle-api.md#replication). 
+* [Cross-zone and cross-region replication](replication.md) provide efficient storage-based data replication without load on compute infrastructure and a layer of protection for disaster recovery. This feature currently is in preview and only supported with the [REST API](configure-application-volume-oracle-api.md#replication). 
 
 ## Application volume group layout
 
 Application volume group for Oracle deploys multiple volumes based on your input and on resource availability in the selected region and zone, subject to the following rules:
 
 [!INCLUDE [AVG bullet points](includes/application-volume-group-layout.md)]
 
-High availability deployments will include volumes in two availability zones or regions. Application volume group for Oracle allows you to deploy production volumes in the primary zone and data protection volumes in an alternate zone or region. You can use Data Guard to replicate redo log and data volumes, or you can choose to offload data volume replication load from the application server by using Azure NetApp Files [cross-zone](cross-zone-replication-introduction.md) or [cross-region replication](replication.md) for the data volumes. Use application-based data replication with Data Guard to synchronously replicate the redo logs so the database can be rolled forward after a failover.
+High availability deployments will include volumes in two availability zones or regions. Application volume group for Oracle allows you to deploy production volumes in the primary zone and data protection volumes in an alternate zone or region. You can use Data Guard to replicate redo log and data volumes, or you can choose to offload data volume replication load from the application server by using Azure NetApp Files [cross-zone or cross-region replication](replication.md) for the data volumes. Use application-based data replication with Data Guard to synchronously replicate the redo logs so the database can be rolled forward after a failover.
 
 :::image type="content" source="./media/application-volume-group-oracle-introduction/oracle-dual-zone-layout.png" alt-text="Diagram of dual-zone volume layout." lightbox="./media/application-volume-group-oracle-introduction/oracle-dual-zone-layout.png":::
 

articles/azure-netapp-files/azure-netapp-files-resize-capacity-pools-or-volumes.md

@@ -71,9 +71,9 @@ See [REST API for Azure NetApp Files](azure-netapp-files-develop-with-rest-api.m
 
 The REST API specification and example code for Azure NetApp Files are available through the [resource-manager GitHub directory](https://github.com/Azure/azure-rest-api-specs/tree/main/specification/netapp/resource-manager/Microsoft.NetApp/stable). See [this command](https://github.com/Azure/azure-rest-api-specs/blob/main/specification/netapp/resource-manager/Microsoft.NetApp/stable/2023-11-01/examples/Volumes_Update.json) for a sample volume update.
 
-## Resize a cross-region replication destination volume 
+## Resize a replication destination volume 
 
-In a [cross-region replication](replication.md) relationship, a destination volume is automatically resized based on the size of the source volume. As such, you don’t need to resize the destination volume separately. This automatic resizing behavior is applicable when the volumes are in an active replication relationship, or when replication peering is broken with the [resync operation](cross-region-replication-manage-disaster-recovery.md#resync-replication). 
+In a [cross-region or cross-zone replication](replication.md) relationship, a destination volume is automatically resized based on the size of the source volume. As such, you don’t need to resize the destination volume separately. This automatic resizing behavior is applicable when the volumes are in an active replication relationship, or when replication peering is broken with the [resync operation](cross-region-replication-manage-disaster-recovery.md#resync-replication). 
 
 The following table describes the destination volume resizing behavior based on the [Mirror state](cross-region-replication-display-health-status.md):
 
@@ -84,7 +84,7 @@ The following table describes the destination volume resizing behavior based on
 | *Uninitialized* | When you resize the source volume and the Mirror state is still *uninitialized*, resizing the destination volume needs to be done manually. As such, it's recommended that you wait for the initialization to complete (that is, when the Mirror state becomes *mirrored*) to resize the source volume. | 
 
 > [!IMPORTANT]
-> Ensure that you have enough headroom in the capacity pools for both the source and the destination volumes of cross-region replication. When you resize the source volume, the destination volume is automatically resized. But if the capacity pool hosting the destination volume doesn’t have enough headroom, the resizing of both the source and the destination volumes will fail.
+> Ensure that you have enough headroom in the capacity pools for both the source and the destination volumes of replication. When you resize the source volume, the destination volume is automatically resized. But if the capacity pool hosting the destination volume doesn’t have enough headroom, the resizing of both the source and the destination volumes will fail.
 
 ## Next steps
 

articles/azure-netapp-files/backup-manage-policies.md

@@ -38,7 +38,7 @@ To modify the backup policy settings:
     > After backups are configured and have taken effect for the scheduled frequency, you can't change the backup retention count to `0`. The backup retention count requires a minimum number of `1` for the backup policy. See [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md) for details.  
 
     >[!NOTE]
-    > Scheduled backups aren't supported on destination volumes in [cross-region](replication.md) or [cross-zone](cross-zone-replication-introduction.md) replication relationships. Backups on destination volumes can only be taken from manual snapshots replicated from the source volume. For more information, see [Requirements and considerations for Azure NetApp Files backup](backup-requirements-considerations.md#requirements-and-considerations).
+    > Scheduled backups aren't supported on destination volumes in [cross-region or cross-zone replication ](replication.md) relationships. Backups on destination volumes can only be taken from manual snapshots replicated from the source volume. For more information, see [Requirements and considerations for Azure NetApp Files backup](backup-requirements-considerations.md#requirements-and-considerations).
 
 ## Suspend a backup policy  
 

articles/azure-netapp-files/backup-requirements-considerations.md

@@ -41,7 +41,7 @@ Azure NetApp Files backup in a region can only protect an Azure NetApp Files vol
 
 * You can't apply a backup policy to a volume while a manual backup is in progress. Wait for the manual backup to complete before applying the policy. 
 
-* With [cross-region replication](replication.md) or [cross-zone replication](cross-zone-replication-introduction.md), Azure NetApp Files backup can be configured on a source volume. 
+* With [cross-region or cross-zone replication](replication.md), Azure NetApp Files backup can be configured on a source volume. 
 
     Backups on a destination volume are only supported for manually created snapshots. To take backups of a destination volume, create a snapshot on the source volume then wait for the snapshot to be replicated to the destination volume. From the destination volume, you select the snapshot for backup. Scheduled backups on a destination volume aren't supported.
 

articles/azure-netapp-files/configure-application-volume-oracle-api.md

@@ -1118,7 +1118,7 @@ curl -X PUT -H "Authorization: Bearer $token" -H "Content-Type:application/json"
 
 ## <a name="replication"></a> Configure cross-region or cross-zone replication (preview)
 
-You can use [cross-zone](cross-zone-replication-introduction.md) or [cross-region](replication.md) replication for disaster recovery for your application volume group. This example configures cross-zone replication. This feature is currently in _preview_. 
+You can use [cross-zone or cross-region replication](replication.md) for disaster recovery for your application volume group. This example configures cross-zone replication. This feature is currently in _preview_. 
 
 >[!NOTE]
 >In this example, placeholders for `<CapacityPoolResourceId>`, `<SrcVolumeId>`, and `<SubnetId>` need to be replaced. 

articles/azure-netapp-files/create-cross-zone-replication.md

@@ -11,7 +11,7 @@ ms.author: anfdocs
 ---
 # Create cross-zone replication relationships for Azure NetApp Files
 
-[Cross-zone replication](cross-zone-replication-introduction.md) enables you to replicate volumes across availability zones within the same region. It enables you to fail over your critical application if a region-wide outage or disaster happens. 
+[Cross-zone replication](replication.md#cross-zone-replication) enables you to replicate volumes across availability zones within the same region. It enables you to fail over your critical application if a region-wide outage or disaster happens. 
 
 For information about availability zones, see [Use availability zone volume placement for application high availability with Azure NetApp Files](replication.md#availability-zones) and [Manage availability zone volume placement for Azure NetApp Files](manage-availability-zone-volume-placement.md). 
 

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

@@ -11,7 +11,7 @@ ms.author: anfdocs
 ---
 # Create volume replication for Azure NetApp Files
 
-Azure NetApp Files enables you to replicate a volume for data protection and resiliency. You can replicate volumes across [regions](replication.md), [zones in the same region](cross-zone-replication-introduction.md), or a [combination](cross-zone-region-replication.md). 
+Azure NetApp Files enables you to replicate a volume for data protection and resiliency. You can replicate volumes across [regions](replication.md#cross-region-replication), [zones in the same region](replication.md#cross-zone-replication), or a [combination](replication.md#cross-zone-region-replication). 
 
 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).  
 
@@ -20,7 +20,7 @@ Setting up replication peering enables you to asynchronously replicate data from
 
 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](replication-requirements.md) and [cross-zone replication](replication-requirements.md).
+Before you begin, review the [requirements and considerations for cross-region and cross-zone replication](replication-requirements.md).
 
 ## Register for cross-subscription replication 
 
@@ -123,14 +123,8 @@ To authorize the replication, you need to obtain the resource ID of the replicat
     > Due to various factors, such as the state of the destination storage at a given time, there’s likely a difference between the used space of the source volume and the used space of the destination volume. <!-- ANF-14038 --> 
 
 ## Next steps  
-
-* [Cross-zone replication](cross-zone-replication-introduction.md)
-* [Requirements and considerations for cross-zone replication](replication-requirements.md)
-* [Cross-region replication](replication.md)
-* [Requirements and considerations for using cross-region replication](replication-requirements.md)
-* [Cross-zone-region replication](cross-zone-region-replication.md)
-* [Cross-zone replication](cross-zone-replication-introduction.md)
-* [Requirements and considerations for cross-zone replication](replication-requirements.md)
+* [Azure NetApp Files replication](replication.md)
+* [Requirements and considerations for Azure NetApp Files replication](replication-requirements.md)
 * [Display health status of replication relationship](cross-region-replication-display-health-status.md)
 * [Volume replication metrics](azure-netapp-files-metrics.md#replication)
 * [Manage disaster recovery](cross-region-replication-manage-disaster-recovery.md)

articles/azure-netapp-files/cross-region-replication-manage-disaster-recovery.md

@@ -55,7 +55,7 @@ After disaster recovery, you can reactivate the source volume by performing a re
 > In case the source volume didn't survive the disaster and therefore no common snapshot exists, all data in the destination will be resynchronized to a newly created source volume.
 
 >[!NOTE]
->To perform a reverse resync with [cross-zone-region replication](cross-zone-region-replication.md), you must break the secondary relationship then perform the reverse resync as described. 
+>To perform a reverse resync with [cross-zone-region replication](replication.md#cross-zone-region-replication), you must break the secondary relationship then perform the reverse resync as described. 
 > 
 > To restore the cross-zone-region replication, delete the secondary DP volume then [reconfigure replication](cross-zone-region-replication-configure.md).
 

articles/azure-netapp-files/cross-zone-region-replication-configure.md

@@ -16,7 +16,7 @@ Azure NetApp Files supports volume cross-zone and cross-region replication on th
 ## Requirements 
 
 - Cross-zone-region replication supports creating two replication relationships for a source volume: cross-zone replication, cross-region replication, or a combination.  
-- Cross-zone-region replication volumes must abide by the same requirements and considerations as individual [cross-zone replication](replication-requirements.md) and [cross-region replication](replication-requirements.md) volumes.  
+- Cross-zone-region replication volumes must abide by the same requirements and considerations as individual [cross-region and cross-zone replication](replication-requirements.md) volumes.  
 - You must break the secondary relationship before you can perform a reverse resync operation with cross-zone-region replication. For more information, see [Resync volumes after disaster recovery](cross-region-replication-manage-disaster-recovery.md#resync-replication).
 - Azure NetApp Files replication is supported within a subscription and between subscriptions under the same tenant.
 - Fan-out deployments are supported for two destination volumes: one source (read/write) volume and two destination volumes. 
@@ -64,8 +64,7 @@ You can also use [Azure CLI commands](/cli/azure/feature) `az feature register`
 
 ## Next steps 
 
-* [Understand cross-zone-region replication](cross-zone-region-replication.md)
-* [Cross-region replication](replication.md)
+* [Azure NetApp Files replication](replication.md)
 * [Requirements and considerations for using cross-region replication](replication-requirements.md)
 * [Display health status of replication relationship](cross-region-replication-display-health-status.md)
 * [Volume replication metrics](azure-netapp-files-metrics.md#replication)

articles/azure-netapp-files/data-protection-disaster-recovery-options.md

@@ -65,7 +65,7 @@ Cross-zone replication can be used in conjunction with cross-region replication.
 - Efficient storage-based data replication without load on compute infrastructure  
 - Lower TCO due to absence of data transfer fees
 
-To learn more, see [Understand cross-zone replication](cross-zone-replication-introduction.md). To get started with cross-zone replication, see [Create cross-zone replication relationships for Azure NetApp Files](create-cross-zone-replication.md). 
+To learn more, see [Understand cross-zone replication](replication.md#cross-zone-replication). To get started with cross-zone replication, see [Create cross-zone replication relationships for Azure NetApp Files](create-cross-zone-replication.md). 
 
 ## Choose a data protection solution
 
@@ -97,4 +97,3 @@ Fast data recovery (whole volume) | Revert volume from snapshot | Revert volume
 * [Restore individual files using single-file snapshot restore](snapshots-restore-file-single.md)
 * [Restore a snapshot to a new volume](snapshots-restore-new-volume.md)
 * [Restore a volume using snapshot revert](snapshots-revert-volume.md)
-* [Understand cross-zone-region replication](cross-zone-region-replication.md)