fix broken anchors

b-ahibbard · b-ahibbard · commit a8adc72cf78a · 2025-07-30T20:34:15.000-04:00
diff --git a/articles/azure-netapp-files/cross-region-replication-display-health-status.md b/articles/azure-netapp-files/cross-region-replication-display-health-status.md
@@ -67,7 +67,7 @@ Create [alert rules in Azure Monitor](/azure/azure-monitor/alerts/alerts-overvie
 
 * [Cross-region replication](replication.md)
 * [Manage disaster recovery](cross-region-replication-manage-disaster-recovery.md)
-* [Resize a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-cross-region-replication-destination-volume)
+* [Resize a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-replication-destination-volume)
 * [Volume replication metrics](azure-netapp-files-metrics.md#replication)
 * [Delete volume replications or volumes](cross-region-replication-delete.md)
 * [Troubleshoot cross-region replication](troubleshoot-cross-region-replication.md)
diff --git a/articles/azure-netapp-files/cross-region-replication-manage-disaster-recovery.md b/articles/azure-netapp-files/cross-region-replication-manage-disaster-recovery.md
@@ -101,7 +101,7 @@ After the resync operation from destination to source is complete, you need to b
 * [Cross-region 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)
-* [Resize a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-cross-region-replication-destination-volume)
+* [Resize a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-replication-destination-volume)
 * [Volume replication metrics](azure-netapp-files-metrics.md#replication)
 * [Delete volume replications or volumes](cross-region-replication-delete.md)
 * [Troubleshoot cross-region replication](troubleshoot-cross-region-replication.md)
diff --git a/articles/azure-netapp-files/data-protection-disaster-recovery-options.md b/articles/azure-netapp-files/data-protection-disaster-recovery-options.md
@@ -11,7 +11,7 @@ ms.author: anfdocs
 ---
 # Understand data protection and disaster recovery options in Azure NetApp Files
 
-Learn about the different data protection and disaster recovery features in Azure NetApp Files to understand what solutions best serve your needs.  
+Learn about the different data protection and disaster recovery features in Azure NetApp Files and understand what solutions best serve your needs.  
 
 ## Snapshots 
 
@@ -42,28 +42,28 @@ To learn more, see [How snapshots can be vaulted for long-term retention and cos
 
 Using snapshot technology, you can replicate your Azure NetApp Files across designated Azure regions to protect your data from unforeseeable regional failures. Cross-region replication minimizes data transfer costs, replicating only changed blocks across regions while also enabling a lower restore point objective.   
 
-Cross-region replication can be used in conjunction with cross-zone replication. For more information, see [configure cross-zone-region replication](cross-zone-region-replication-configure.md).
+Cross-region replication can be used with cross-zone replication. For more information, see [configure cross-zone-region replication](cross-zone-region-replication-configure.md).
 
 ### Benefits 
 
 - Provides disaster recovery across regions 
 - Data availability and redundancy for remote data processing and user access 
 - Efficient storage-based data replication without load on compute infrastructure 
 
-To learn more, see [How volumes and snapshots are replicated cross-region for DR](snapshots-introduction.md#how-volumes-and-snapshots-are-replicated-for-disaster-recovery-and-business-continuity). To get started with cross-region replication, see [Create cross-region replication for Azure NetApp Files](cross-region-replication-create-peering.md). 
+To learn more, see [How volumes and snapshots are replicated cross-region for disaster recovery](snapshots-introduction.md#how-volumes-and-snapshots-are-replicated-for-disaster-recovery-and-business-continuity). To get started with cross-region replication, see [Create cross-region replication for Azure NetApp Files](cross-region-replication-create-peering.md). 
 
 ## Cross-zone replication 
 
 Cross-zone replication leverages [availability zones](replication.md#availability-zones) and the same replication engine as cross-region replication. This technology creating a fast and cost-effective solution for you to asynchronously replicate volumes from availability zone to another without the need for host-based data replication.  
 
-Cross-zone replication can be used in conjunction with cross-region replication. For more information, see [configure cross-zone-region replication](cross-zone-region-replication-configure.md).
+Cross-zone replication can be used with cross-region replication. For more information, see [configure cross-zone-region replication](cross-zone-region-replication-configure.md).
 
 ### Benefits 
 
 - Data availability and redundancy across zones within regions 
 - Bring data into same zone as compute for lowest latency-envelope 
 - Efficient storage-based data replication without load on compute infrastructure  
-- Lower TCO due to absence of data transfer fees
+- Lower total cost of ownership (TCO) due to absence of data transfer fees
 
 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). 
 
diff --git a/articles/azure-netapp-files/troubleshoot-cross-region-replication.md b/articles/azure-netapp-files/troubleshoot-cross-region-replication.md
@@ -78,7 +78,7 @@ This article describes error messages and resolutions that can help you troubles
 
 | Error message | Resolution |
 |-|-|
-|   Attempt to resize a source volume is failing with the error `"PoolSizeTooSmall","message":"Pool size too small for total volume size."`  |  Ensure you have enough space available 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. If the capacity pool hosting the destination volume doesn’t have enough available space, resizing both the source and the destination volumes will fail. See [Resize a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-cross-region-replication-destination-volume) for details.   |
+|   Attempt to resize a source volume is failing with the error `"PoolSizeTooSmall","message":"Pool size too small for total volume size."`  |  Ensure you have enough space available 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. If the capacity pool hosting the destination volume doesn’t have enough available space, resizing both the source and the destination volumes will fail. See [Resize a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-replication-destination-volume) for details.   |
 
 ## Next steps  
 
@@ -87,5 +87,5 @@ This article describes error messages and resolutions that can help you troubles
 * [Create volume replication](cross-region-replication-create-peering.md)
 * [Display health status of replication relationship](cross-region-replication-display-health-status.md)
 * [Manage disaster recovery](cross-region-replication-manage-disaster-recovery.md)
-* [Resize a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-cross-region-replication-destination-volume)
+* [Resize a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-replication-destination-volume)
 * [Test disaster recovery for Azure NetApp Files](test-disaster-recovery.md)
diff --git a/articles/azure-netapp-files/whats-new.md b/articles/azure-netapp-files/whats-new.md
@@ -817,7 +817,7 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
     SMB Transparent Failover enables maintenance operations on the Azure NetApp Files service without interrupting connectivity to server applications storing and accessing data on SMB volumes. To support SMB Transparent Failover, Azure NetApp Files now supports the SMB Continuous Availability shares option for use with SQL Server applications over SMB running on Azure VMs. This feature is currently supported on Windows SQL Server. Azure NetApp Files doesn't currently support Linux SQL Server. This feature provides significant performance improvements for SQL Server. It also provides scale and cost benefits for [Single Instance, Always-On Failover Cluster Instance and Always-On Availability Group deployments](azure-netapp-files-solution-architectures.md#sql-server). See [Benefits of using Azure NetApp Files for SQL Server deployment](solutions-benefits-azure-netapp-files-sql-server.md).
 
-* [Automatic resizing of a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-cross-region-replication-destination-volume)
+* [Automatic resizing of a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-replication-destination-volume)
 
     In a cross-region replication 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 applies when the volumes are in an active replication relationship. It also applies when replication peering is broken with the resync operation. For this feature to work, you need to ensure sufficient headroom in the capacity pools for both the source and the destination volumes.
 
diff --git a/articles/reliability/reliability-netapp-files.md b/articles/reliability/reliability-netapp-files.md
@@ -153,7 +153,7 @@ By default, Azure NetApp Files is a single-region service. If the region becomes
 
 ### Region support
 
-The secondary region that you can replicate your volumes to depends on the primary region. For more information, see [supported region pairs](../azure-netapp-files/replication.md#supported-cross-region-replication-pairs). 
+The secondary region that you can replicate your volumes to depends on the primary region. For more information, see [supported region pairs](../azure-netapp-files/replication.md#supported-region-pairs). 
 
 ### Considerations
 
