Skip to content

Commit 8461648

Browse files
committed
minor edits
1 parent a3721eb commit 8461648

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-vmware/enable-vmware-cds-with-azure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Organization VDCs can be part of a single organization but it still provides iso
3434

3535
### Prerequisites
3636
- Organization VDC is configured with an Edge gateway and has Public IPs assigned to it to establish IPSEC VPN by provider.
37-
- Tenants have created a routed Organization VDC network in tenant’s Virtual datacenter.
37+
- Tenants have created a routed Organization VDC network in tenant’s Virtual datacenter.
3838
- Test VM1 and VM2 are created in the Organization VDC1 and VDC2 respectively. Both VMs are connected to the routed orgVDC network in their respective VDCs.
3939
- Have a dedicated [Azure vNET](tutorial-configure-networking.md#create-a-vnet-manually) configured for each tenant. For this example, we created Tenant1-vNet and Tenant2-vNet for tenant1 and tenant2 respectively.
4040
- Create an [Azure Virtual network gateway](tutorial-configure-networking.md#create-a-virtual-network-gateway) for vNETs created earlier.
@@ -65,7 +65,7 @@ To create an Azure virtual network gateway, see the [create-a-virtual-network-ga
6565
1. Select tenant1 VPN Gateway (created earlier) and then select **Connection** (in left pane) to add new IPSEC connection with tenant1 orgVDC Edge gateway.
6666
1. Enter the following details.
6767

68-
| **Name** | **Connection name** |
68+
| **Name** | **Connection** |
6969
|:---------- | :--------------|
7070
| Connection Type | Site to Site |
7171
| VPN Gateway | Tenant’s VPN Gateway |

0 commit comments

Comments
 (0)