Apply suggestions from code review

Author: ranbel

src/content/docs/cloudflare-one/account-limits.mdx

@@ -64,7 +64,7 @@ This page lists the default account limits for rules, applications, fields, and
 | Feature                                  | Limit |
 | ---------------------------------------- | ----- |
 | Tunnels per account                      | 1,000 |
-| Combined hostname and IP routes per tunnel  | 1,000 |
+| Routes per tunnel  | 1,000 |
 | Active `cloudflared` replicas per tunnel | 25    |
 
 ## Digital Experience Monitoring (DEX)

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

@@ -147,4 +147,4 @@ To configure how `cloudflared` sends requests to your [published applications](/
 3. Select the **Published applications** 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 hostname**.
+6. Select **Save**.

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

@@ -20,7 +20,7 @@ Client-side `cloudflared` can be used in conjunction with [routing over WARP](/c
 
 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`.
 
-4. Save the configuration.
+4. Select **Save**.
 
 ## 2. (Recommended) Create an Access application
 

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

@@ -71,11 +71,11 @@ The public hostname method can be implemented in conjunction with routing over W
 
 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.
 
-4. Save the configuration.
+4. Select **Save**.
 
 ## 2. (Recommended) Create an Access application
 
-By default, anyone on the Internet can connect to the server using its public hostname. To allow or block specific users, create a [self-hosted application](/cloudflare-one/applications/configure-apps/self-hosted-public-app/) in Cloudflare Access.
+By default, anyone on the Internet can connect to the server using the hostname of the published application. To allow or block specific users, create a [self-hosted application](/cloudflare-one/applications/configure-apps/self-hosted-public-app/) in Cloudflare Access.
 
 ### 3. Connect as a user
 

src/content/docs/data-localization/compatibility.mdx

@@ -131,7 +131,7 @@ The table below provides a summary of the Data Localization Suite product's beha
 [^15]: Can be localized to US FedRAMP Moderate Domestic region only.
 [^16]: Customer Metadata Boundary can be used to limit data transfer outside region, but Access User Logs will not be available outside US region.
 [^17]: Currently may only be used with US FedRAMP region.
-[^18]: When Cloudflare Tunnel connects to Cloudflare, the connectivity options available are the Global Region (default) and [US FedRAMP Moderate Domestic region](/cloudflare-one/connections/connect-networks/configure-tunnels/cloudflared-parameters/run-parameters/#region). For incoming requests to the Cloudflare Edge, Regional Services only applies when using [public hostnames on Cloudflare](/cloudflare-one/connections/connect-networks/routing-to-tunnel/). In this case, the region associated with the DNS record will apply.
+[^18]: When Cloudflare Tunnel connects to Cloudflare, the connectivity options available are the Global Region (default) and [US FedRAMP Moderate Domestic region](/cloudflare-one/connections/connect-networks/configure-tunnels/cloudflared-parameters/run-parameters/#region). For incoming requests to the Cloudflare Edge, Regional Services only applies when using [published applications](/cloudflare-one/connections/connect-networks/routing-to-tunnel/). In this case, the region associated with the DNS record will apply.
 [^19]: Uses Gateway HTTP and CASB.
 [^20]: You can [bring your own certificate](https://blog.cloudflare.com/bring-your-certificates-cloudflare-gateway/) to Gateway but these cannot yet be restricted to a specific region.
 [^21]: Gateway HTTP supports Regional Services. Gateway DNS does not yet support regionalization. <br/> ICMP proxy and WARP-to-WARP proxy are not available to Regional Services users.

src/content/docs/learning-paths/clientless-access/connect-private-applications/create-tunnel.mdx

@@ -18,9 +18,9 @@ To create a Cloudflare Tunnel:
 
 <Render file="tunnel/create-tunnel" product="cloudflare-one" />
 
-## Connect an application
+## Publish an application
 
-To add a published application to the tunnel:
+To route an application to a public hostname:
 
 <Render file="tunnel/add-public-hostname" product="cloudflare-one" />
 

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

@@ -8,6 +8,6 @@
 
 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`.
 
-4. Save the configuration.
+4. Select **Save**.
 
 5. (Recommended) Add a [self-hosted application](/cloudflare-one/applications/configure-apps/self-hosted-public-app/) to Cloudflare Access in order to manage access to your server.

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

@@ -7,7 +7,7 @@
 
 1. In the **Published applications** tab, enter a hostname for the application (for example, `hellocloudflare.<your-domain>.com`).
 2. Under **Service**, enter `http://localhost:80`.
-3. Save the configuration.
+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.
 
 You can optionally [create an Access application](/cloudflare-one/applications/configure-apps/self-hosted-public-app/) to control who can access the service.