Acrolinx and updates - single doc submission

Author: Michael Bender

articles/virtual-network-manager/how-to-deploy-hub-spoke-topology-with-azure-firewall.md

@@ -5,12 +5,12 @@ author: mbender-ms
 ms.author: mbender
 ms.service: virtual-network-manager
 ms.topic: how-to
-ms.date: 05/22/2024
+ms.date: 06/04/2024
 ---
 
 # How to deploy hub and spoke topology with Azure Firewall
 
-In this article, you learn how to deploy a hub and spoke topology with Azure Firewall using Azure Virtual Network Manager (AVNM). You create a network manager instance, and implements network groups for trusted and untrusted traffic. Next, you deploy a connectivity configuration for defining your hub and spoke topology. When deploying the connectivity configuration, you have a choice of adding [direct connectivity](concept-connectivity-configuration.md#direct-connectivity) for direct, trusted communication between spoke virtual networks, or requiring spokes to communicate through the hub network.  You finish by deploying a routing configuration to route all traffic to Azure Firewall, except the traffic within the same virtual network when the virtual networks are trusted.
+In this article, you learn how to deploy a hub and spoke topology with Azure Firewall using Azure Virtual Network Manager (AVNM). You create a network manager instance, and implement network groups for trusted and untrusted traffic. Next, you deploy a connectivity configuration for defining your hub and spoke topology. When deploying the connectivity configuration, you have a choice of adding [direct connectivity](concept-connectivity-configuration.md#direct-connectivity) for direct, trusted communication between spoke virtual networks, or requiring spokes to communicate through the hub network.  You finish by deploying a routing configuration to route all traffic to Azure Firewall, except the traffic within the same virtual network when the virtual networks are trusted.
 
 Many organizations use Azure Firewall to protect their virtual networks from threats and unwanted traffic, and they route all traffic to Azure Firewall except trusted traffic within the same virtual network. Traditionally, setting up such a scenario is cumbersome because new user-defined routes (UDRs) need to be created for each new subnet, and all route tables have different UDRs. UDR management in Azure Virtual Network Manager can help you easily achieve this scenario by creating a routing rule that routes all traffic to Azure Firewall, except the traffic within the same virtual network.
 

articles/virtual-network-manager/media/how-to-deploy-spoke-to-spoke-topology-two-hubs/spoke-to-spoke-two-hubs-topology-network-manager.png

@@ -5,7 +5,7 @@
  author: mbender
  ms.service: virtual-network-manager
  ms.topic: include
- ms.date: 05/08/2024
+ ms.date: 06/04/2024
  ms.author: mbender-ms
 ms.custom: include-file
 ---

includes/virtual-network-manager-create-2-spoke-vnets.md

@@ -5,7 +5,7 @@ services: virtual-network-manager
 author: mbender
 ms.service: virtual-network-manager
 ms.topic: include
-ms.date: 05/21/2024
+ms.date: 06/04/2024
 ms.author: mbender-ms
 ms.custom: include-file
 ---

includes/virtual-network-manager-create-spoke-network-group.md

@@ -5,7 +5,7 @@
  author: mbender
  ms.service: virtual-network-manager
  ms.topic: include
- ms.date: 05/08/2024
+ ms.date: 06/04/2024
  ms.author: mbender-ms
 ms.custom: include-file
 ---
@@ -29,7 +29,7 @@ In this step, you deploy a Virtual Network Manager instance with *user defined r
     | **Description** | *(Optional)* Provide a description about this Virtual Network Manager instance and the task it's managing. |
     | [Features](../articles/virtual-network-manager/concept-network-manager-scope.md#features) | Select **User defined routing** and **Connectivity** from the dropdown list. |
 
-    :::image type="content" source="media/virtual-network-manager-create-udr-instance/create-network-manager-instance..png" alt-text="Screenshot of Create a network manager window with values for connectivity and user defined routing.":::
+    :::image type="content" source="media/virtual-network-manager-create-udr-instance/create-network-manager-instance.png" alt-text="Screenshot of Create a network manager window with values for connectivity and user defined routing.":::
 
 1. Select the **Management scope** tab or select **Next: Management scope >** to continue.
 

includes/virtual-network-manager-create-udr-instance.md

@@ -5,7 +5,7 @@
  author: mbender
  ms.service: virtual-network-manager
  ms.topic: include
- ms.date: 05/21/2024
+ ms.date: 06/04/2024
  ms.author: mbender-ms
 ms.custom: include-file
 ---
@@ -27,7 +27,7 @@ In this task, you create a connectivity configuration that includes your network
     > [!IMPORTANT]
     > If you enable direct connectivity, you must have a routing configuration with direct routing within the virtual network. If you enable global mesh, you must have a routing configuration with global mesh enabled.
    
-   :::image type="content" source="media/virtual-network-manager-deploy-hub-spoke-topology/create-direct-connectivity-hub-spoke-configuration.png" alt-text="Screenshot of Create a connectivity configuration configuration for hub and spoke with direct connectivity.":::
+   :::image type="content" source="media/virtual-network-manager-deploy-hub-spoke-topology/create-direct-connectivity-hub-spoke-configuration.png" alt-text="Screenshot of Create a connectivity configuration for hub and spoke with direct connectivity.":::
 
 5. Choose **Next: Visualization >** to review the connectivity configuration then select **Review + create** > **Create**.
 
@@ -37,7 +37,7 @@ In this task, you deploy the connectivity configuration to create the hub and sp
 
 1. In the network manager instance, select **Configurations** under **Settings** then select the connectivity configuration you created.
 2. From the task bar, select **Deploy**.
-3. In the **Deploy a configuration** window, select the you connectivity configuration you created, and select the **Target Regions** you wish to deploy the configuration to.
+3. In the **Deploy a configuration** window, select the connectivity configuration you created, and select the **Target Regions** you wish to deploy the configuration to.
 
     > [!IMPORTANT]
     > The hub and spoke topology is created in the selected regions. Make sure to select the regions where your hub and spoke virtual networks are deployed.