Fixes FAQ

Author: aimee-littleton

articles/virtual-network/nat-gateway/faq.yml

@@ -13,40 +13,37 @@ sections:
     questions:
       - question: How can I use NAT gateway to connect outbound in a setup where load balancer outbound rules or virtual machine public IPs are being used?
         answer: |
-          NAT gateway will automatically be used to connect outbound to the internet as soon as it is associated with a public IP address or prefix and a subnet. NAT gateway will be used to connect outbound over load balancer or instance-level public IP addresses on virtual machines.
+          NAT gateway will automatically connect outbound to the internet as soon as it's associated with a public IP address or prefix and a subnet. NAT gateway takes precedence over load balancer or instance-level public IP addresses on virtual machines for outbound connectivity.
      
       - question: Is there a drop in packets when a virtual network configured with Load balancer outbound rules switches to NAT gateway after being configured to a subnet?
         answer: |
-          No, there will be no drop in packets. Existing connections with Load balancer will continue to work until those connections officially close. After NAT gateway is added to the subnet of the virtual network, all new connections will then use NAT gateway for making outbound connections. 
+          No, there is no drop in packets. Existing connections with Load balancer continue to work until those connections officially close. After NAT gateway is added to the subnet of the virtual network, all new connections use NAT gateway for making outbound connections. 
      
       - question: Can NAT gateway be used to connect inbound?
         answer: |
           NAT gateway provides outbound connectivity from a virtual network. Return traffic in direct response to an outbound flow can also pass through NAT gateway. No inbound traffic directly from the internet can pass through NAT gateway.
       
       - question: Can a NAT gateway public IP connect directly to a private IP address over the internet?
         answer: |
-          No. A public IP address of NAT gateway cannot connect directly to a private IP over the internet. 
+          No. A public IP address of NAT gateway can't connect directly to a private IP over the internet. 
       
       - question: If multiple public IP addresses are assigned to a NAT gateway, is traffic flow disrupted when one of the IP addresses is removed?
         answer: |
-          Any active connections associated with a public IP address will terminate upon the public IP address being removed. If the NAT gateway resource has multiple public IPs, new traffic will be redistributed among the assigned IPs. It's advised that if you decide to remove one of the public IP addresses from the NAT gateway resource, use a maintenance window for the removal.
+          Any active connections associated with a public IP address terminate upon the public IP address being removed. If the NAT gateway resource has multiple public IPs, new traffic is edistributed among the assigned IPs.
           
       - question: Can NAT gateway be used with IPv6 public IP addresses?
         answer: |
-          No, NAT gateway does not support IPv6 public IP addresses at this time. You can configure dual stack outbound connectivity with NAT gateway and public Load balancer, see [configure dual stack outbound connectivity](./tutorial-dual-stack-outbound-nat-load-balancer.md?tabs=dual-stack-outbound-portal)
+          No, NAT gateway doesn't support IPv6 public IP addresses at this time. You can configure dual stack outbound connectivity with NAT gateway and public Load balancer, see [configure dual stack outbound connectivity](./tutorial-dual-stack-outbound-nat-load-balancer.md?tabs=dual-stack-outbound-portal)
   
   - name: NAT gateway configurations
     questions:  
       - question: Is the NAT gateway public IP address static?  
         answer: |
           Yes. When NAT gateway is configured on a subnet, all outbound connectivity uses your specified static public IP address(es).  
 
-      - question: What is the maximum number of public IP addresses that can be used by NAT gateway?
+      - question: How many public IP addresses can be attached to NAT gateway?
         answer: |
-          The NAT gateway resource can use up to 16 public IP addresses. The NAT gateway can use any combination of public IP addresses and public IP address prefixes totaling to 16 addresses. The maximum prefix size that can be used by NAT gateway is /28 (16 addresses). Other public IP prefix sizes that can be used by NAT gateway include:
-          /29 (8 addresses), 
-          /30 (4 addresses), 
-          /31 (2 addresses).  
+          The NAT gateway resource can use up to 16 public IP addresses. The NAT gateway can use any combination of public IP addresses and public IP address prefixes totaling to 16 addresses. NAT gateway can support the following prefix sizes: /28 (16 addresses), /29 (8 addresses), /30 (4 addresses), and /31 (2 addresses).  
 
       - question: How can I use custom IP prefixes (BYOIP) with NAT gateway?
         answer: |
@@ -60,29 +57,29 @@ sections:
         answer: |
           No, the address of an existing public IP can't be changed. A different or additional IP can be added to NAT gateway.  Associate either an existing or newly created public IP address to the NAT gateway resource.  Disassociate the old IP address. See [add or remove a public IP address](./manage-nat-gateway.md?tabs=manage-nat-portal#add-or-remove-a-public-ip-address) for guidance.
 
