connect server

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-networks/deployment-guides/aws.mdx

@@ -98,7 +98,7 @@ EOF
 
 [Private network routes](/cloudflare-one/connections/connect-networks/private-net/cloudflared/) allow users to connect to your virtual private cloud (VPC) using the WARP client. To add a private network route for your Cloudflare Tunnel:
 
-1. In the **Private Network** tab, enter the **Private IPv4 address** of your AWS instance (for example, `172.31.19.0`). You can expand the IP range later if necessary.
+1. In the **Private Networks** tab, enter the **Private IPv4 address** of your AWS instance (for example, `172.31.19.0`). You can expand the IP range later if necessary.
 2. In your [Split Tunnel configuration](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#add-a-route), make sure the private IP is routing through WARP. For example, if you are using Split Tunnels in Exclude mode, delete `172.16.0.0/12`. We recommend re-adding the IPs that are not explicitly used by your AWS instance.
 
 		To determine which IP addresses to re-add, subtract your AWS instance IPs from `172.16.0.0/12`:

src/content/docs/cloudflare-one/connections/connect-networks/deployment-guides/google-cloud-platform.mdx

@@ -77,7 +77,7 @@ To complete the following procedure, you will need to:
 
 To configure a private network route for your Cloudflare Tunnel:
 
-1. In the **Private Network** tab, enter the **Internal IP** of your GCP VM instance (for example, `10.0.0.2`). You can expand the IP range later if necessary.
+1. In the **Private Networsk** tab, enter the **Internal IP** of your GCP VM instance (for example, `10.0.0.2`). You can expand the IP range later if necessary.
 2. In your [Split Tunnel configuration](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/#add-a-route), make sure the internal IP is routing through WARP. For example, if you are using Split Tunnels in Exclude mode, delete `10.0.0.0/8`. We recommend re-adding the IPs that are not explicitly used by your GCP VM.
 
 		To determine which IP addresses to re-add, subtract your GCP instance IPs from `10.0.0.0/8`:

src/content/docs/cloudflare-one/connections/connect-networks/private-net/cloudflared/connect-private-hostname.mdx

@@ -45,7 +45,9 @@ This section covers how to enable remote access to a private hostname applicatio
 
 ### 1. Connect the server to Cloudflare
 
-Hostname must be unique for an account (1:M mapping from hostname to Tunnel)
+<Render file="tunnel/create-tunnel"/>
+
+9. In the **Hostname routes** tab, enter the fully qualified domain name (FDQN) that represents your application (for example, `wiki.internal.local`).
 
 	<Details header="Hostname format restrictions">
 			- Less than 255 characters
@@ -55,6 +57,7 @@ Hostname must be unique for an account (1:M mapping from hostname to Tunnel)
 			- Hostnames with non-Latin characters must be Punycode encoded and include the [ACE prefix](https://en.wikipedia.org/wiki/Punycode#ACE_prefix_for_internationalized_domain_names). For example, to represent `例.internal.local`, enter `xn--fsq.internal.local`.
 	</Details>
 
+10. Select **Complete setup**.
 
 ### 2. Set up the client
 

src/content/docs/cloudflare-one/connections/connect-networks/private-net/cloudflared/tunnel-virtual-networks.mdx

@@ -60,7 +60,7 @@ The following example demonstrates how to add two overlapping IP routes to Cloud
          2. Select **Create a tunnel**.
          3. Name your tunnel `Staging tunnel` and select **Save tunnel**.
          4. Install the connector within your staging environment.
-         5. In the **Private Network** tab, add `10.128.0.1/32`.
+         5. In the **Private Networks** tab, add `10.128.0.1/32`.
          6. Select **Additional settings**. Under **Virtual networks**, select *staging-vnet*.
          7. Save the tunnel.
          8. Repeat Steps 2a-2g to create another tunnel called `Production tunnel`. Be sure to install the connector within your production environment and assign the route to *production-vnet*.

src/content/docs/cloudflare-one/tutorials/user-selectable-egress-ips.mdx

@@ -73,7 +73,7 @@ After creating your virtual networks, route your private network CIDRs over each
 
 1. Go to **Networks** > **Tunnels**.
 2. Select your tunnel routing `10.0.0.0/8`, then select **Configure**.
-3. Go to **Private Network**. Select the `10.0.0.0/8` route.
+3. Go to **Private Networks**. Select the `10.0.0.0/8` route.
 4. In **Additional settings**, choose your first virtual network. For example, `vnet-AMER`.
 5. Select **Save private network**.
 6. To route `10.0.0.0/8` over another virtual network, select **Add a private network**.

src/content/docs/load-balancing/private-network/tunnels-setup.mdx

@@ -28,7 +28,7 @@ To assign the virtual network to the tunnel:
 
 1. Go to **Networks** > **Tunnels**.
 2. Select the tunnel you created in the previous steps and select **Configure**.
-3. Under **Private Network**, select **Add a private network**.
+3. Under **Private Networks**, select **Add a private network**.
 4. Specify an IP range under **CIDR** and select the virtual network under **Additional settings**.
 5. Select **Save private network**.
 

src/content/partials/cloudflare-one/tunnel/cloud-create-tunnel.mdx

@@ -5,7 +5,7 @@ inputParameters: param1;;param2
 
 import { Markdown } from "~/components"
 
-Next, we will create a Cloudflare Tunnel in Zero Trust and run the tunnel on the {props.one}.
+Create a Cloudflare Tunnel in Zero Trust and run the tunnel on the {props.one}.
 
 1. Log in to [Zero Trust](https://one.dash.cloudflare.com) and go to **Networks** > **Tunnels**.