fix urls due to changes in cloudflare-one docs structure

Author: thomasgauvin

src/content/docs/workers-vpc/configuration/tunnel/hardware-requirements.mdx

@@ -11,14 +11,14 @@ import { TunnelCalculator } from "~/components";
 
 For production use cases, we recommend the following baseline configuration:
 
-- Run a cloudflared replica on two dedicated host machines per network location. Using two hosts enables server-side redundancy. See [tunnel availability and replicas](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/) for setup instructions.
+- Run a cloudflared replica on two dedicated host machines per network location. Using two hosts enables server-side redundancy. See [tunnel availability and replicas](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/) for setup instructions.
 - Size each host with minimum 4GB of RAM and 4 CPU cores.
 
 This setup is usually sufficient to handle traffic from small-medium sized applications. The actual amount of resources used by cloudflared will depend on many variables, including the number of requests per second, bandwidth, network path, and hardware. If usage increases beyond your existing tunnel capacity, you can scale your tunnel by increasing the hardware allocated to the cloudflared hosts.
 
 ## Capacity calculator
 
-To estimate tunnel capacity requirements for your deployment, refer to the [tunnel capacity calculator in the Zero Trust documentation](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/system-requirements/).
+To estimate tunnel capacity requirements for your deployment, refer to the [tunnel capacity calculator in the Zero Trust documentation](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/system-requirements/).
 
 ## Scaling considerations
 

src/content/docs/workers-vpc/configuration/tunnel/index.mdx

@@ -14,7 +14,7 @@ When you create a VPC Service, you specify a tunnel ID and target service. Worke
 The tunnel maintains persistent connections to Cloudflare, eliminating the need for inbound firewall rules or public IP addresses.
 
 :::note
-This section provides tunnel configuration specific to Workers VPC use cases. For comprehensive tunnel documentation including monitoring and advanced configurations, refer to the [full Cloudflare Tunnel documentation](/cloudflare-one/connections/connect-networks/).
+This section provides tunnel configuration specific to Workers VPC use cases. For comprehensive tunnel documentation including monitoring and advanced configurations, refer to the [full Cloudflare Tunnel documentation](/cloudflare-one/networks/connectors/cloudflare-tunnel/).
 :::
 
 ## Create and run tunnel (`cloudflared`)
@@ -28,7 +28,7 @@ Cloudflare Tunnels can be created one of two ways:
 
 For Workers VPC, we recommend creating a remotely-managed tunnel through the dashboard. Follow the [Tunnels for Workers VPC dashboard setup guide](/workers-vpc/get-started/) to create your tunnel with provided installation commands shown in the dashboard.
 
-For locally-managed tunnels, refer to the [`cloudflared` locally-managed tunnels](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/) guide. For manual installation, refer to the [`cloudflared` downloads page](/cloudflare-one/connections/connect-networks/downloads/) for platform-specific installation instructions.
+For locally-managed tunnels, refer to the [`cloudflared` locally-managed tunnels](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/) guide. For manual installation, refer to the [`cloudflared` downloads page](/cloudflare-one/networks/connectors/cloudflare-tunnel/downloads/) for platform-specific installation instructions.
 
 :::note[Important Note]
 Cloudflare Tunnels can either be configured for usage with [Cloudflare Zero Trust](/cloudflare-one/) or [Workers VPC](/workers-vpc/).
@@ -43,21 +43,21 @@ The same `cloudflared` instance can be used to cover both Zero Trust and Workers
 
 :::note
 
-[Ingress configurations](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/configuration-file/) for locally-managed tunnels are only relevant when using tunnels to expose services to the public internet, and are not required for Workers VPC as routing is handled by the VPC Service configuration.
+[Ingress configurations](/cloudflare-one/networks/connectors/cloudflare-tunnel/do-more-with-tunnels/local-management/configuration-file/) for locally-managed tunnels are only relevant when using tunnels to expose services to the public internet, and are not required for Workers VPC as routing is handled by the VPC Service configuration.
 
 :::
 
 ## Cloud platform setup guides
 
 For platform-specific tunnel deployment instructions for production workloads:
 
-- [AWS](/cloudflare-one/connections/connect-networks/deployment-guides/aws/) - Deploy tunnels in Amazon Web Services
-- [Azure](/cloudflare-one/connections/connect-networks/deployment-guides/azure/) - Deploy tunnels in Microsoft Azure
-- [Google Cloud](/cloudflare-one/connections/connect-networks/deployment-guides/google-cloud-platform/) - Deploy tunnels in Google Cloud Platform
-- [Kubernetes](/cloudflare-one/connections/connect-networks/deployment-guides/kubernetes/) - Deploy tunnels in Kubernetes clusters
-- [Terraform](/cloudflare-one/connections/connect-networks/deployment-guides/terraform/) - Deploy tunnels using Infrastructure as Code
+- [AWS](/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/aws/) - Deploy tunnels in Amazon Web Services
+- [Azure](/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/azure/) - Deploy tunnels in Microsoft Azure
+- [Google Cloud](/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/google-cloud-platform/) - Deploy tunnels in Google Cloud Platform
+- [Kubernetes](/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/kubernetes/) - Deploy tunnels in Kubernetes clusters
+- [Terraform](/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/terraform/) - Deploy tunnels using Infrastructure as Code
 
