fix invalid links

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-networks/do-more-with-tunnels/migrate-legacy-tunnels.mdx

@@ -48,7 +48,7 @@ To migrate your legacy tunnels to the named tunnels architecture:
      cloudflared tunnel route dns <TUNNEL-NAME> tunnel.example.com
      ```
 
-   - If you used to run your legacy tunnel with the `--lb-pool` flag, run this command to set up your named tunnel as a load balancer origin. For more information, refer to the [Load Balancers routing](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb/) section.
+   - If you used to run your legacy tunnel with the `--lb-pool` flag, run this command to set up your named tunnel as a load balancer origin. For more information, refer to the [Load Balancers routing](/cloudflare-one/connections/connect-networks/routing-to-tunnel/public-load-balancers/) section.
 
      ```sh
      cloudflared tunnel route lb <TUNNEL-NAME> <LOAD-BALANCER-NAME> <LOAD-BALANCER-POOL>

src/content/docs/cloudflare-one/connections/connect-networks/downloads/update-cloudflared.mdx

@@ -141,7 +141,7 @@ You can update `cloudflared` without downtime by using Cloudflare's Load Balance
 
 1. Install a new instance of `cloudflared` and [create](/cloudflare-one/connections/connect-networks/get-started/) a new Tunnel.
 2. Configure the instance to point traffic to the same locally-available service as your current, active instance of `cloudflared`.
-3. [Add the address](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb/) of the new instance of `cloudflared` into your Load Balancer pool as priority 2.
+3. [Add the address](/cloudflare-one/connections/connect-networks/routing-to-tunnel/public-load-balancers/) of the new instance of `cloudflared` into your Load Balancer pool as priority 2.
 4. Swap the priority such that the new instance is now priority 1 and monitor to confirm traffic is being served.
 5. Once confirmed, you can remove the older version from the Load Balancer pool.
 

