pr feedback and fixups

Author: emily-shen

src/content/docs/containers/examples/container-backend.mdx

@@ -32,6 +32,7 @@ For a full example, see the [Static Frontend + Container Backend Template](https
     {
       "class_name": "Backend",
       "image": "./Dockerfile",
+			"max_instances": 3
     }
   ],
   "durable_objects": {
@@ -175,6 +176,7 @@ Your container should be able to handle requests to `/api/widgets`.
 In this case, we'll use a simple Golang backend that returns a hard-coded list of widgets.
 
 <Details header="server.go">
+
 ```go
 package main
 
@@ -185,23 +187,23 @@ import (
 )
 
 func handler(w http.ResponseWriter, r \*http.Request) {
-widgets := []map[string]interface{}{
-{"id": 1, "name": "Widget A"},
-{"id": 2, "name": "Sprocket B"},
-{"id": 3, "name": "Gear C"},
-}
+	widgets := []map[string]interface{}{
+		{"id": 1, "name": "Widget A"},
+		{"id": 2, "name": "Sprocket B"},
+		{"id": 3, "name": "Gear C"},
+	}
 
-    w.Header().Set("Content-Type", "application/json")
-    w.Header().Set("Access-Control-Allow-Origin", "*")
-    json.NewEncoder(w).Encode(widgets)
+	w.Header().Set("Content-Type", "application/json")
+	w.Header().Set("Access-Control-Allow-Origin", "*")
+	json.NewEncoder(w).Encode(widgets)
 
 }
 
 func main() {
-http.HandleFunc("/api/widgets", handler)
-log.Fatal(http.ListenAndServe(":8080", nil))
+	http.HandleFunc("/api/widgets", handler)
+	log.Fatal(http.ListenAndServe(":8080", nil))
 }
 
 ```
+
 </Details>
-```

src/content/docs/containers/examples/status-hooks.mdx

@@ -1,5 +1,4 @@
 ---
-
 summary: Execute Workers code in reaction to Container status changes
 pcx_content_type: example
 title: Status Hooks
@@ -9,7 +8,7 @@ description: Execute Workers code in reaction to Container status changes
 ---
 
 When a Container starts, stops, and errors, it can trigger code execution in a Worker
-that has defined status hooks on the `Container` class.
+that has defined status hooks on the `Container` class. Refer to the [Container package docs](https://github.com/cloudflare/containers/blob/main/README.md#lifecycle-hooks) for more details.
 
 ```js
 import { Container } from '@cloudflare/containers';

src/content/docs/containers/examples/websocket.mdx

@@ -1,5 +1,4 @@
 ---
-
 summary: Forwarding a Websocket request to a Container
 pcx_content_type: example
 title: Websocket to Container
@@ -8,11 +7,11 @@ sidebar:
 description: Forwarding a Websocket request to a Container
 ---
 
-WebSocket requests are automatically forwarded to a container using the default`fetch`
+WebSocket requests are automatically forwarded to a container using the default `fetch`
 method on the `Container` class:
 
 ```js
-import { Container, getContainer } from "@cloudflare/workers-types";
+import { Container, getContainer } from "@cloudflare/containers";
 
 export class MyContainer extends Container {
 	defaultPort = 8080;
@@ -27,6 +26,5 @@ export default {
 };
 ```
 
-Additionally, the `containerFetch` method can be used to forward WebSocket requests as well.
-
+View a full example in the [Container class repository](https://github.com/cloudflare/containers/tree/main/examples/websocket).
 {/* TODO: Add more advanced examples - like kicking off a WS request then passing messages to container from the WS */}

src/content/docs/containers/platform-details/architecture.mdx

@@ -25,7 +25,7 @@ by a datacenter in a location with the best latency between itself and the reque
 A different datacenter may be selected to optimize overall latency, if [Smart Placement](/workers/configuration/smart-placement/)
 is on, or if the nearest location is under heavy load.
 
-Because all Container requests are passed through a Worker, end-users cannot make TCP or
+Because all Container requests are passed through a Worker, end-users cannot make non-HTTP TCP or
 UDP requests to a Container instance. If you have a use case that requires inbound TCP
 or UDP from an end-user, please [let us know](https://forms.gle/AGSq54VvUje6kmKu8).
 
@@ -81,25 +81,29 @@ This location will again be the nearest location to the originating request with
 Each container instance runs inside its own VM, which provides strong
 isolation from other workloads running on Cloudflare's network. Containers
 should be built for the `linux/amd64` architecture, and should stay within
-[size limits](/containers/platform-details/limits). [Logging](/containers/faq/#how-do-container-logs-work), metrics collection, and
-networking are automatically set up on each container, if configured by the developer.
+[size limits](/containers/platform-details/limits).
 
-### After a request
+[Logging](/containers/faq/#how-do-container-logs-work), metrics collection, and
+[networking](/containers/faq/#how-do-i-allow-or-disallow-egress-from-my-container) are automatically set up on each container, as configured by the developer.
+
+### Container shutdown
 
 Cloudflare will not actively shut off a container instance after a specific amount of
-time. If you do not set `sleepAfter` on your Container class, or stop the instance
+time. If you do not set [`sleepAfter`](https://github.com/cloudflare/containers/blob/main/README.md#properties) on your Container class, or stop the instance
 manually, it will continue to run unless its host server is restarted. This
 happens on an irregular cadence, but frequently enough where Cloudflare does not
 guarantee that any instance will run for any set period of time.
 
+You can manually shutdown a container instance by calling `stop()` or `destroy()` on it - refer to the [Container package docs](https://github.com/cloudflare/containers/blob/main/README.md#container-methods) for more details.
+
 When a container instance is going to be shut down, it is sent a `SIGTERM` signal,
 and then a `SIGKILL` signal after 15 minutes. You should perform any necessary
-cleanup to ensure a graceful shutdown in this time. The container instance
-will be rebooted elsewhere shortly after this.
+cleanup to ensure a graceful shutdown in this time.
+
+#### Persistent disk
 
 All disk is ephemeral. When a Container instance goes to sleep, the next time
 it is started, it will have a fresh disk as defined by its container image.
-
 Persistent disk is something the Cloudflare team is exploring in the future, but
 is not slated for the near term.
 

src/content/docs/containers/platform-details/environment-variables.mdx

@@ -13,11 +13,9 @@ The container runtime automatically sets the following variables:
 
 - `CLOUDFLARE_APPLICATION_ID` - the ID of the Containers application
 - `CLOUDFLARE_COUNTRY_A2` - the [ISO 3166-1 Alpha 2 code](https://www.iso.org/obp/ui/#search/code/) of a country the container is placed in
-- `CLOUDFLARE_DEPLOYMENT_ID` - the ID of the container instance
 - `CLOUDFLARE_LOCATION` - a name of a location the container is placed in
-- `CLOUDFLARE_PLACEMENT_ID` - a placement ID
 - `CLOUDFLARE_REGION` - a region name
-- `CLOUDFLARE_DURABLE_OBJECT_ID` - the ID of the Durable Object that the container is bound to
+- `CLOUDFLARE_DURABLE_OBJECT_ID` - the ID of the Durable Object instance that the container is bound to
 
 ## User-defined environment variables
 

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

@@ -80,7 +80,7 @@ This will output an image registry URI that you can then use in your Wrangler co
 ```json
 {
 	"containers": {
-		"image": "registry.cloudflare.com/your-image:tag"
+		"image": "registry.cloudflare.com/your-account-id/your-image:tag"
 		// ...rest of config...
 	}
 }