Merge pull request #284579 from b-ahibbard/copilot-edits

copilot edits

Author: PMEds28

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

@@ -13,7 +13,7 @@ ms.custom: references_regions
 
 Network architecture planning is a key element of designing any application infrastructure. This article helps you design an effective network architecture for your workloads to benefit from the rich capabilities of Azure NetApp Files.
 
-Azure NetApp Files volumes are designed to be contained in a special purpose subnet called a [delegated subnet](../virtual-network/virtual-network-manage-subnet.md) within your Azure Virtual Network. Therefore, you can access the volumes directly from within Azure over VNet peering or from on-premises over a Virtual Network Gateway (ExpressRoute or VPN Gateway). The subnet is dedicated to Azure NetApp Files and there's no connectivity to the Internet. 
+Azure NetApp Files volumes are designed to be contained in a special purpose subnet called a [delegated subnet](../virtual-network/virtual-network-manage-subnet.md) within your Azure Virtual Network. Therefore, you can access the volumes directly from within Azure over virtual network (VNet) peering or from on-premises over a Virtual Network Gateway (ExpressRoute or VPN Gateway). The subnet is dedicated to Azure NetApp Files and there's no connectivity to the Internet. 
 
 <a name="regions-standard-network-features"></a>The option to set Standard network features on new volumes and to modify network features for existing volumes is supported in all Azure NetApp Files-enabled regions. 
 
@@ -37,7 +37,7 @@ The following table describes what’s supported for each network features confi
 
 |      Features     |      Standard network features     |      Basic network features     |
 |---|---|---|
-|     Number of IPs in a VNet (including immediately peered VNets) accessing volumes in an Azure NetApp Files hosting VNet    |     [Same standard limits as VMs](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-resource-manager-virtual-networking-limits)    |     1000    |
+|     Number of IPs in a VNet (including immediately peered VNets) accessing volumes in an Azure NetApp Files hosting VNet    |     [Same standard limits as virtual machines (VMs)](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-resource-manager-virtual-networking-limits)    |     1000    |
 |     Azure NetApp Files delegated subnets per VNet    |     1    |     1    |
 |     [Network Security Groups](../virtual-network/network-security-groups-overview.md) (NSGs) on Azure NetApp Files delegated   subnets    |     Yes    |     No    |
 |     [User-defined routes](../virtual-network/virtual-networks-udr-overview.md#user-defined) (UDRs) on Azure NetApp Files delegated subnets    |     Yes    |     No    |
@@ -98,7 +98,7 @@ If the VNet is peered with another VNet, you can't expand the VNet address space
 >
 > It's also recommended that the size of the delegated subnet be at least /25 for SAP workloads and /26 for other workload scenarios.
 
-### UDRs and NSGs
+### <a name="udrs-and-nsgs"></a> User-defined routes (UDRs) and network security groups (NSGs)
 
 If the subnet has a combination of volumes with the Standard and Basic network features, user-defined routes (UDRs) and network security groups (NSGs) applied on the delegated subnets will only apply to the volumes with the Standard network features.
 

articles/azure-netapp-files/azure-netapp-files-quickstart-set-up-account-create-volumes.md

@@ -451,17 +451,8 @@ Use the Azure portal, PowerShell, or the Azure CLI to delete the resource group.
 
 ## Next steps
 
-> [!div class="nextstepaction"]
-> [Storage hierarchy of Azure NetApp Files](azure-netapp-files-understand-storage-hierarchy.md)
-
-> [!div class="nextstepaction"]
-> [Service levels for Azure NetApp Files](azure-netapp-files-service-levels.md)
-
-> [!div class="nextstepaction"]
-> [Create an NFS volume](azure-netapp-files-create-volumes.md)
-
-> [!div class="nextstepaction"]
-> [Solution architectures using Azure NetApp Files](azure-netapp-files-solution-architectures.md)
-
-> [!div class="nextstepaction"]
-> [Application resilience FAQs for Azure NetApp Files](faq-application-resilience.md)
+- [Storage hierarchy of Azure NetApp Files](azure-netapp-files-understand-storage-hierarchy.md)
+- [Service levels for Azure NetApp Files](azure-netapp-files-service-levels.md)
+- [Create an NFS volume](azure-netapp-files-create-volumes.md)
+- [Solution architectures using Azure NetApp Files](azure-netapp-files-solution-architectures.md)
+- [Application resilience FAQs for Azure NetApp Files](faq-application-resilience.md)

articles/azure-netapp-files/azure-netapp-files-resource-limits.md

@@ -24,7 +24,7 @@ The following table describes resource limits for Azure NetApp Files:
 |  Number of volumes per subscription   |    500     |   Yes   |
 |  Number of volumes per capacity pool     |    500   |    Yes     |
 |  Number of snapshots per volume       |    255     |    No        |
-|  Number of IPs in a virtual network (including immediately peered VNets) accessing volumes in an Azure NetApp Files hosting VNet    |   <ul><li>**Basic**: 1000</li><li>**Standard**: [Same standard limits as VMs](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-resource-manager-virtual-networking-limits)</li></ul>  |    No    |
+|  Number of IPs in a virtual network (including immediately peered virtual networks [VNets]) accessing volumes in an Azure NetApp Files hosting VNet    |   <ul><li>**Basic**: 1000</li><li>**Standard**: [Same standard limits as VMs](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-resource-manager-virtual-networking-limits)</li></ul>  |    No    |
 |  Minimum size of a single capacity pool   |  1 TiB*     |    No  |
 |  Maximum size of a single capacity pool    |  2,048 TiB   |   No   |
 |  Minimum size of a single regular volume    |    50 GiB    |    No    |