Merge pull request #220577 from asudbring/nat-over-fresh

Freshness check and review for NAT overview

Author: prmerger-automator[bot]

articles/virtual-network/nat-gateway/nat-overview.md

@@ -8,7 +8,7 @@ author: asudbring
 ms.service: virtual-network
 ms.subservice: nat
 ms.topic: conceptual
-ms.date: 03/17/2022
+ms.date: 12/06/2022
 ms.author: allensu
 ---
 
@@ -81,15 +81,15 @@ Virtual appliance UDR / ExpressRoute >> NAT gateway >> Instance-level public IP
 
   * Public IP prefixes
 
-  * Public IP addresses and prefixes derived from custom IP prefixes (BYOIP), to learn more, see [Custom IP address prefix (BYOIP)](../ip-services/custom-ip-address-prefix.md)
+  * Public IP addresses and prefixes derived from custom IP prefixes (BYOIP), to learn more, see [Custom IP address prefix (BYOIP)](../ip-services/custom-ip-address-prefix.md).
 
 * NAT gateway can’t be associated to an IPv6 public IP address or IPv6 public IP prefix. It can be associated to a dual stack subnet, but will only be able to direct outbound traffic with an IPv4 address.
 
 ### Availability zones
 
 * A NAT gateway can be created in a specific availability zone or placed in 'no zone'. 
 
-* NAT gateway can be isolated in a specific zone when you create [zone isolation scenarios](./nat-availability-zones.md). This deployment is called a zonal deployment. After NAT gateway is deployed, the zone selection cannot be changed.
+* NAT gateway can be isolated in a specific zone when you create [zone isolation scenarios](./nat-availability-zones.md). This deployment is called a zonal deployment. After NAT gateway is deployed, the zone selection can't be changed.
 
 * NAT gateway is placed in no zone by default. A [non-zonal NAT gateway](./nat-availability-zones.md#non-zonal) is placed in a zone for you by Azure.
 
@@ -99,19 +99,19 @@ Virtual appliance UDR / ExpressRoute >> NAT gateway >> Instance-level public IP
 
 * Basic resources, such as basic load balancer or basic public IPs aren't compatible with Virtual Network NAT.  Basic resources must be placed on a subnet not associated to a NAT gateway. Basic load balancer and basic public IP can be upgraded to standard to work with a NAT gateway
 
-  * To upgrade a basic load balancer to standard, see [Upgrade a public basic Azure Load Balancer](../../load-balancer/upgrade-basic-standard.md).
+  * Upgrade a load balancer from basic to standard, see [Upgrade a public basic Azure 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).
+  * Upgrade a public IP from basic to standard, see [Upgrade a public IP address](../ip-services/public-ip-upgrade-portal.md).
 
 ### NAT gateway timers
 
-* NAT gateway holds on to SNAT ports after a connection closes before it is available to reuse to connect to the same destination endpoint over the internet. SNAT port reuse timer durations for TCP traffic vary depending on how the connection closes. To learn more, see [Port Reuse Timers](./nat-gateway-resource.md#port-reuse-timers).
+* NAT gateway holds on to SNAT ports after a connection closes before it's available to reuse to connect to the same destination endpoint over the internet. SNAT port reuse timer durations for TCP traffic vary depending on how the connection closes. To learn more, see [Port Reuse Timers](./nat-gateway-resource.md#port-reuse-timers).
 
 * A default TCP idle timeout of 4 minutes is used and can be increased to up to 120 minutes. Any activity on a flow can also reset the idle timer, including TCP keepalives. To learn more, see [Idle Timeout Timers](./nat-gateway-resource.md#idle-timeout-timers).
 
-* UDP traffic has an idle timeout timer of 4 minutes that cannot be changed.
+* UDP traffic has an idle timeout timer of 4 minutes that can't be changed.
 
-* UDP traffic has a port reset timer of 65 seconds for which a port is in hold down before it is available for reuse to the same destination endpoint.
+* UDP traffic has a port reset timer of 65 seconds for which a port is in hold down before it's available for reuse to the same destination endpoint.
 
 ## Pricing and SLA
 
@@ -128,3 +128,5 @@ For information on the SLA, see [SLA for Virtual Network NAT](https://azure.micr
 * Learn about the [NAT gateway resource](./nat-gateway-resource.md).
 
 * [Learn module: Introduction to Azure Virtual Network NAT](/training/modules/intro-to-azure-virtual-network-nat).
+
+* To learn more about architecture options for Azure Virtual Network NAT, see [Azure Well-Architected Framework review of an Azure NAT gateway](/azure/architecture/networking/guide/well-architected-network-address-translation-gateway).