point to avg considerations

Author: b-ahibbard

articles/azure-netapp-files/application-volume-group-considerations.md

@@ -17,7 +17,7 @@ This article describes the requirements and considerations you need to be aware
 * You need to use the [manual QoS capacity pool](manage-manual-qos-capacity-pool.md) functionality.  
 * Application volume group supports Basic and Standard network features. To use features including availability zone volume placement, use [Standard network features](azure-netapp-files-network-topologies.md).
 * Application volume group supports [availability zone volume placement](use-availability-zones.md) as the default and recommended method for placement. Using availability zone volume placement mitigates the need for AVset pinning and eliminates the need for proximity placement groups. With support for availability zone volume placement, you only need to select the same availability zone as the database servers. Using availability zone volume placement aligns with the Microsoft recommendation on how to deploy SAP HANA infrastructures to achieve best performance with high-availability, maximum flexibility, and simplified deployment. 
-    * <a name="ppg"></a> If regions don't support availability zones, you can select a regional deployment or choose proximity placement groups (PPG).
+    * If regions don't support availability zones, you can select a regional deployment or choose proximity placement groups (PPG).
 
     When you create a PPG, you must anchor it to your SAP HANA compute resources. Application volume group for SAP HANA needs this setup to search for an Azure NetApp Files resource that is close to the SAP HANA servers. For more information, see [Best practices about PPGs](#best-practices-about-proximity-placement) and [Create a PPG using the Azure portal](/azure/virtual-machines/windows/proximity-placement-groups-portal).
 

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

@@ -42,7 +42,7 @@ Application volume group for SAP HANA helps you simplify the deployment process
 
 * [Availability zone volume placement](use-availability-zones.md)
 
-    Designating the same availability zone for the volumes ensures that virtual machines and Azure NetApp Files volumes reside in the same availability zone and meet the latency requirements for SAP HANA. Availability zone volume placement simplifies the deployment process, avoiding the manual AvSet pinning process and eliminating the requirement for availability sets. To learn more about the differences between availability zone volume placement and proximity placement groups, see [Requirements and considerations for application volume group for SAP HANA](application-volume-group-considerations.md#ppg).
+    Designating the same availability zone for the volumes ensures that virtual machines and Azure NetApp Files volumes reside in the same availability zone and meet the latency requirements for SAP HANA. Availability zone volume placement simplifies the deployment process, avoiding the manual AvSet pinning process and eliminating the requirement for availability sets. To learn more about the differences between availability zone volume placement and proximity placement groups, see [Requirements and considerations for application volume group for SAP HANA](application-volume-group-considerations.md#bes-practices-about-proximity-placement).
 
 * Creation of separate storage endpoints (with different IP addresses) for data and log volumes.
     * This deployment method provides better performance and throughput for the SAP HANA database.