update published applications tab name

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/cloudflared-parameters/index.mdx

@@ -144,7 +144,7 @@ To configure how `cloudflared` sends requests to your [published applications](/
 
 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Networks** > **Tunnels**.
 2. Choose a tunnel and select **Configure**.
-3. Select the **Published applications** tab.
+3. Select the **Published application routes** tab.
 4. Choose an application and select **Edit**.
 5. Under **Additional application settings**, modify one or more [origin configuration parameters](/cloudflare-one/connections/connect-networks/configure-tunnels/cloudflared-parameters/origin-parameters/).
 6. Select **Save**.

src/content/docs/cloudflare-one/connections/connect-networks/use-cases/rdp/rdp-cloudflared-authentication.mdx

@@ -16,7 +16,7 @@ Client-side `cloudflared` can be used in conjunction with [routing over WARP](/c
 
 1. Create a Cloudflare Tunnel by following our [dashboard setup guide](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/).
 
-2. In the **Published applications** tab, choose a domain from the drop-down menu and specify any subdomain (for example, `rdp.example.com`).
+2. In the **Published application routes** tab, choose a domain from the drop-down menu and specify any subdomain (for example, `rdp.example.com`).
 
 3. For **Service**, select _RDP_ and enter the [RDP listening port](https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/change-listening-port) of your server (for example, `localhost:3389`). It will likely be port `3389`.
 

src/content/docs/cloudflare-one/connections/connect-networks/use-cases/smb.mdx

@@ -67,7 +67,7 @@ The public hostname method can be implemented in conjunction with routing over W
 
 1. Create a Cloudflare Tunnel by following our [dashboard setup guide](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/).
 
-2. In the **Published applications** tab, choose a domain from the drop-down menu and specify any subdomain (for example, `smb.example.com`).
+2. In the **Published application routes** tab, choose a domain from the drop-down menu and specify any subdomain (for example, `smb.example.com`).
 
 3. For **Service**, select _TCP_ and enter the SMB listening port (for example, `localhost:445`). SMB drives listen on port `139` or `445` by default.
 

src/content/docs/hyperdrive/configuration/connect-to-private-database.mdx

@@ -48,7 +48,7 @@ First, create a [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks
 
 Your tunnel must be configured to use a public hostname on Cloudflare so that Hyperdrive can route requests to it. If you don't have a hostname on Cloudflare yet, you will need to [register a new hostname](/registrar/get-started/register-domain/) or [add a zone](/dns/zone-setups/) to Cloudflare to proceed.
 
-1. In the **Published applications** tab, choose a **Domain** and specify any subdomain or path information. This will be used in your Hyperdrive configuration to route to this tunnel.
+1. In the **Published application routes** tab, choose a **Domain** and specify any subdomain or path information. This will be used in your Hyperdrive configuration to route to this tunnel.
 
 2. In the **Service** section, specify **Type** `TCP` and the URL and configured port of your database, such as `localhost:5432` or `my-database-host.database-provider.com:5432`. This address will be used by the tunnel to route requests to your database.
 

src/content/partials/cloudflare-one/ssh/tunnel-public-hostname.mdx

@@ -4,7 +4,7 @@
 
 1. Create a Cloudflare Tunnel by following our [dashboard setup guide](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/).
 
-2. In the **Published applications** tab, choose a domain from the drop-down menu and specify any subdomain (for example, `ssh.example.com`).
+2. In the **Published application routes** tab, choose a domain from the drop-down menu and specify any subdomain (for example, `ssh.example.com`).
 
 3. For **Service**, select _SSH_ and enter `localhost:22`. If the SSH server is on a different machine from where you installed the tunnel, enter `<server IP>:22`.
 

src/content/partials/cloudflare-one/tunnel/add-public-hostname.mdx

@@ -3,7 +3,7 @@
 
 ---
 
-1. Go to the **Published applications** tab.
+1. Go to the **Published application routes** tab.
 
 2. Enter a subdomain and select a **Domain** from the dropdown menu. Specify any subdomain or path information.
 	:::note

src/content/partials/cloudflare-one/tunnel/cloud-public-hostname.mdx

@@ -5,7 +5,7 @@
 
 [Published applications](/cloudflare-one/connections/connect-networks/routing-to-tunnel/) allow anyone on the Internet to connect to HTTP resources hosted on your virtual private cloud (VPC). To add a published application for your Cloudflare Tunnel:
 
-1. In the **Published applications** tab, enter a hostname for the application (for example, `hellocloudflare.<your-domain>.com`).
+1. In the **Published application routes** tab, enter a hostname for the application (for example, `hellocloudflare.<your-domain>.com`).
 2. Under **Service**, enter `http://localhost:80`.
 3. Select **Save**.
 4. To test, open a browser and go to `http://hellocloudflare.<your-domain>.com`. You should see the **Hello Cloudflare!** test page.