PCX Review

Author: Oxyjun

src/content/changelog/workers-vpc/2025-09-25-workers-vpc.mdx

@@ -14,4 +14,4 @@ We're excited to announce the beta release of **Workers VPC Services**, enabling
 
 ## Getting started
 
-Set up a Cloudflare Tunnel, create a VPC Service, add service bindings to your Worker, and access private resources securely. [Read the documentation](/workers-vpc/) to get started.
+Set up a Cloudflare Tunnel, create a VPC Service, add service bindings to your Worker, and access private resources securely. [Refer to the documentation](/workers-vpc/) to get started.

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

@@ -13,7 +13,7 @@ Each request made on the binding will route to the specific service that was con
 
 :::note
 
-Workers VPC is currently in beta. Features and APIs may change before general availability. During the beta, Workers VPC is available for free to all Workers plans.
+Workers VPC is currently in beta. Features and APIs may change before general availability. While in beta, Workers VPC is available for free to all Workers plans.
 
 :::
 
@@ -25,7 +25,7 @@ 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.
 
-```javascript
+```js
 const response = await env.VPC_SERVICE_BINDING.fetch(url, options);
 ```
 
@@ -50,7 +50,7 @@ Returns a `Promise<Response>` that resolves to a standard Fetch API Response obj
 
 #### Basic GET request
 
-```javascript
+```js
 export default {
 	async fetch(request, env) {
 		const privateRequest = new Request(
@@ -68,7 +68,7 @@ export default {
 
 #### POST request with body
 
-```javascript
+```js
 export default {
 	async fetch(request, env) {
 		const privateRequest = new Request(
@@ -102,7 +102,7 @@ export default {
 
 #### Request with HTTPS and IP address
 
-```javascript
+```js
 export default {
 	async fetch(request, env) {
 		const privateRequest = new Request("https://10.0.1.50:8443/api/data");
@@ -116,4 +116,4 @@ export default {
 ## Next steps
 
 - Configure [service bindings in wrangler.toml](/workers-vpc/configuration/vpc-services/)
-- View [usage examples](/workers-vpc/examples/)
+- Refer to [usage examples](/workers-vpc/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 and traffic balancing.
 - 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. 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
 

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

@@ -29,6 +29,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.
 
 :::note[Important Note]
@@ -42,7 +43,7 @@ Use Tunnels with Workers VPC when you want to access private APIs, private datab
 
 :::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 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 specific to Zero Trust, and are not required for Workers VPC, as routing is handled by the VPC Service configuration.
 
 :::
 

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

@@ -22,20 +22,20 @@ VPC Services enforce that requests are routed to their intended service without
 
 :::note
 
-Workers VPC is currently in beta. Features and APIs may change before general availability. During the beta, Workers VPC is available for free to all Workers plans.
+Workers VPC is currently in beta. Features and APIs may change before general availability. While in beta, Workers VPC is available for free to all Workers plans.
 
 :::
 
-## VPC Service Configuration
+## VPC Service configuration
 
 A VPC Service consists of:
 
 - **Type**: Currently only `http` is supported (support for `tcp` coming soon)
 - **Tunnel ID**: The Cloudflare Tunnel that provides network connectivity
-- **Hostname or IPv4/IPv6 addresses**: The hostname, or IPv4 and/or IPv6 addresses to use to route to your service from the tunnel in your private network.
+- **Hostname or IPv4/IPv6 addresses**: The hostname, or IPv4 and/or IPv6 addresses to use to route to your service from the tunnel in your private network
 - **Ports**: HTTP and/or HTTPS port configuration (optional, defaults to 80/443)
 
-## Configuration Example
+## 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.
 
@@ -83,7 +83,7 @@ The following is an example of a VPC Service for a service using custom HTTP and
 
 ## Workers binding configuration
 
-Once you've created a VPC Service, you can bind it to your Worker:
+Once you have created a VPC Service, you can bind it to your Worker:
 
 <WranglerConfig>
 ```toml
@@ -95,22 +95,7 @@ binding = "PRIVATE_API"
 service_id = "5634563546"
 remote = true
 
-````
-
-```jsonc
-{
-  "name": "my-worker",
-  "main": "src/index.js",
-  "services": [
-    {
-      "binding": "PRIVATE_API",
-      "service_id": "5634563546",
-      "remote": true
-    }
-  ]
-}
-````
-
+```
 </WranglerConfig>
 
 You can have multiple service bindings:
