Merge pull request #104649 from christiankuhtz/patch-272

tweak

Author: PRMerger8

articles/virtual-network/nat-overview.md

@@ -45,7 +45,7 @@ NAT is compatible with standard SKU [public IP address resources](./virtual-netw
 
 All outbound traffic for the subnet is processed by NAT automatically without any customer configuration.  User-defined routes aren't necessary. NAT takes precedence over other [outbound scenarios](../load-balancer/load-balancer-outbound-connections.md) and replaces the default Internet destination of a subnet.
 
-## SNAT with multiple IP addresses for scale
+## On-demand SNAT with multiple IP addresses for scale
 
 NAT uses "port network address translation" (PNAT or PAT) and is recommended for most workloads. Dynamic or divergent workloads can be easily accommodated with on-demand outbound flow allocation. Extensive pre-planning, pre-allocation, and ultimately overprovisioning of outbound resources is avoided. SNAT port resources are shared and available across all subnets using a specific NAT gateway resource and are provided when needed.