minor fixes

Author: aimee-littleton

articles/nat-gateway/nat-overview.md

@@ -14,7 +14,7 @@ ms.custom: FY23 content-maintenance
 
 # What is Azure NAT Gateway?
 
-Azure NAT Gateway is a fully managed and highly resilient Network Address Translation (NAT) service. You can use Azure NAT Gateway to let all instances in a private subnet  connect outbound to the internet while remaining fully private. Unsolicited inbound connections from the internet are not permitted through a NAT gateway. Only packets arriving as response packets to an outbound connection can pass through a NAT gateway.
+Azure NAT Gateway is a fully managed and highly resilient Network Address Translation (NAT) service. You can use Azure NAT Gateway to let all instances in a private subnet  connect outbound to the internet while remaining fully private. Unsolicited inbound connections from the internet aren't permitted through a NAT gateway. Only packets arriving as response packets to an outbound connection can pass through a NAT gateway.
 
 NAT Gateway provides dynamic SNAT port functionality to automatically scale outbound connectivity and reduce the risk of SNAT port exhaustion. 
 
@@ -34,7 +34,7 @@ Azure NAT Gateway provides outbound connectivity for many Azure resources, inclu
 
 ### Simple Setup
 
-Deployments are intentionally made simple with NAT gateway. Attach NAT gateway to a subnet and public IP address and start connecting outbound to the internet right away. There is zero maintenance and routing configurations required. More public IPs or subnets can be addded later without impact to your existing configuration. 
+Deployments are intentionally made simple with NAT gateway. Attach NAT gateway to a subnet and public IP address and start connecting outbound to the internet right away. There's zero maintenance and routing configurations required. More public IPs or subnets can be added later without impact to your existing configuration. 
 
 NAT gateway deployment steps: 
 1. Create a non-zonal or zonal NAT gateway. 