-      - question: If multiple public IP addresses are assigned to a NAT gateway resource, which public IPs will be used by my subnet resources?
+      - question: If multiple public IP addresses are assigned to a NAT gateway resource, which public IPs will my subnet resources use?
         answer: |
-          Any of your subnet resources can use any of the public IP addresses configured to your NAT gateway resource for outbound connectivity. Each time a new outbound connection is made through NAT gateway, the outbound public IP is selected at random. 
+          Your subnet resources can use any of the public IP addresses configured to your NAT gateway resource for outbound connectivity. Each time a new outbound connection is made through NAT gateway, the outbound public IP is selected at random. 
       
       - question: Can the address of a public IP be known before the IP address is created and attached to NAT gateway?
         answer: |
-          No, you cannot know the address of a newly created public IP before the public IP is created and deployed.
+          No, you can't know the address of a newly created public IP before the public IP is created and deployed.
       
       - question: If NAT gateway has multiple public IP addresses, can one of those IPs be assigned to a specific VM to use explicitly for going outbound?
         answer: |
-          No. Explicit IP assignment to specific VM instances in a NAT gateway configured subnet is not supported.
+          No. Explicit IP assignment to specific VM instances in a NAT gateway configured subnet isn't supported.
       
       - question: Are basic SKU resources (Basic Load Balancer and Basic public IP addresses) compatible with NAT gateway?
         answer: |
-          No. NAT gateway can only be used with standard SKU resources. Learn more from [VNet NAT basics](./nat-overview.md#azure-nat-gateway-basics)
+          No. NAT gateway is compatible with standard SKU resources. Learn more from [VNet NAT basics](./nat-overview.md#azure-nat-gateway-basics)
           You can upgrade your basic Load balancer and basic public IP address to standard in order to work with NAT gateway.
           
           To upgrade a basic Load balancer to standard, see [Upgrade Azure Public Load Balancer](../../load-balancer/upgrade-basic-standard.md)
           To upgrade a basic public IP to standard, see [Upgrade a public IP address](../ip-services/public-ip-upgrade-portal.md)
       
       - question: Can NAT gateway be attached to multiple virtual networks?  
         answer: |
-          No. NAT gateway cannot be attached to multiple virtual networks.  
+          No. NAT gateway can't be attached to multiple virtual networks.  
 
       - question: Can NAT gateway be attached to multiple subnets? 
         answer: |
@@ -98,17 +95,17 @@ sections:
           
       - question: Can multiple NAT gateways be attached to a single subnet?
         answer: |
-          No. NAT gateway operates based on the properties of the subnet it is attached to, and so multiple NAT gateways cannot be attached to a single subnet.
+          No. NAT gateway operates based on the properties of the subnet it is attached to, and so multiple NAT gateways can't be attached to a single subnet.
 
       - question: How does NAT gateway work with availability zones?   
         answer: |
           NAT gateway can be zonal or placed in "no zone". See [NAT gateway and availability zones](./nat-availability-zones.md) for more information. 
 
-          A "no zone" NAT gateway is placed into a zone for you by Azure and does not give a guarantee of redundancy.
+          A "no zone" NAT gateway is placed into a zone for you by Azure.
 
           A zonal NAT gateway is associated to a specific zone by the user when the NAT gateway is created.
           
-          After NAT gateway is deployed and placed in "no zone" or a specific zone, the zone selection cannot be changed.
+          The zonal configuration of NAT gateway can't be changed after deployment.
 
       - question: Can NAT gateway be moved from a region/subscription/resource group to another?
         answer: |
@@ -144,7 +141,7 @@ sections:
 
       - question: Can I use NAT gateway with Virtual Network service endpoints or Private Link?
         answer: | 
-           Yes. The addition of a NAT gateway to a subnet with service endpoints does not affect the endpoints. [Virtual Network service endpoints](../virtual-network-service-endpoints-overview.md) enable a more specific route for the destination Azure service traffic they represent. Traffic for the service endpoint will continue to be routed toward the service and won't go via the NAT gateway. Private Link is recommended over service endpoints when connecting to Azure PaaS services directly from your Azure network.
+           Yes. The addition of a NAT gateway to a subnet with service endpoints doesn't affect the endpoints. [Virtual Network service endpoints](../virtual-network-service-endpoints-overview.md) enable a more specific route for the destination Azure service traffic they represent. Traffic for the service endpoint will continue to be routed toward the service and won't go via the NAT gateway. Private Link is recommended over service endpoints when connecting to Azure PaaS services directly from your Azure network.
 
 additionalContent: |