minor nits

Author: thomasgauvin

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

@@ -26,12 +26,12 @@ A VPC Service binding is accessed via the `env` parameter in your Worker's fetch
 Makes an HTTP request to the private service through the configured tunnel.
 
 ```js
-const response = await env.VPC_SERVICE_BINDING.fetch(url, options);
+const response = await env.VPC_SERVICE_BINDING.fetch(resource, options);
 ```
 
 ### Parameters
 
-- `url` (string | URL | Request) - The URL to fetch. This must be an absolute URL including protocol, host, and path (for example, `http://internal-api:8080/api/users`)
+- `resource` (string | URL | Request) - The URL to fetch. This must be an absolute URL including protocol, host, and path (for example, `http://internal-api:8080/api/users`)
 - `options` (optional RequestInit) - Standard fetch options including:
   - `method` - HTTP method (GET, POST, PUT, DELETE, etc.)
   - `headers` - Request headers
@@ -44,7 +44,7 @@ VPC Service fetch requests must use absolute URLs including the protocol (http/h
 
 ### Return value
 
-Returns a `Promise<Response>` that resolves to a standard Fetch API Response object.
+Returns a `Promise<Response>` that resolves to a [standard Fetch API Response object](https://developer.mozilla.org/en-US/docs/Web/API/Response).
 
 ### Examples
 

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

@@ -14,7 +14,7 @@ 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.
 - 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.
+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
 

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

@@ -28,9 +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/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.
 
 :::note[Important Note]
 Cloudflare Tunnels can either be configured for usage with [Cloudflare Zero Trust](/cloudflare-one/) or [Workers VPC](/workers-vpc/).

src/content/docs/workers-vpc/configuration/vpc-services.mdx

@@ -37,7 +37,7 @@ A VPC Service consists of:
 
 ## Configuration example
 
-The following is an example of a VPC Service for a service using custom HTTP and HTTPS ports, and both IPv4 and IPv6 addresses.
+The following is an example of a VPC Service for a service using custom HTTP and HTTPS ports, and both IPv4 and IPv6 addresses. These configurations represent the expected contract of the [REST API for creating a VPC Service](https://developers.cloudflare.com/api/resources/zero_trust/subresources/connectivity/subresources/directory/subresources/services/), a type of service within the broader connectivity directory.
 
 ```json
 {

src/content/docs/workers-vpc/examples/private-api.mdx

@@ -9,8 +9,8 @@ This example demonstrates how to access a private REST API that is not exposed t
 
 ## Prerequisites
 
-- A private API running in your VPC/VNet
-- Cloudflare Tunnel configured and running
+- A private API running in your VPC/virtual network
+- Cloudflare Tunnel configured and running (follow the [Get Started guide](/workers-vpc/get-started/) to set up)
 - Workers account with Workers VPC access
 
 ## 1. Create the VPC Service

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

@@ -62,7 +62,7 @@ cd workers-vpc-app
 
 ## 2. Set up Cloudflare Tunnel
 
-A Cloudflare Tunnel creates a secure connection from your private network to Cloudflare. This tunnel will allow Workers to securely access your private resources.
+A Cloudflare Tunnel creates a secure connection from your private network to Cloudflare. This tunnel will allow Workers to securely access your private resources. You can create the tunnel on a virtual machine or container in your external cloud, or even on your local desktop for the sake of this tutorial.
 
 <Steps>
 
@@ -159,7 +159,7 @@ main = "src/index.ts"
 compatibility_date = "2024-01-01"
 
 [[vpc_services]]
-binding = "PRIVATE_API"
+binding = "VPC_SERVICE"
 service_id = "<YOUR_SERVICE_ID>"
 
 ````

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 using [VPC Service bindings](/workers-vpc/api/) to connect from Workers.
+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.
 
 :::note
 
@@ -46,17 +46,16 @@ export default {
 			"http://internal-api.company.local/data",
 		);
 
-    	// Process the response from your private network
-    	const data = await response.json();
-
-    	return new Response(JSON.stringify(data), {
-    		headers: { "content-type": "application/json" },
-    	});
-    },
+		// Process the response from your private network
+		const data = await response.json();
 
+		return new Response(JSON.stringify(data), {
+			headers: { "content-type": "application/json" },
+		});
+	},
 };
 
-```
+````
 
     </TabItem>
     <TabItem label="wrangler.jsonc">
@@ -74,20 +73,20 @@ export default {
 			}
 		]
 	}
-```
+````
 
 </TabItem>
 </Tabs>
 
 ## Use cases
 
-### Applications on Workers with access to private APIs
+### Access private APIs from Workers applications
 
 Deploy APIs or full-stack applications to Workers that connect to private authentication services, CMS systems, internals APIs, and more. Your Workers applications run globally with optimized access to the backend services of your private network.
 
 ### API gateway
 
-Route requests to internal microservices in your private network based on URL paths. Centralize access control and load balancing for multiple private services.
+Route requests to internal microservices in your private network based on URL paths. Centralize access control and load balancing for multiple private services on Workers.
 
 ### Internal tooling, agents, dashboards