Merge pull request #267356 from aimee-littleton/patch-188

Update nat-gateway-resource.md

Author: prmerger-automator[bot]

articles/nat-gateway/nat-availability-zones.md

@@ -27,7 +27,7 @@ Virtual networks and their subnets are regional. Subnets aren't restricted to a
 
 ## Zonal
 
-You can place your NAT gateway resource in a specific zone for a region. When NAT gateway is deployed to a specific zone, it provides outbound connectivity to the internet explicitly from that zone. The public IP address or prefix configured to NAT gateway must match the same zone. NAT gateway resources with public IP addresses from a different zone, zone-redundancy or with no zone aren't allowed.
+You can place your NAT gateway resource in a specific zone for a region. When NAT gateway is deployed to a specific zone, it provides outbound connectivity to the internet explicitly from that zone. NAT gateway resources assigned to an availability zone can be attached to public IP addresses either from the same zone or that are zone redundant. Public IP addresses from a different availability zone or no zone aren't allowed.
 
 NAT gateway can provide outbound connectivity for virtual machines from other availability zones different from itself. The virtual machine’s subnet needs to be configured to the NAT gateway resource to provide outbound connectivity. Additionally, multiple subnets can be configured to the same NAT gateway resource. 
 

articles/nat-gateway/nat-gateway-resource.md

@@ -63,7 +63,7 @@ A single NAT gateway can scale up to 16 IP addresses. Each NAT gateway public IP
 
 A NAT gateway can be created in a specific availability zone or placed in **no zone**. When a NAT gateway is placed in no zone, Azure selects a zone for the NAT gateway to reside in.
 
-Zone redundant public IP addresses can be used with no zone NAT gateway resources.
+Zone redundant public IP addresses can be used with zonal or no zone NAT gateway resources.
 
 The recommendation is to configure a NAT gateway to individual availability zones. Additionally, it should be attached to subnets with private instances from the same zone. For more information about availability zones and Azure NAT Gateway, see [Availability zones design considerations](/azure/nat-gateway/nat-availability-zones#design-considerations).
 

articles/nat-gateway/troubleshoot-nat.md

@@ -182,7 +182,7 @@ NAT gateway can be used with public IP addresses designated to a specific zone,
 | NAT gateway availability zone designation | Public IP address / prefix designation that can be used |
 |---|---|
 | No zone | Zone-redundant, No zone, or Zonal (the public IP zone designation can be any zone within a region in order to work with a no zone NAT gateway) |
-| Designated to a specific zone | The public IP address zone must match the zone of the NAT gateway |
+| Designated to a specific zone | Zone-redundant or Zonal Public IPs can be used |
 
 >[!NOTE]
 >If you need to know the zone that your NAT gateway resides in, make sure to designate it to a specific availability zone.