@@ -45,7 +45,7 @@ If necessary, modify TCP idle timeout (optional). Review [timers](/azure/nat-gat
 
 ### Security
 
-NAT Gateway is built on the zero trust network security model and is secure by default. With NAT gateway, private instances within a subnet don't need public IP addresses to reach the internet. Private resources can reach external sources outside the virtual network by source network address translating (SNAT) to NAT gateway's static public IP addresses or prefixes. You can associate a public IP prefix to ensure that a contiguous set of IPs will be used for outbound. Destination firewall rules can be configured based on this predictable IP list.
+NAT Gateway is built on the zero trust network security model and is secure by default. With NAT gateway, private instances within a subnet don't need public IP addresses to reach the internet. Private resources can reach external sources outside the virtual network by source network address translating (SNAT) to NAT gateway's static public IP addresses or prefixes. You can provide a contiguous set of IPs for outbound connectivity by using a public IP prefix. Destination firewall rules can be configured based on this predictable IP list.
 
 ### Resiliency 
 
@@ -55,13 +55,13 @@ Azure NAT Gateway is a fully managed and distributed service. It doesn't depend
 
 NAT gateway is scaled out from creation. There isn't a ramp up or scale-out operation required. Azure manages the operation of NAT gateway for you. 
 
-A NAT gateway resource can be associated to a subnet and can be used by all private resources in that subnet. All subnets in a virtual network can use the same NAT gateway resource.  Outbound connectivity can be scaled out by assigning up to 16 public IP addresses or a /28 size public IP prefix to NAT gateway. When a NAT gateway is associated to a public IP prefix, it automatically scales to the number of IP addresses needed for outbound.
+Attach NAT gateway to a subnet to provide outbound connectivity for all private resources in that subnet. All subnets in a virtual network can use the same NAT gateway resource.  Outbound connectivity can be scaled out by assigning up to 16 public IP addresses or a /28 size public IP prefix to NAT gateway. When a NAT gateway is associated to a public IP prefix, it automatically scales to the number of IP addresses needed for outbound.
 
 ### Performance
 
 Azure NAT Gateway is a software defined networking service. Each NAT gateway can process up to 50 Gbps of data for both outbound and return traffic. 
 
-A NAT gateway won't affect the network bandwidth of your compute resources. Learn more about [NAT gateway's performance](nat-gateway-resource.md#performance).
+A NAT gateway doesn't affect the network bandwidth of your compute resources. Learn more about [NAT gateway's performance](nat-gateway-resource.md#performance).
 
 ## Azure NAT Gateway basics
 
@@ -78,17 +78,17 @@ A NAT gateway won't affect the network bandwidth of your compute resources. Lear
 
 * NAT gateway takes precedence over other outbound connectivity methods, including Load balancer, instance-level public IP addresses, and Azure Firewall.
 
-* When NAT gateway is configured to a virtual network where a different outbound connectivity method already exists, NAT gateway will take over all outbound traffic moving forward. There will be no drops in traffic flow for existing connections on Load balancer. All new connections will use NAT gateway.  
+* When NAT gateway is configured to a virtual network where a different outbound connectivity method already exists, NAT gateway takes over all outbound traffic moving forward. There are no drops in traffic flow for existing connections on Load balancer. All new connections use NAT gateway.  
 
 * NAT gateway doesn't have the same limitations of SNAT port exhaustion as does [default outbound access](../virtual-network/ip-services/default-outbound-access.md) and [outbound rules of a load balancer](../load-balancer/outbound-rules.md).
 
 * NAT gateway supports TCP and UDP protocols only. ICMP isn't supported.
 
 ### Traffic routes
 
-* A subnet’s default route to the internet is replaced by NAT gateway when configured. All traffic within the 0.0.0.0/0 prefix will have a next hop type to NAT gateway before connecting outbound to the internet. 
+* NAT gateway replaces a subnet’s default route to the internet when configured. All traffic within the 0.0.0.0/0 prefix have a next hop type to NAT gateway before connecting outbound to the internet. 
 
-* You can override a subnet’s default route to the internet through a NAT gateway with the creation of a custom user-defined route (UDR). 
+* You can override NAT gateway as a subnet’s next hop to the internet with the creation of a custom user-defined route (UDR). 
 
 * Presence of custom UDRs for virtual appliances and ExpressRoute override NAT gateway for directing internet bound traffic (route to the 0.0.0.0/0 address prefix).
 
@@ -115,7 +115,7 @@ Virtual appliance UDR / ExpressRoute >> NAT gateway >> Instance-level public IP
 
 * NAT gateway can’t be associated to an IPv6 public IP address or IPv6 public IP prefix. 
 
-* NAT gateway can be used in conjunction with Load balancer using outbound rules to provide dual-stack outbound connectivity, see [dual stack outbound connectivity with NAT gateway and Load balancer](/azure/virtual-network/nat-gateway/tutorial-dual-stack-outbound-nat-load-balancer?tabs=dual-stack-outbound-portal).
+* NAT gateway can be used with Load balancer using outbound rules to provide dual-stack outbound connectivity, see [dual stack outbound connectivity with NAT gateway and Load balancer](/azure/virtual-network/nat-gateway/tutorial-dual-stack-outbound-nat-load-balancer?tabs=dual-stack-outbound-portal).
 
 * NAT gateway works with any virtual machine network interface or IP configuration. NAT gateway can SNAT multiple IP configurations on a NIC. 
 
@@ -143,11 +143,11 @@ Virtual appliance UDR / ExpressRoute >> NAT gateway >> Instance-level public IP
 
 ### Connection timeouts and timers
 
-* NAT gateway sends a TCP Reset (RST) packet for any connection flow that it does not recognize as an existing connection. The connection flow may no longer exist if the NAT gateway idle timeout was reached or the connection was closed earlier. 
+* NAT gateway sends a TCP Reset (RST) packet for any connection flow that it doesn't recognize as an existing connection. The connection flow may no longer exist if the NAT gateway idle timeout was reached or the connection was closed earlier. 
 
-* When the NAT gateway TCP RST packet is received by the sender of traffic on the nonexisting connection flow, this signifies that the connection is no longer usable.
+* When the sender of traffic on the nonexisting connection flow receives the NAT gateway TCP RST packet, the connection is no longer usable.
 
-* SNAT ports are not readily available for reuse to the same destination endpoint after a connection closes. NAT gateway places SNAT ports in a cool down state before they can be reused to connect to the same destination endpoint. 
+* SNAT ports aren't readily available for reuse to the same destination endpoint after a connection closes. NAT gateway places SNAT ports in a cool down state before they can be reused to connect to the same destination endpoint. 
 
 * SNAT port reuse (cool down) timer durations vary for TCP traffic depending on how the connection closes. To learn more, see [Port Reuse Timers](./nat-gateway-resource.md#port-reuse-timers).