-Refer to the full Cloudflare Tunnel documentation on [how to setup Tunnels for high availability and failover with replicas](/cloudflare-one/connections/connect-networks/configure-tunnels/tunnel-availability/).
+Refer to the full Cloudflare Tunnel documentation on [how to setup Tunnels for high availability and failover with replicas](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/tunnel-availability/).
 
 :::note
 We do not recommend using `cloudflared` in autoscaling setups because downscaling (removing replicas) will break existing user connections to that replica. Additionally, `cloudflared` does not load balance across replicas; replicas are strictly for high availability and requests are routed to the nearest replica.
@@ -67,4 +67,4 @@ We do not recommend using `cloudflared` in autoscaling setups because downscalin
 
 - Configure [VPC Services](/workers-vpc/configuration/vpc-services/) to connect your tunnels to Workers
 - Review [hardware requirements](/workers-vpc/configuration/tunnel/hardware-requirements/) for capacity planning
-- Review the [complete Cloudflare Tunnel documentation](/cloudflare-one/connections/connect-networks/) for advanced features
+- Review the [complete Cloudflare Tunnel documentation](/cloudflare-one/networks/connectors/cloudflare-tunnel/) for advanced features

src/content/docs/workers-vpc/get-started.mdx

@@ -87,7 +87,7 @@ Once your tunnel is connected, you will need to ensure it can access your the se
 :::note
 This guide provides a quick setup for Workers VPC.
 
-For comprehensive tunnel configuration, monitoring, and management, refer to the [full Cloudflare Tunnel documentation](/cloudflare-one/connections/connect-networks/).
+For comprehensive tunnel configuration, monitoring, and management, refer to the [full Cloudflare Tunnel documentation](/cloudflare-one/networks/connectors/cloudflare-tunnel/).
 :::
 
 ## 3. Create a VPC Service
@@ -221,5 +221,5 @@ Your Worker is now deployed and can access your private network resources secure
 
 - Explore [configuration options](/workers-vpc/configuration/) for advanced setups
 - Set up [high availability tunnels](/workers-vpc/configuration/tunnel/hardware-requirements/) for production
-- View [platform-specific guides](/cloudflare-one/connections/connect-networks/deployment-guides/) for AWS, Azure, GCP, and Kubernetes
+- View [platform-specific guides](/cloudflare-one/networks/connectors/cloudflare-tunnel/deployment-guides/) for AWS, Azure, GCP, and Kubernetes
 - Check out [examples](/workers-vpc/examples/) for common use cases

src/content/docs/workers-vpc/index.mdx

@@ -28,7 +28,7 @@ Securely connect your private cloud to Cloudflare to build cross-cloud apps.
 
 Workers VPC allows you to connect your Workers to your private APIs and services in external clouds (AWS, Azure, GCP, on-premise, etc.) that are not accessible from the public Internet.
 
-With Workers VPC, you can configure a [Cloudflare Tunnel](/cloudflare-one/connections/connect-networks/) to establish secure, private connections from your private networks to Cloudflare. Then, you can configure a [VPC Service](/workers-vpc/configuration/vpc-services/) for each service in the external private network you need to connect to, and use [VPC Service bindings](/workers-vpc/api/) to connect from Workers.
+With Workers VPC, you can configure a [Cloudflare Tunnel](/cloudflare-one/networks/connectors/cloudflare-tunnel/) to establish secure, private connections from your private networks to Cloudflare. Then, you can configure a [VPC Service](/workers-vpc/configuration/vpc-services/) for each service in the external private network you need to connect to, and use [VPC Service bindings](/workers-vpc/api/) to connect from Workers.
 
 :::note
 
@@ -46,13 +46,14 @@ export default {
 			"http://internal-api.company.local/data",
 		);
 
-		// Process the response from your private network
-		const data = await response.json();
+    	// Process the response from your private network
+    	const data = await response.json();
+
+    	return new Response(JSON.stringify(data), {
+    		headers: { "content-type": "application/json" },
+    	});
+    },
 
-		return new Response(JSON.stringify(data), {
-			headers: { "content-type": "application/json" },
-		});
-	},
 };
 
 ````