More link fixes

Author: erikadoyle

articles/vmware-cloudsimple/azure-expressroute-connection.md

@@ -20,7 +20,7 @@ Virtual network connection allows you to:
 * Deploy KMS servers in your Azure subscription to encrypt your Private Cloud vSAN datastore.
 * Use hybrid applications where the web tier of the application runs in the public cloud while the application and database tiers run in your Private Cloud.
 
-[![Azure ExpressRoute Connection to virtual network](media/cloudsimple-azure-network-connection.png)](media/cloudsimple-azure-network-connection.png)
+![Azure ExpressRoute Connection to virtual network](media/cloudsimple-azure-network-connection.png)
 
 ## Set up a virtual network connection
 
@@ -29,10 +29,10 @@ To set up the virtual network connection to your Private Cloud, you need your au
 > [!TIP]
 > If you already have a Azure virtual network, gateway subnet, and virtual network gateway, you can skip to step 4.
 
-1. Create a virtual network on your Azure subscription and verify that the address space you select is different from the address space of your Private Cloud.  If you already have an Azure virtual network, you can use the existing one.  For details, see [Create a virtual network using the Azure portal](..\virtual-network\quick-create-portal.md).
-2. Create the gateway subnet on your Azure virtual network.  If you already have a gateway subnet in your Azure virtual network, you can use the existing one. For details, see [Create the gateway subnet](..\expressroute\expressroute-howto-add-gateway-portal-resource-manager.md#create-the-gateway-subnet).
-3. Create the virtual network gateway on your virtual network.  If you have an existing virtual network gateway, you can use the existing one. For details, see [Create the virtual network gateway](..\expressroute\expressroute-howto-add-gateway-portal-resource-manager.md#create-the-virtual-network-gateway).
-4. Create the connection between your virtual network and your Private Cloud by redeeming the authorization key as described in [Connect a virtual network to a circuit - different subscription](..\expressroute\expressroute-howto-linkvnet-portal-resource-manager.md#connect-a-vnet-to-a-circuit---different-subscription).
+1. Create a virtual network on your Azure subscription and verify that the address space you select is different from the address space of your Private Cloud.  If you already have an Azure virtual network, you can use the existing one.  For details, see [Create a virtual network using the Azure portal](../virtual-network/quick-create-portal.md).
+2. Create the gateway subnet on your Azure virtual network.  If you already have a gateway subnet in your Azure virtual network, you can use the existing one. For details, see [Create the gateway subnet](../expressroute/expressroute-howto-add-gateway-portal-resource-manager.md#create-the-gateway-subnet).
+3. Create the virtual network gateway on your virtual network.  If you have an existing virtual network gateway, you can use the existing one. For details, see [Create the virtual network gateway](../expressroute/expressroute-howto-add-gateway-portal-resource-manager.md#create-the-virtual-network-gateway).
+4. Create the connection between your virtual network and your Private Cloud by redeeming the authorization key as described in [Connect a virtual network to a circuit - different subscription](../expressroute/expressroute-howto-linkvnet-portal-resource-manager.md#connect-a-vnet-to-a-circuit---different-subscription).
 
 > [!WARNING]
 > If you are using an existing virtual network gateway and it has an ExpressRoute connection to the same location as the CloudSimple ExpressRoute circuit, the connection will not be established.  Create a new virtual network and follow the previous steps.

articles/vmware-cloudsimple/high-availability-vpn-connection.md

@@ -46,7 +46,7 @@ By default, CloudSimple VPN gateways are configured in IKEv1 mode along with the
 Complete the following tasks before you configure the on-premises firewall.
 
 1. Verify that your organization has [purchased](create-nodes.md) or [reserved](reserve-nodes.md) the required nodes and created at least one CloudSimple Private Cloud.
-2. [Configure a Site-to-Site VPN gateway](vpn-gateway.md/#set-up-a-site-to-site-vpn-gateway) between your on-premises network and your CloudSimple Private Cloud.
+2. [Configure a Site-to-Site VPN gateway](vpn-gateway.md#set-up-a-site-to-site-vpn-gateway) between your on-premises network and your CloudSimple Private Cloud.
 
 ## Configure on-premises Cisco ASA firewall
 
@@ -75,7 +75,7 @@ lifetime 28800
 
 ### 3. Create a tunnel group
 
-Create a tunnel group under the IPsec attributes. Configure the peer IP address and the tunnel pre-shared key, which you set when [configuring your Site-to-Site VPN gateway](vpn-gateway.md/#set-up-a-site-to-site-vpn-gateway).
+Create a tunnel group under the IPsec attributes. Configure the peer IP address and the tunnel pre-shared key, which you set when [configuring your Site-to-Site VPN gateway](vpn-gateway.md#set-up-a-site-to-site-vpn-gateway).
 
 ```
 tunnel-group <primary peer ip> type ipsec-l2l
@@ -151,11 +151,11 @@ The following is the NAT rule that is used. Ensure that the VPN traffic is not s
 
 Phase 1 output:
 
-![Phase 1 output for Cisco ASA firewall](../media/ha-vpn-connection-cisco-phase1.png)
+![Phase 1 output for Cisco ASA firewall](media/ha-vpn-connection-cisco-phase1.png)
 
 Phase 2 output:
 
-![Phase 2 output for Cisco ASA firewall](../media/ha-vpn-connection-cisco-phase2.png)
+![Phase 2 output for Cisco ASA firewall](media/ha-vpn-connection-cisco-phase2.png)
 
 ## Configure on-premises Palo Alto Networks firewall
 

articles/vmware-cloudsimple/media/network-virt-conn-page.png

@@ -23,7 +23,7 @@ In a region, you can create one Site-to-Site VPN gateway and one Point-to-Site V
 
 ## Point-to-site VPN
 
-To create a Point-to-Site VPN gateway, see [Create Point-to-Site VPN gateway](vpn-gateway.md/#create-point-to-site-vpn-gateway).
+To create a Point-to-Site VPN gateway, see [Create Point-to-Site VPN gateway](vpn-gateway.md#create-point-to-site-vpn-gateway).
 
 ### Connect to CloudSimple using Point-to-Site VPN
 
@@ -101,7 +101,7 @@ A Point-to-Site VPN connection resolves the DNS names of the first Private Cloud
 
 ## Site-to-Site VPN
 
-To create a Site-to-Site VPN gateway, see [Create Site-to-Site VPN gateway](vpn-gateway.md/#set-up-a-site-to-site-vpn-gateway).  Site-to-Site VPN connection from your on-premises network to your Private Cloud provides these benefits.  
+To create a Site-to-Site VPN gateway, see [Create Site-to-Site VPN gateway](vpn-gateway.md#set-up-a-site-to-site-vpn-gateway).  Site-to-Site VPN connection from your on-premises network to your Private Cloud provides these benefits.  
 
 * Accessibility of your Private Cloud vCenter from any workstation in your on-premises network
 * Use of your on-premises Active Directory as a vCenter identity source

articles/vmware-cloudsimple/set-up-vpn.md

@@ -117,4 +117,4 @@ The following table lists the number of concurrent client connections for prefix
 | Number of concurrent TCP connections | 124 | 60 | 28 | 12 | 4 |
 | Number of concurrent UDP connections | 124 | 60 | 28 | 12 | 4 |
 
-To connect using Point-to-Site VPN, see [Connect to CloudSimple using Point-to-Site VPN](set-up-vpn.md/#connect-to-cloudsimple-using-point-to-site-vpn).
+To connect using Point-to-Site VPN, see [Connect to CloudSimple using Point-to-Site VPN](set-up-vpn.md#connect-to-cloudsimple-using-point-to-site-vpn).