Merge pull request #297130 from cherylmc/vwan-fresh4

rewrite NVA article

Author: denrea

articles/virtual-wan/virtual-wan-route-table-nva-portal.md

@@ -5,7 +5,7 @@ services: virtual-wan
 author: cherylmc
 ms.service: azure-virtual-wan
 ms.topic: how-to
-ms.date: 08/24/2023
+ms.date: 03/27/2025
 ms.author: cherylmc
 # Customer intent: As someone with a networking background, I want to create a route table using the portal.
 ---
@@ -20,20 +20,21 @@ This article shows you how to steer traffic from a branch (on-premises site) con
 
 Verify that you have met the following criteria:
 
-*  You have a Network Virtual Appliance (NVA). A Network Virtual Appliance is a third-party software of your choice that is typically provisioned from Azure Marketplace in a virtual network.
+* You have a Network Virtual Appliance (NVA). A Network Virtual Appliance is a third-party software of your choice that is typically provisioned from Azure Marketplace in a virtual network.
 
-    * A private IP address must be assigned to the NVA network interface.
+  * A private IP address must be assigned to the NVA network interface.
 
-    * The NVA isn't deployed in the virtual hub. It must be deployed in a separate virtual network.
+  * The NVA isn't deployed in the virtual hub. It must be deployed in a separate virtual network.
 
-    *  The NVA virtual network may have one or many virtual networks connected to it. In this article, we refer to the NVA virtual network as an 'indirect spoke VNet'. These virtual networks can be connected to the NVA VNet by using VNet peering. The VNet Peering links are depicted by black arrows in the above figure between VNet 1, VNet 2, and NVA VNet.
-*  You have created two virtual networks. They will be used as spoke VNets.
+  * The NVA virtual network can have one or many virtual networks connected to it. In this article, we refer to the NVA virtual network as an 'indirect spoke VNet'. These virtual networks can be connected to the NVA VNet by using VNet peering. The VNet Peering links are depicted by black arrows in the previous figure between VNet 1, VNet 2, and NVA VNet.
 
-    * The VNet spoke address spaces are: VNet1: 10.0.2.0/24 and VNet2: 10.0.3.0/24. If you need information on how to create a virtual network, see [Create a virtual network](../virtual-network/quick-create-portal.md).
+* You have created two virtual networks. They'll be used as spoke VNets.
 
-    * Ensure there are no virtual network gateways in any of the VNets.
+  * The VNet spoke address spaces are: VNet1: 10.0.2.0/24 and VNet2: 10.0.3.0/24. If you need information on how to create a virtual network, see [Create a virtual network](../virtual-network/quick-create-portal.md).
 
-    * The VNets don't require a gateway subnet.
+  * Ensure there are no virtual network gateways in any of the VNets.
+
+  * The VNets don't require a gateway subnet.
 
 ## <a name="signin"></a>1. Sign in
 
@@ -47,7 +48,7 @@ Create a virtual WAN. You can use the following example values, or replace with
 * **Resource group:** testRG
 * **Location:** West US
 
-[!INCLUDE [Create a virtual WAN](../../includes/virtual-wan-tutorial-vwan-include.md)]
+[!INCLUDE [Create a virtual WAN](../../includes/virtual-wan-create-vwan-include.md)]
 
 ## <a name="hub"></a>3. Create a hub
 
@@ -57,7 +58,7 @@ Create the hub. You can use the following example values, or replace with your o
 * **Name:** westushub
 * **Hub private address space:** 10.0.1.0/24
 
-[!INCLUDE [Create a hub](../../includes/virtual-wan-hub-blank.md)]
+[!INCLUDE [Create a hub](../../includes/virtual-wan-hub-basics.md)]
 
 ## <a name="route"></a>4. Create and apply a hub route table
 
@@ -67,19 +68,19 @@ Update the hub with a hub route table. Use the following example values:
 * **DMZ NVA network interface private IP address:** 10.0.4.5
 
 1. Navigate to your virtual WAN.
-2. Click the hub for which you want to create a route table.
-3. Click the **...**, and then click **Edit virtual hub**.
-4. On the **Edit virtual hub** page, scroll down and select the checkbox **Use table for routing**.
-5. In the **If destination prefix is** column, add the address spaces. In the **Send to next hop** column, add the DMZ NVA network interface private IP address.
+1. Click the hub for which you want to create a route table.
+1. Click the **...**, and then click **Edit virtual hub**.
+1. On the **Edit virtual hub** page, scroll down and select the checkbox **Use table for routing**.
+1. In the **If destination prefix is** column, add the address spaces. In the **Send to next hop** column, add the DMZ NVA network interface private IP address.
 
    > [!NOTE]
    > The DMZ NVA network is applicable to the local hub.
-   
-6. Click **Confirm** to update the hub resource with the route table settings.
+
+1. Click **Confirm** to update the hub resource with the route table settings.
 
 ## <a name="connections"></a>5. Create the VNet connections
 
-Create a virtual network connection from each indirect spoke VNet (VNet1 and VNet2) to the hub. These virtual network connections are depicted by the blue arrows in the above figure. Then, create a VNet connection from the NVA VNet to the hub (black arrow in the figure).
+Create a virtual network connection from each indirect spoke VNet (VNet1 and VNet2) to the hub. These virtual network connections are depicted by the blue arrows in the previous figure. Then, create a VNet connection from the NVA VNet to the hub (black arrow in the figure).
 
  For this step, you can use the following values:
 
@@ -92,14 +93,14 @@ Create a virtual network connection from each indirect spoke VNet (VNet1 and VNe
 Repeat the following procedure for each virtual network that you want to connect.
 
 1. On the page for your virtual WAN, click **Virtual network connections**.
-2. On the virtual network connection page, click **+Add connection**.
-3. On the **Add connection** page, fill in the following fields:
+1. On the virtual network connection page, click **+Add connection**.
+1. On the **Add connection** page, fill in the following fields:
 
     * **Connection name** - Name your connection.
     * **Hubs** - Select the hub you want to associate with this connection.
     * **Subscription** - Verify the subscription.
     * **Virtual network** - Select the virtual network you want to connect to this hub. The virtual network can't have an already existing virtual network gateway.
-4. Click **OK** to create the connection.
+1. Click **OK** to create the connection.
 
 ## Next steps