Update virtual-network-troubleshoot-peering-issues.md

Author: ShawnJackson

articles/virtual-network/virtual-network-troubleshoot-peering-issues.md

@@ -24,11 +24,11 @@ This troubleshooting guide provides steps to help you resolve most [virtual netw
 
 ![Diagram of virtual network peering](./media/virtual-network-troubleshoot-peering-issues/4489538_en_1.png)
 
-## Scenario 1: Configure virtual network peering between two virtual networks
+## Configure virtual network peering between two virtual networks
 
 Are the virtual networks in the same subscription or in different subscriptions?
 
-### Connection type 1: The virtual networks are in the same subscription
+### The virtual networks are in the same subscription
 
 To configure virtual network peering for the virtual networks that are in the same subscription, use the methods in the following articles:
 
@@ -50,31 +50,31 @@ To configure virtual network peering for the virtual networks that are in the sa
 
 For more information, see the [requirements and constraints](https://docs.microsoft.com/azure/virtual-network/virtual-network-peering-overview#requirements-and-constraints) of global peering.
 
-### Connection type 2: The virtual networks are in different subscriptions or Active Directory tenants
+### The virtual networks are in different subscriptions or Active Directory tenants
 
 To configure virtual network peering for virtual networks in different subscriptions or Active Directory tenants, see [Create peering in different subscriptions for Azure CLI](https://docs.microsoft.com/azure/virtual-network/create-peering-different-subscriptions#cli).
 
 > [!Note]
 > To configure network peering, you must have **Network Contributor** permissions in both subscriptions. For more information, see [Peering permissions](virtual-network-manage-peering.md#permissions).
 
-## Scenario 2: Configure virtual network peering with hub-spoke topology that uses on-premises resources
+## Configure virtual network peering with hub-spoke topology that uses on-premises resources
 
 ![Diagram of virtual network peering with on-premises spoke](./media/virtual-network-troubleshoot-peering-issues/4488712_en_1a.png)
 
-### Connection type 1: For a site-to-site connection or an ExpressRoute connection
+### For a site-to-site connection or an ExpressRoute connection
 
 Follow the steps in: [Configure VPN gateway transit for virtual network peering](https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-peering-gateway-transit?toc=/azure/virtual-network/toc.json).
 
-### Connection type 2: For point-to-site connections
+### For point-to-site connections
 
 1. Follow the steps in: [Configure VPN gateway transit for virtual network peering](https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-peering-gateway-transit?toc=/azure/virtual-network/toc.json).
 2. After virtual network peering is established or changed, download and reinstall the point-to-site package so that the point-to-site clients get the updated routes to the spoke virtual network.
 
-## Scenario 3: Configure virtual network peering with hub-spoke topology virtual network
+## Configure virtual network peering with hub-spoke topology virtual network
 
 ![Diagram of virtual network peering with a virtual network spoke](./media/virtual-network-troubleshoot-peering-issues/4488712_en_1b.png)
 
-### Connection type 1: The virtual networks are in the same region
+### The virtual networks are in the same region
 
 
 1. In the hub virtual network, configure a network virtual appliance (NVA).
@@ -87,7 +87,7 @@ For more information, see [Service chaining](https://docs.microsoft.com/azure/vi
 
 For help with troubleshooting the NVA device setup and routing, see [Network virtual appliance issues in Azure](https://docs.microsoft.com/azure/virtual-network/virtual-network-troubleshoot-nva).
 
-### Connection type 2: The virtual networks are in different regions
+### The virtual networks are in different regions
 
 Transit over global virtual network peering is now supported. Connectivity does not work over global virtual network peering for the following resources:
 
@@ -103,11 +103,11 @@ Transit over global virtual network peering is now supported. Connectivity does
 
 To learn more about global peering requirements and restraints, see [Virtual network peering](https://docs.microsoft.com/azure/virtual-network/virtual-network-peering-overview#requirements-and-constraints).
 
-## Scenario 4: Troubleshoot a connectivity issue between two peered virtual networks
+## Troubleshoot a connectivity issue between two peered virtual networks
 
 Sign in to the [Azure portal](https://portal.azure.com/) with an account that has the necessary [roles and permissions](virtual-network-manage-peering.md#permissions). Select the virtual network, select **Peering**, and then check the **Status** field. What is the status?
 
-### Connection type 1: The peering status is "Connected"
+### The peering status is "Connected"
 
 To troubleshoot this issue:
 
@@ -123,7 +123,7 @@ To troubleshoot this issue:
    1. Start a network trace on the destination VM. For Windows, you can use **Netsh**. For Linux, use **TCPDump**.
    2. Run **TcpPing** or **PsPing** from the source to the destination IP.
 
-   * This is an example of a **TcpPing** command: `tcping64.exe -t <destination VM address> 3389`
+      This is an example of a **TcpPing** command: `tcping64.exe -t <destination VM address> 3389`
 
    3. After the **TcpPing** is complete, stop the network trace on the destination.
    4. If packets arrive from the source, there is no networking issue. Examine both the VM firewall and the application listening on that port to locate the configuration issue.
@@ -143,22 +143,22 @@ To troubleshoot this issue:
 
 For more information, see the [requirements and constraints](https://docs.microsoft.com/azure/virtual-network/virtual-network-peering-overview#requirements-and-constraints) of global peering.
 
-### Connection type 2: The peering status is "Disconnected"
+### The peering status is "Disconnected"
 
 To resolve this issue, delete the peering from both virtual networks, and then re-create them.
 
-## Scenario 5: Troubleshoot a connectivity issue between a hub-spoke virtual network and an on-premises resource
+## Troubleshoot a connectivity issue between a hub-spoke virtual network and an on-premises resource
 
 Does your network use a third-party NVA or VPN gateway?
 
-### Connection type 1: My network uses a third-party NVA or VPN gateway
+### My network uses a third-party NVA or VPN gateway
 
 To troubleshoot connectivity issues that affect a third-party NVA or VPN gateway, see the following articles:
 
 * [NVA troubleshooter](https://docs.microsoft.com/azure/virtual-network/virtual-network-troubleshoot-nva)
 * [Service chaining](https://docs.microsoft.com/azure/virtual-network/virtual-network-peering-overview#service-chaining)
 
-### Connection type 2: My network does not use a third-party NVA or VPN gateway
+### My network does not use a third-party NVA or VPN gateway
 
 Do the hub virtual network and the spoke virtual network have a VPN gateway?
 
@@ -182,13 +182,13 @@ For point-to-site connections:
 * On the virtual network that doesn't have a gateway, verify that the **Use remote gateway** check box is selected.
 * Download and reinstall the point-to-site client package. Virtual network routes that are newly peered don't automatically add routes to point-to-site clients.
 
-## Scenario 6: Troubleshoot a hub-spoke network connectivity issue between spoke virtual networks in the same region
+## Troubleshoot a hub-spoke network connectivity issue between spoke virtual networks in the same region
 
 A hub network must include an NVA. Configure UDRs in spokes that have an NVA set as the next hop, and enable **Allow forwarded traffic** in the hub virtual network.
 
 For more information, see [Service chaining](https://docs.microsoft.com/azure/virtual-network/virtual-network-peering-overview#service-chaining), and discuss these requirements with the [NVA vendor](https://support.microsoft.com/help/2984655/support-for-azure-market-place-for-virtual-machines) of your choice.
 
-## Scenario 7: Troubleshoot a hub-spoke network connectivity issue between spoke virtual networks in different regions
+## Troubleshoot a hub-spoke network connectivity issue between spoke virtual networks in different regions
 
 Transit over global virtual network peering is now supported. Connectivity doesn't work over global virtual network peering for the following resources:
 
@@ -204,7 +204,7 @@ Transit over global virtual network peering is now supported. Connectivity doesn
 
 For more information, see the [requirements and constraints](https://docs.microsoft.com/azure/virtual-network/virtual-network-peering-overview#requirements-and-constraints) of global peering and [Different VPN Topologies](https://blogs.msdn.microsoft.com/igorpag/2016/02/11/hubspoke-daisy-chain-and-full-mesh-vnet-topologies-in-azure-arm-v2/).
 
-## Scenario 8: Troubleshoot a hub-spoke network connectivity issue between a web app and the spoke virtual network
+## Troubleshoot a hub-spoke network connectivity issue between a web app and the spoke virtual network
 
 To troubleshoot this issue:
 
@@ -214,23 +214,23 @@ To troubleshoot this issue:
 
 For more information, see the following articles:
 
-* [Integrate your app with an Azure Virtual Network](https://docs.microsoft.com/azure/app-service/web-sites-integrate-with-vnet)
+* [Integrate your app with an Azure virtual network](https://docs.microsoft.com/azure/app-service/web-sites-integrate-with-vnet)
 * [About Point-to-Site VPN routing](https://docs.microsoft.com/azure/vpn-gateway/vpn-gateway-about-point-to-site-routing)
 
-## Scenario 9: Troubleshoot a virtual network peering configuration error message 
+## Troubleshoot a virtual network peering configuration error message 
 
-### Error 1: Current tenant `<TENANT ID>` isn't authorized to access linked subscription
+### Current tenant `<TENANT ID>` isn't authorized to access linked subscription
 
 To resolve this issue, see [Create peering - Azure CLI](https://docs.microsoft.com/azure/virtual-network/create-peering-different-subscriptions#cli).
 
-### Error 2: Not connected
+### Not connected
 
 To resolve this issue, delete the peering from both virtual networks, and then recreate them.
 
-### Error 3: Failed to peer a Databricks virtual network
+### Failed to peer a Databricks virtual network
 
 To resolve this issue, configure the virtual network peering under **Azure Databricks**, and then specify the target virtual network by using **Resource ID**. For more information, see [Peer a Databricks virtual network to a remote virtual network](https://docs.azuredatabricks.net/administration-guide/cloud-configurations/azure/vnet-peering.html#id2).
 
 ## Next steps
 
-* [Troubleshooting connectivity problems between Azure VMs](https://docs.microsoft.com/azure/virtual-network/virtual-network-troubleshoot-connectivity-problem-between-vms)
+* [Troubleshooting connectivity problems between Azure VMs](https://docs.microsoft.com/azure/virtual-network/virtual-network-troubleshoot-connectivity-problem-between-vms)