Various tweaks

Author: mikenomitch

src/content/docs/containers/get-started.mdx

@@ -32,7 +32,7 @@ the `docker info` command will hang or return an error including the message "Ca
 Run the following command to create and deploy a new Worker with a container, from the starter template:
 
 ```sh
-npm create cloudflare@latest -- --template=cloudflare/templates/hello-world-containers
+npm create cloudflare@latest -- --template=cloudflare/templates/containers-template
 ```
 
 When you want to deploy a code change to either the Worker or Container code, you can run the following command using [Wrangler CLI](/workers/wrangler/:
@@ -46,14 +46,14 @@ When you run `wrangler deploy`, the following things happen:
   integrated with your Cloudflare account.
 - Wrangler deploys your Worker, and configures Cloudflare's network to be ready to spawn instances of your container
 
-:::note
 The build and push usually take the longest on the first deploy. Subsequent deploys
 are faster, because they [reuse cached image layers](https://docs.docker.com/build/cache/).
-:::
 
+:::note
 After you deploy your Worker for the first time, you will need to wait several minutes until
 it is ready to receive requests. Unlike Workers, Containers take a few minutes to be provisioned.
 During this time, requests are sent to the Worker, but calls to the Container will error.
+:::
 
 ### Check deployment status
 
@@ -79,6 +79,7 @@ You can confirm this behavior by reading the output of each request.
 ## Understanding the Code
 
 Now that you've deployed your first container, let's explain what is happening in your Worker's code, in your configuration file, in your container's code, and how requests are routed.
+
 ## Each Container is backed by its own Durable Object
 
 Incoming requests are initially handled by the Worker, then passed to a container-enabled [Durable Object](/durable-objects).
@@ -204,9 +205,9 @@ When a request enters Cloudflare, your Worker's [`fetch` handler](/workers/runti
 
   ```js
   if (pathname.startsWith("/container")) {
-  	let id = env.MY_CONTAINER.idFromName("container");
-  	let container = env.MY_CONTAINER.get(id);
-  	return await container.fetch(request);
+  	const id = env.MY_CONTAINER.idFromName(pathname);
+		const container = env.MY_CONTAINER.get(id);
+		return await container.fetch(request);
   }
   ```
 
@@ -216,7 +217,7 @@ When a request enters Cloudflare, your Worker's [`fetch` handler](/workers/runti
 
   ```js
   if (pathname.startsWith("/lb")) {
-  	let container = await getRandom(env.MY_CONTAINER, 3);
+  	const container = await getRandom(env.MY_CONTAINER, 3);
   	return await container.fetch(request);
   }
   ```

src/content/docs/containers/image-management.mdx

@@ -40,7 +40,7 @@ calls after the initial deploy.
 Docker or a Docker-compatible CLI tool must be running for Wrangler to build and push images.
 :::
 
-## Using existing images
+## Using pre-built container images
 
 If you wish to use a pre-built image, first, push it to the Cloudflare Registry:
 

src/content/docs/containers/index.mdx

@@ -23,6 +23,7 @@ import {
 	Tabs,
 	Badge,
 	WranglerConfig,
+	LinkButton,
 } from "~/components";
 
 <Description>
@@ -40,7 +41,7 @@ Worker and `wrangler deploy`.
 
 With Containers you can run:
 
-- Resource-intensive applications that require multiple vCPUs, large amounts of memory or disk space
+- Resource-intensive applications that require CPU cores running in parallel, large amounts of memory or disk space
 - Applications and libraries that require a full filesystem, specific runtime, or Linux-like environment
 - Existing applications and tools that have been distributed as container images
 

src/content/docs/containers/local-dev.mdx

@@ -8,7 +8,7 @@ sidebar:
 You can run both your container and your Worker locally, without additional configuration, by running [`npx wrangler dev`](/workers/wrangler/commands/#dev) in your project's directory.
 
 To develop Container-enabled Workers locally, you will need to first ensure that a
-Docker compatible CLI tool is installed. For instance, you can use [Docker Desktop](https://docs.docker.com/desktop/)
+Docker compatible CLI tool and Engine are installed. For instance, you can use [Docker Desktop](https://docs.docker.com/desktop/)
 on Mac, Windows, or Linux.
 
 When you run `wrangler dev`, your container image will be built or downloaded. If your

src/content/docs/containers/pricing.mdx

@@ -9,28 +9,32 @@ sidebar:
 
 Containers are billed for every 10ms that they are actively running at the following rates, with included monthly usage as part of the $5 USD per month [Workers Paid plan](/workers/platform/pricing/):
 
-|             | Memory                                                                        | CPU                                                                   | Disk                                                              |
-|-------------|-------------------------------------------------------------------------------|-----------------------------------------------------------------------|-------------------------------------------------------------------|
-| **Free**    | N/A                                                                           | N/A                                                                   |                                                                   |
-| **Workers Paid**| 25 GiB-hours/month included <br/> +$0.0000025 per additional GiB-second   | 375 vCPU-minutes/month <br/>+ $0.000020 per additional vCPU-second    | 200 GB-hours/month <br/> +$0.00000007 per additional GB-second    |
+|                  | Memory                                                                  | CPU                                                                | Disk                                                           |
+| ---------------- | ----------------------------------------------------------------------- | ------------------------------------------------------------------ | -------------------------------------------------------------- |
+| **Free**         | N/A                                                                     | N/A                                                                |                                                                |
+| **Workers Paid** | 25 GiB-hours/month included <br/> +$0.0000025 per additional GiB-second | 375 vCPU-minutes/month <br/>+ $0.000020 per additional vCPU-second | 200 GB-hours/month <br/> +$0.00000007 per additional GB-second |
 
 You only pay for what you use — charges start when a request is sent to the container or when it is manually started. Charges stop after the container instance goes to sleep, which can happen automatically after a timeout. This makes it easy to scale to zero, and allows you to get high utilization even with bursty traffic.
 
 #### Instance Types
 
 When you add containers to your Worker, you specify an [instance type](/containers/platform-details/#instance-types). The instance type you select will impact your bill — larger instances include more vCPUs, memory and disk, and therefore incur additional usage costs. The following instance types are currently available, and larger instance types are coming soon:
 
-| Name     | Memory   | CPU        | Disk |
-|----------|----------|------------|------|
-| dev      | 256 MiB  | 1/16 vCPU  | 2 GB |
-| basic    | 1 GiB    | 1/4 vCPU   | 4 GB |
-| standard | 4 GiB    | 1/2 vCPU   | 4 GB |
+| Name     | Memory  | CPU       | Disk |
+| -------- | ------- | --------- | ---- |
+| dev      | 256 MiB | 1/16 vCPU | 2 GB |
+| basic    | 1 GiB   | 1/4 vCPU  | 4 GB |
+| standard | 4 GiB   | 1/2 vCPU  | 4 GB |
 
 ## Network Egress
 
 Egress from Containers is priced at the following rates:
 
-TODO
+| Region                 | Price per GB | Included Allotment per month |
+| ---------------------- | ------------ | ---------------------------- |
+| North America & Europe | $0.025       | 1 TB                         |
+| Oceania, Korea, Taiwan | $0.05        | 500 GB                       |
+| Everywhere Else        | $0.04        | 500 GB                       |
 
 ## Workers and Durable Objects Pricing