edit pass: azure-nat-gateway-faq

Author: paulth1

articles/nat-gateway/faq.yml

@@ -51,13 +51,13 @@ sections:
 
       - question: Does Azure NAT Gateway support IP fragmentation?
         answer: |
-          No, Azure NAT Gateway doesn't support IP fragmentation for TCP or UDP protocols.
+          No, Azure NAT Gateway doesn't support IP fragmentation for the transmission control protocol (TCP) or the User Datagram Protocol (UDP).
                   
   - name: Azure NAT Gateway metrics
     questions: 
-      - question: What is the difference between source network address translation (SNAT) Connection Count and Total SNAT Connection Count metrics for Azure NAT Gateway?
+      - question: What is the difference between SNAT Connection Count and Total SNAT Connection Count metrics for Azure NAT Gateway?
         answer: |
-          The [SNAT Connection Count](nat-metrics.md#snat-connection-count) metric shows the number of new SNAT connections made per second. The [Total SNAT Connection Count](nat-metrics.md#total-snat-connection-count) metric shows the total number of active connections on an Azure NAT Gateway resource. 
+          The [source network address translation (SNAT) Connection Count](nat-metrics.md#snat-connection-count) metric shows the number of new SNAT connections made per second. The [Total SNAT Connection Count](nat-metrics.md#total-snat-connection-count) metric shows the total number of active connections on an Azure NAT Gateway resource. 
 
       - question: How can I see SNAT port usage on Azure NAT Gateway?
         answer: |
@@ -95,9 +95,9 @@ sections:
           
   - name: Traffic routes
     questions:
-      - question: What happens to Azure NAT Gateway if I force tunnel 0.0.0.0/0 (internet) traffic to a network virtual appliance (NVA), Azure VPN Gateway, or Azure ExpressRoute? 
+      - question: What happens to Azure NAT Gateway if I force tunnel 0.0.0.0/0 (internet) traffic to an NVA, Azure VPN Gateway, or Azure ExpressRoute? 
         answer: |
-          Azure NAT Gateway uses a subnet's system default internet path to route traffic to the internet. Traffic doesn't pass through Azure NAT Gateway if a UDR is created to direct 0.0.0.0/0 traffic to the next hop type NVA or a virtual network gateway.
+          Azure NAT Gateway uses a subnet's system default internet path to route traffic to the internet. Traffic doesn't pass through Azure NAT Gateway if a user-defined route is created to direct 0.0.0.0/0 traffic to the next hop type network virtual appliance (NVA) or a virtual network gateway.
 
       - question: What configuration must I make on the subnet route table to connect outbound with Azure NAT Gateway?
         answer: |
@@ -117,9 +117,9 @@ sections:
         answer: |
           Azure NAT Gateway can use up to 16 public IP addresses. Azure NAT Gateway can use any combination of public IP addresses and public IP prefixes totaling 16 addresses. Azure 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, also known as bring your own IP (BYOIP), with Azure NAT Gateway?
+      - question: How can I use custom IP prefixes (BYOIP) with Azure NAT Gateway?
         answer: |
-          You can use public IP prefixes and addresses derived from custom IP prefixes (BYOIP) with your NAT gateway. To learn more, see [Custom IP address prefix (BYOIP)](../virtual-network/ip-services/custom-ip-address-prefix.md). 
+          You can use public IP prefixes and addresses derived from custom IP prefixes, also known as bring your own IP (BYOIP), with your NAT gateway. To learn more, see [Custom IP address prefix (BYOIP)](../virtual-network/ip-services/custom-ip-address-prefix.md). 
       
       - question: Can an IPv6 public IP address be used with Azure NAT Gateway?
         answer: |
@@ -169,15 +169,15 @@ sections:
     questions:
       - question: How does Azure NAT Gateway work with availability zones?   
         answer: |
-          Azure NAT Gateway can be zonal or placed in "no zone." For more information, see [Azure NAT Gateway and availability zones](./nat-availability-zones.md). 
+          Azure NAT Gateway can be zonal or placed in "no zone." For more information, see [Azure NAT Gateway and availability zones](./nat-availability-zones.md). In addition:
 
           - A no-zone NAT gateway is placed in 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.
           - The zonal configuration of Azure NAT Gateway can't be changed after deployment.
 
       - question: Can a zone-redundant public IP address be attached to a NAT gateway? 
         answer: |
-          Zone-redundant public IP addresses and prefixes can be attached to either a no-zone NAT gateway or a NAT gateway assigned to a specific availability zone. For more information, see [Azure NAT Gateway and availability zones](/azure/nat-gateway/nat-availability-zones). In addition:
+          Zone-redundant public IP addresses and prefixes can be attached to either a no-zone NAT gateway or a NAT gateway assigned to a specific availability zone. For more information, see [Azure NAT Gateway and availability zones](/azure/nat-gateway/nat-availability-zones). 
 
   - name: Azure NAT Gateway and basic SKU resources
     questions: 
@@ -224,7 +224,7 @@ sections:
         answer: |
           Yes. If you enable secure cluster connectivity in your workspace, Azure NAT Gateway can be used with Azure Databricks in one of two ways: 
           
-          - If you use secure cluster connectivity with the default virtual network that Azure Databricks creates, Azure Databricks automatically creates a NAT gateway for outbound traffic from your workspace's subnets. The NAT gateway is created within the managed resource group that's managed by Azure Databricks. You can't modify this resource group or any resources provisioned within it.
+          - If you use secure cluster connectivity with the default virtual network that Azure Databricks creates, Azure Databricks automatically creates a NAT gateway for outbound traffic from your workspace's subnets. The NAT gateway is created within the managed resource group that Azure Databricks manages. You can't modify this resource group or any resources provisioned within it.
           - If you enable secure cluster connectivity on your workspace that uses virtual network injection, you can deploy a NAT gateway on both of the workspace's subnets to provide outbound connectivity. You can modify the configuration for customized outbound connectivity requirements in this case. For more information, see [Secure cluster connectivity](/azure/databricks/security/network/classic/secure-cluster-connectivity). 
           
 additionalContent: |