Update src/content/changelog/cloudflare-tunnel/2025-09-18-tunnel-hostname-routing.mdx

Author: ranbel

src/content/changelog/cloudflare-tunnel/2025-09-18-tunnel-hostname-routing.mdx

@@ -18,6 +18,6 @@ Previously, Tunnel routes could only be defined by IP address or [CIDR range](/c
 - **Precise Egress Control**: Route traffic for public hostnames (e.g., `bank.example.com`) through a specific Tunnel to enforce a dedicated source IP, solving the IP allowlist problem for third-party services.
 - **No More IP Lists**: This feature makes the workaround of maintaining dynamic IP Lists for Tunnel connections obsolete.
 
-Get started in the Tunnels section of the Zero Trust dashboard with your first [hostname route](/cloudflare-one/connections/connect-networks/private-net/cloudflared/connect-private-hostname/) and connect your [private networks](/cloudflare-one/connections/connect-networks/private-net/cloudflared/) with [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/).
+Get started in the Tunnels section of the Zero Trust dashboard with your first [private hostname](/cloudflare-one/connections/connect-networks/private-net/cloudflared/connect-private-hostname/) or [public hostname](/cloudflare-one/policies/gateway/egress-policies/egress-cloudflared/) route.
 
 Learn more in our [blog post](https://blog.cloudflare.com/tunnel-hostname-routing/).