acrolinx

Author: b-ahibbard

articles/azure-netapp-files/faq-networking.md

@@ -13,7 +13,7 @@ This article answers frequently asked questions (FAQs) about Azure NetApp Files
 
 ## Does the data path for NFS or SMB go over the Internet?  
 
-No. The data path for NFS or SMB does not go over the Internet. Azure NetApp Files is an Azure native service that is deployed into the Azure Virtual Network (VNet) where the service is available. Azure NetApp Files uses a delegated subnet and provisions a network interface directly on the VNet. 
+No. The data path for NFS or SMB doesn't go over the Internet. Azure NetApp Files is an Azure native service that is deployed into the Azure Virtual Network (VNet) where the service is available. Azure NetApp Files uses a delegated subnet and provisions a network interface directly on the VNet. 
 
 See [Guidelines for Azure NetApp Files network planning](./azure-netapp-files-network-topologies.md) for details.  
 
@@ -32,21 +32,21 @@ Yes, you can, if you create the required DNS entries. Azure NetApp Files supplie
 
 ## Can I set or select my own IP address for an Azure NetApp Files volume?  
 
-No. IP assignment to Azure NetApp Files volumes is dynamic. Static IP assignment is not supported. 
+No. IP assignment to Azure NetApp Files volumes is dynamic. Static IP assignment isn't supported. 
 
 ## Does Azure NetApp Files support dual stack (IPv4 and IPv6) VNet?
 
-No, Azure NetApp Files does not currently support deploying volumes in a dual-stack (IPv4 and IPv6) delegated subnet. The delegated subnet for the Azure NetApp Files service must be an IPv4-only subnet. However, Azure NetApp Files is accessible over IPv4 through a dual-stack subnet or (peered) VNet.
+No. Azure NetApp Files doesn't currently support deploying volumes in a dual-stack (IPv4 and IPv6) delegated subnet. The delegated subnet for the Azure NetApp Files service must be an IPv4-only subnet. However, Azure NetApp Files is accessible over IPv4 through a dual-stack subnet or (peered) VNet.
 
-## Is the number of the IP addresses using Azure VMware Solutions for Guest OS mounts limited to 1000?
+## Is the number of the IP addresses using Azure VMware Solution for Guest OS mounts limited to 1000?
 
-No. Azure VMware Solutions is behind an ER gateway, which makes it behave similar to on-premises systems. The number of AVS "Hosts" and "Guests" is not visible to Azure NetApp Files, and the [1000 IP address limit](azure-netapp-files-resource-limits.md#resource-limits) is not applicable.
+No. Azure VMware Solutions is behind an ER gateway, which makes it behave similar to on-premises systems. The number of AVS "Hosts" and "Guests" isn't visible to Azure NetApp Files, and the [1000 IP address limit](azure-netapp-files-resource-limits.md#resource-limits) isn't applicable.
 
 ## Can I use DNS A/AAAA records or CNAME records to connect to Azure NetApp Files volumes?
 
 Azure NetApp Files provides full support for using both A/AAAA (hostname) and CNAME (alias) records in DNS when connecting to NFS and SMB shares. Both  types of records can be used for hostname to IP resolution, load balancing, preserving legacy mount paths when data has been migrated, and more.
 
-For additional flexibility, see [How to use DFS Namespaces with Azure NetApp Files](use-dfs-n-and-dfs-root-consolidation-with-azure-netapp-files.md). 
+For further flexibility, see [How to use DFS Namespaces with Azure NetApp Files](use-dfs-n-and-dfs-root-consolidation-with-azure-netapp-files.md). 
 
 ## Next steps