address pr comments

Author: thomasgauvin

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

@@ -11,16 +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 and traffic balancing.
+- 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.
 - 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. As additional users are onboarded, or if network traffic increases beyond your existing tunnel capacity, you can scale your tunnel by adding an additional cloudflared host in that location.
 
 ## Capacity calculator
 
-Use the calculator below to estimate tunnel capacity requirements for your deployment:
-
-<TunnelCalculator />
+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-capacity/).
 
 ## Scaling considerations
 
@@ -29,7 +27,7 @@ Monitor tunnel performance and scale accordingly:
 - **CPU utilization**: Keep below 70% average usage
 - **Memory usage**: Maintain headroom for traffic spikes
 - **Network bandwidth**: Ensure adequate throughput for peak loads
-- **Connection count**: Add replicas when approaching capacity limits
+- **Connection count**: Scale cloudflared vertically when approaching capacity limits
 
 ## Next steps
 

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

@@ -39,11 +39,13 @@ Use Tunnels with Zero Trust when you are exposing internal applications securely
 
 Use Tunnels with Workers VPC when you want to access private APIs, private databases, internal services or other HTTP services within your cloud or on-premise private network from Workers.
 
+The same `cloudflared` instance can be used to cover both Zero Trust and Workers VPC use cases simultaneously.
+
 :::
 
 :::note
 
-[Ingress configurations](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/configuration-file/) for locally-managed tunnels are specific to Zero Trust, and are not required for Workers VPC, as routing is handled by the VPC Service configuration.
+[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.
 
 :::
 

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

@@ -42,9 +42,17 @@ Additionally, you will need:
 
 Create a new Worker project using Wrangler:
 
-<PackageManagers type="create" pkg="cloudflare@latest" args={"workers-vpc-app"} />
-
-<Render file="c3-post-run-steps" product="workers" params={{category: "hello-world", type: "Worker only", lang: "TypeScript",}} />
+<PackageManagers
+	type="create"
+	pkg="cloudflare@latest"
+	args={"workers-vpc-app"}
+/>
+
+<Render
+	file="c3-post-run-steps"
+	product="workers"
+	params={{ category: "hello-world", type: "Worker only", lang: "TypeScript" }}
+/>
 
 Navigate to your project directory:
 
@@ -154,7 +162,7 @@ compatibility_date = "2024-01-01"
 binding = "PRIVATE_API"
 service_id = "<YOUR_SERVICE_ID>"
 
-```
+````
 
 </WranglerConfig>
 
@@ -187,7 +195,7 @@ export default {
 	},
 } satisfies ExportedHandler<Env>;
 
-```
+````
 
 ## 6. Test locally
 
@@ -212,7 +220,6 @@ Your Worker is now deployed and can access your private network resources secure
 ## Next steps
 
 - Explore [configuration options](/workers-vpc/configuration/) for advanced setups
-- Set up [high availability tunnels](/workers-vpc/configuration/tunnel/availability/) for production
-- Refer to [platform-specific guides](/workers-vpc/configuration/tunnel/recommended-setups/) for AWS, Azure, GCP, and Kubernetes
-- Refer to [examples](/workers-vpc/examples/) for common use cases
-
+- 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
+- Check out [examples](/workers-vpc/examples/) for common use cases