@@ -132,34 +117,12 @@ binding = "INTERNAL_CACHE"
 service_id = "3412345678"
 remote = true
 
-````
-
-```jsonc
-{
-  "services": [
-    {
-      "binding": "PRIVATE_API",
-      "service_id": "5634563546",
-      "remote": true
-    },
-    {
-      "binding": "PRIVATE_DATABASE",
-      "service_id": "7856789012",
-      "remote": true
-    },
-    {
-      "binding": "INTERNAL_CACHE",
-      "service_id": "3412345678",
-      "remote": true
-    }
-  ]
-}
-````
+```
 
 </WranglerConfig>
 
 ## Next steps
 
 - Set up [Cloudflare Tunnel](/workers-vpc/configuration/tunnel/) for your environment
 - Learn about the [Service Binding API](/workers-vpc/api/)
-- View [examples](/workers-vpc/examples/) of common use cases
+- Refer to [examples](/workers-vpc/examples/) of common use cases

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

@@ -3,11 +3,9 @@ title: Access private API
 pcx_content_type: example
 ---
 
-import { Tabs, TabItem } from "~/components";
+import { Tabs, TabItem, WranglerConfig } from "~/components";
 
-:::note
-This example demonstrates how to access a private REST API that's not exposed to the public internet.
-:::
+This example demonstrates how to access a private REST API that is not exposed to the public internet.
 
 ## Overview
 
@@ -42,6 +40,7 @@ Note the service ID returned for the next step.
 
 Update your `wrangler.toml`:
 
+<WranglerConfig>
 ```toml
 name = "private-api-gateway"
 main = "src/index.js"
@@ -54,12 +53,13 @@ service_id = "<YOUR_SERVICE_ID>"
 [vars]
 API_VERSION = "v2"
 ```
+</WranglerConfig>
 
 ## 3. Implement the Worker
 
 Create `src/index.js`:
 
-```javascript
+```js title="index.js"
 export default {
 	async fetch(request, env, ctx) {
 		// Parse the incoming request
@@ -125,7 +125,7 @@ export default {
 
 For more complex authentication, create a middleware pattern:
 
-```javascript
+```js
 // middleware/auth.js
 export async function authenticate(request, env) {
 	const authHeader = request.headers.get("Authorization");

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

@@ -3,11 +3,9 @@ title: Access private S3 bucket
 pcx_content_type: example
 ---
 
-import { Tabs, TabItem } from "~/components";
+import { Tabs, TabItem, WranglerConfig } from "~/components";
 
-:::note
 This example shows how to access an S3 bucket through a VPC endpoint without exposing it to the public internet.
-:::
 
 ## Overview
 
@@ -76,6 +74,7 @@ The VPC Service configuration handles the routing to S3 through your tunnel. The
 
 Update `wrangler.toml`:
 
+<WranglerConfig>
 ```toml
 name = "private-s3-worker"
 main = "src/index.js"
@@ -89,12 +88,13 @@ service_id = "<YOUR_SERVICE_ID>"
 AWS_REGION = "us-east-1"
 S3_BUCKET = "my-private-bucket"
 ```
+</WranglerConfig>
 
 ## 4. Implement S3 access with AWS Signature V4
 
 Create `src/index.js`:
 
-```javascript
+```js title="index.js"
 import { AwsClient } from "aws4fetch";
 
 export default {

src/content/docs/workers-vpc/examples/route-across-private-services.mdx

@@ -14,7 +14,7 @@ Use Workers VPC to create a centralized gateway that:
 
 ## Code example
 
-```javascript
+```js
 export interface Env {
   USER_SERVICE: PrivateNetworkService;
   ORDER_SERVICE: PrivateNetworkService;
@@ -24,7 +24,7 @@ export interface Env {
 export default {
   async fetch(request: Request, env: Env): Promise<Response> {
     const url = new URL(request.url);
-    
+
     // Add authentication
     const authHeader = request.headers.get('Authorization');
     if (!authHeader?.startsWith('Bearer ')) {
@@ -39,7 +39,7 @@ export default {
     } else if (url.pathname.startsWith('/api/inventory')) {
       return env.INVENTORY_SERVICE.fetch(request);
     }
-    
+
     return new Response('Not Found', { status: 404 });
   }
 };