name fix - tutorial hub spoke

Author: aimee-littleton

articles/virtual-network/nat-gateway/tutorial-hub-spoke-route-nat.md

@@ -1,6 +1,6 @@
 ---
 title: 'Tutorial: Use a NAT gateway with a hub and spoke network'
-titleSuffix: Azure Virtual Network NAT
+titleSuffix: Azure NAT Gateway
 description: Learn how to integrate a NAT gateway into a hub and spoke network with a network virtual appliance. 
 author: asudbring
 ms.author: allensu
@@ -15,7 +15,7 @@ ms.custom: template-tutorial
 
 A hub and spoke network is one of the building blocks of a highly available multiple location network infrastructure. The most common deployment of a hub and spoke network is done with the intention of routing all inter-spoke and outbound internet traffic through the central hub. The purpose is to inspect all of the traffic traversing the network with a Network Virtual Appliance (NVA) for security scanning and packet inspection.
 
-For outbound traffic to the internet, the network virtual appliance would typically have one network interface with an assigned public IP address. The NVA after inspecting the outbound traffic forwards the traffic out the public interface and to the internet. Azure Virtual Network NAT eliminates the need for the public IP address assigned to the NVA. Associating a NAT gateway with the public subnet of the NVA changes the routing for the public interface to route all outbound internet traffic through the NAT gateway. The elimination of the public IP address increases security and allows for the scaling of outbound source network address translation (SNAT) with multiple public IP addresses and or public IP prefixes.
+For outbound traffic to the internet, the network virtual appliance would typically have one network interface with an assigned public IP address. The NVA after inspecting the outbound traffic forwards the traffic out the public interface and to the internet. Azure NAT Gateway eliminates the need for the public IP address assigned to the NVA. Associating a NAT gateway with the public subnet of the NVA changes the routing for the public interface to route all outbound internet traffic through the NAT gateway. The elimination of the public IP address increases security and allows for the scaling of outbound source network address translation (SNAT) with multiple public IP addresses and or public IP prefixes.
 
 > [!IMPORTANT]
 > The NVA used in this article is for demonstration purposes only and is simulated with an Ubuntu virtual machine. The solution doesn't include a load balancer for high availability of the NVA deployment. Replace the Ubuntu virtual machine in this article with an NVA of your choice. Consult the vendor of the chosen NVA for routing and configuration instructions. A load balancer and availability zones is recommended for a highly available NVA infrastructure.
@@ -858,4 +858,4 @@ If you're not going to continue to use this application, delete the created reso
 
 Advance to the next article to learn how to use an Azure Gateway Load Balancer for highly available network virtual appliances:
 > [!div class="nextstepaction"]
-> [Gateway Load Balancer](../../load-balancer/gateway-overview.md)
+> [Gateway Load Balancer](../../load-balancer/gateway-overview.md)