src/content/docs/cloudflare-one/connections/connect-networks/routing-to-tunnel/index.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 Cloudflare Tunnel allows you to publish local applications to the Internet via a public hostname. For example, you can [add a published application route](/cloudflare-one/connections/connect-networks/get-started/create-remote-tunnel/#2a-publish-an-application) that points `docs.example.com` to `https://localhost:8080`. Anyone can now view your application by going to `docs.example.com` in their web browser.
 
-Cloudflare can route traffic down your Cloudflare Tunnel using a [DNS record](/cloudflare-one/connections/connect-networks/routing-to-tunnel/dns/) or [Cloudflare Load Balancer](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb/). You can configure either option from the Cloudflare dashboard by pointing a DNS `CNAME` record or a load balancer pool to your Cloudflare Tunnel subdomain (`<UUID>.cfargotunnel.com`). You can also associate these records with your tunnel from `cloudflared` directly.
+Cloudflare can route traffic down your Cloudflare Tunnel using a [DNS record](/cloudflare-one/connections/connect-networks/routing-to-tunnel/dns/) or [Cloudflare Load Balancer](/cloudflare-one/connections/connect-networks/routing-to-tunnel/public-load-balancers/). You can configure either option from the Cloudflare dashboard by pointing a DNS `CNAME` record or a load balancer pool to your Cloudflare Tunnel subdomain (`<UUID>.cfargotunnel.com`). You can also associate these records with your tunnel from `cloudflared` directly.
 
 :::note
 

src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx

@@ -54,7 +54,7 @@ This means the origin is using a certificate that `cloudflared` does not trust.
 
 An error 1033 indicates your tunnel is not connected to Cloudflare's edge. First, run `cloudflared tunnel list` to see whether your tunnel is listed as active. If it isn't, check the following:
 
-1. Make sure you correctly routed traffic to your tunnel (step 5 in the [Tunnel guide](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/create-local-tunnel/#5-start-routing-traffic)) by assigning a CNAME record to point traffic to your tunnel. Alternatively, check [this guide](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb/) to route traffic to your tunnel using load balancers.
+1. Make sure you correctly routed traffic to your tunnel (step 5 in the [Tunnel guide](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/create-local-tunnel/#5-start-routing-traffic)) by assigning a CNAME record to point traffic to your tunnel. Alternatively, check [this guide](/cloudflare-one/connections/connect-networks/routing-to-tunnel/public-load-balancers/) to route traffic to your tunnel using load balancers.
 2. Make sure you run your tunnel (step 6 in the [Tunnel guide](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/create-local-tunnel/#6-run-the-tunnel)).
 
 For more information, here is a [comprehensive list](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/) of Cloudflare 1xxx errors.

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

@@ -41,4 +41,4 @@ If the tunnel is disconnected:
 For more control over how traffic routes through your tunnel, refer to the following links:
 
 * [DNS records](/cloudflare-one/connections/connect-networks/routing-to-tunnel/dns/)
-* [Load balancer](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb/)
+* [Load balancer](/cloudflare-one/connections/connect-networks/routing-to-tunnel/public-load-balancers/)

src/content/docs/load-balancing/additional-options/cloudflare-tunnel.mdx

@@ -11,4 +11,4 @@ head:
 
 Cloudflare Tunnel (formerly Argo Tunnel) establishes a secure outbound connection which runs in your infrastructure to connect the applications and machines to Cloudflare.
 
-For more details on how to use Load Balancing with Cloudflare Tunnel and public hostnames, refer to [Route tunnel traffic using a load balancer](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb/). For using private IPs instead, refer to [Set up private IPs with Tunnel](/load-balancing/private-network/tunnels-setup/).
+For more details on how to use Load Balancing with Cloudflare Tunnel and public hostnames, refer to [Route tunnel traffic using a load balancer](/cloudflare-one/connections/connect-networks/routing-to-tunnel/public-load-balancers/). For using private IPs instead, refer to [Set up private IPs with Tunnel](/load-balancing/private-network/warp-to-tunnel/).

src/content/docs/load-balancing/private-network/index.mdx

@@ -33,7 +33,7 @@ Currently, to be able to connect to private IP origins, Cloudflare load balancer
 
 Once the endpoint and virtual network (VNet) tunnel association is configured, Cloudflare can determine not only the tunnel health but also the health of the corresponding virtual or private IP targets.
 
-Refer to [Set up private IPs with Cloudflare Tunnel](/load-balancing/private-network/tunnels-setup/) for a detailed guide.
+Refer to [Set up Private Network Load Balancing with WARP-to-Tunnel](/load-balancing/private-network/warp-to-tunnel/) for a detailed guide.
 
 ### Magic WAN
 
@@ -58,5 +58,5 @@ When using [Spectrum](/spectrum/) as an on-ramp and [Magic WAN](/load-balancing/
 * **Intelligent traffic routing**: Benefit from failover for your private traffic and have the ability to monitor the health of these IP targets directly, rather than load balancing to a tunnel and only monitoring the health of the tunnel itself.
 
 * **Host applications on non-standard ports**: Easily specify and route traffic to applications hosted on private IP addresses using non-standard ports, allowing greater flexibility in service configuration without requiring changes to existing infrastructure.
- 
+
 * **Public and Private Load Balancers**: Public LBs can direct Internet traffic to private IP addresses, supporting all L7 products like WAF and API Shield. Private LBs direct traffic originating from private networks to private IP addresses and require an on-ramp like WARP or Magic WAN.

src/content/docs/load-balancing/private-network/warp-to-tunnel.mdx

@@ -50,7 +50,7 @@ The components in the diagram include:
 
 ## 1. Create a Cloudflare Tunnel
 
-Skip to [step 2](/load-balancing/private-network/warp/#2-create-load-balancer-pools) if you have already connected your private networks with Cloudflare Tunnel.
+Skip to [step 2](#2-create-load-balancer-pools) if you have already connected your private networks with Cloudflare Tunnel.
 
 To create a new tunnel:
 

src/content/docs/reference-architecture/architectures/sase.mdx

@@ -153,7 +153,7 @@ Connectivity to self-hosted applications is facilitated through tunnels that are
 
 `cloudflared` manages multiple outbound connections back to Cloudflare and usually requires no changes to network firewalls. Those connections are spread across servers in more than one Cloudflare data center for reliability and failover. Traffic destined for a tunnel is forwarded to the connection that is geographically closest to the request, and if a `cloudflared` connection isn't responding, the tunnel will automatically failover to the next available.
 
-For more control over the traffic routed through each tunnel connection, users can integrate with the Cloudflare [load balancing](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb/) service. To ensure reliable local connectivity, organizations should deploy more than one instance of `cloudflared` across their application infrastructure. For example, with ten front-end web servers running in a Kubernetes cluster, you might deploy three kubernetes services [running `cloudflared` replicas](/cloudflare-one/connections/connect-networks/deployment-guides/kubernetes/).
+For more control over the traffic routed through each tunnel connection, users can integrate with the Cloudflare [load balancing](/cloudflare-one/connections/connect-networks/routing-to-tunnel/public-load-balancers/) service. To ensure reliable local connectivity, organizations should deploy more than one instance of `cloudflared` across their application infrastructure. For example, with ten front-end web servers running in a Kubernetes cluster, you might deploy three kubernetes services [running `cloudflared` replicas](/cloudflare-one/connections/connect-networks/deployment-guides/kubernetes/).
 
 ![Using cloudflared, multiple outbound connections are created back to Cloudflare across multiple data centers to improve overall performance and reliability.](~/assets/images/reference-architecture/cloudflare-one-reference-architecture-images/cf1-ref-arch-7.svg)
 

src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1033.mdx

@@ -15,4 +15,4 @@ You have requested a page on a website (`tunnel.example.com`) that is on the Clo
 ### Resolution
 
 - **If you are a visitor to this website**: Please try again in a few minutes.
-- **If you are the owner of this website**: Ensure that _cloudflared_ is running and can reach the network. You may wish to enable [load balancing](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb) for your tunnel.
+- **If you are the owner of this website**: Ensure that _cloudflared_ is running and can reach the network. You may wish to enable [load balancing](/cloudflare-one/connections/connect-networks/routing-to-tunnel/public-load-balancers/) for your tunnel.