Apply suggestions from code review

Various small fixes

Co-authored-by: Nikita Sharma <[email protected]>

Author: mikenomitch

src/content/docs/containers/architecture.mdx

@@ -47,7 +47,7 @@ extends Durable Objects with Container-specific APIs and helpers. We recommend u
 the [`Container` class documentation](/containers/container-package) for more details.
 
 Each Durable Object is a globally routable isolate that can execute code and store state. This allows
-developers to easily address and route to specific container instances (no matter where they are placed)
+developers to easily address and route to specific container instances (no matter where they are placed),
 define and run hooks on container status changes, execute recurring checks on the instance, and store persistent
 state associated with each instance.
 

src/content/docs/containers/beta-info.mdx

@@ -38,7 +38,7 @@ We plan to automatically reduce log noise in the future.
 
 The dashboard will be updated to show:
 
-- the status of Container rollouts.
+- the status of Container rollouts
 - links from Workers to their associated Containers
 
 ### Co-locating Durable Objects and Containers

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

@@ -13,7 +13,7 @@ import { WranglerConfig, Details } from "~/components";
 A common pattern is to serve a static frontend application (e.g., React, Vue, Svelte) using Static Assets,
 then pass backend requests to a containerized backend application.
 
-In this example, we'll show an example using a simple index.html file served as a static asset,
+In this example, we'll show an example using a simple `index.html` file served as a static asset,
 but you can select from one of many frontend frameworks. See our [Workers framework examples](/workers/framework-guides/web-apps/) for more information.
 
 For a full example, see the [Static Frontend + Container Backend Template](https://github.com/mikenomitch/static-frontend-container-backend).
@@ -123,7 +123,7 @@ Create a simple `index.html` file in the `./dist` directory.
 ```
 </Details>
 
-In this example, we are using [Alpine.js](https://alpinejs.dev/) to fetch a list of widgets from "/api/widgets".
+In this example, we are using [Alpine.js](https://alpinejs.dev/) to fetch a list of widgets from `/api/widgets`.
 
 This is meant to be a very simple example, but you can get significantly more complex.
 See [examples of Workers integrating with frontend frameworks](/workers/framework-guides/web-apps/) for more information.
@@ -186,11 +186,11 @@ 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", "*")
@@ -199,8 +199,8 @@ widgets := []map[string]interface{}{
 }
 
 func main() {
-http.HandleFunc("/api/widgets", handler)
-log.Fatal(http.ListenAndServe(":8080", nil))
+    http.HandleFunc("/api/widgets", handler)
+    log.Fatal(http.ListenAndServe(":8080", nil))
 }
 
 ```

src/content/docs/containers/examples/env-vars-and-secrets.mdx

@@ -115,8 +115,8 @@ We'll assume that we've set additional secrets in the Secret Store.
 
 ```js
 export class MyContainer extends Container {
-  defaultPort = 8080;
-  sleepAfter = '10s';
+	defaultPort = 8080;
+	sleepAfter = '10s';
 	manualStart = true;
 }
 

src/content/docs/containers/faq.mdx

@@ -86,7 +86,7 @@ See [scaling & routing documentation](/containers/scaling-and-routing/) for deta
 
 A cold start is when a container instance is started from a completely stopped state.
 
-If you call `env.MY_CONTAINER.get(id)` with a completely novel ID, and launch
+If you call `env.MY_CONTAINER.get(id)` with a completely novel ID and launch
 this instance for the first time, it will result in a cold start.
 
 This will start the container image from its entrypoint for the first time. Depending

src/content/docs/containers/index.mdx

@@ -55,14 +55,14 @@ export class MyContainer extends Container {
 }
 
 async fetch(request, env) {
-  const { "session-id": sessionId } = await request.json();
-  // Get the container instance for the given session ID
-  const containerInstance = getContainer(env.MY_CONTAINER, sessionId)
-  // Pass the request to the container instance on its default port
-  return containerInstance.fetch(request);
+	const { "session-id": sessionId } = await request.json();
+	// Get the container instance for the given session ID
+	const containerInstance = getContainer(env.MY_CONTAINER, sessionId)
+	// Pass the request to the container instance on its default port
+	return containerInstance.fetch(request);
 }
 
-````
+```
 </TabItem>
 <TabItem label="Worker Config">
 <WranglerConfig>
@@ -96,7 +96,7 @@ async fetch(request, env) {
 		}
 	],
 }
-````
+```
 
 </WranglerConfig>
 </TabItem>

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

@@ -13,16 +13,16 @@ This page containers general details about the Containers platform.
 
 ## Instance Types
 
-Currently, Containers are configured with custom memory, vCPU, and disk space.
-On launch, there will be three instance types available for Containers users by default:
+The memory, vCPU, and disk space for Containers are set through predefined instance types.
+There are currently three instance types available for Containers users by default:
 
-| Instance Type | Memory | vCPU | Disk |
-| ------------- | ------ | ---- | ---- |
-| dev           | 256 MB | 1/16 | 2 GB |
-| basic         | 1 GB   | 1/4  | 4 GB |
-| standard      | 4 GB   | 1/2  | 4 GB |
+| Instance Type | Memory  | vCPU | Disk |
+| ------------- | ------- | ---- | ---- |
+| dev           | 256 MiB | 1/16 | 2 GB |
+| basic         | 1 GiB   | 1/4  | 4 GB |
+| standard      | 4 GiB   | 1/2  | 4 GB |
 
-These will be specified using the `instance_type` property in wrangler config.
+These are specified using the `instance_type` property in wrangler config.
 
 ## Limits
 

src/content/docs/containers/scaling-and-routing.mdx

@@ -41,11 +41,11 @@ class Backend extends Container {
 }
 
 export default {
-  async fetch(request: Request, env: Env): Promise<Response> {
+	async fetch(request: Request, env: Env): Promise<Response> {
 		// note: "getRandom" to be replaced with latency-aware routing in the near future
 		const containerInstance = getRandom(env.BACKEND, INSTANCE_COUNT)
 		return containerInstance.fetch(request);
-  },
+	},
 };
 ```
 

src/content/docs/workers/wrangler/configuration.mdx

@@ -1090,7 +1090,7 @@ The following options are available:
 
   - The instance type of the container. This determines the amount of memory, CPU, and disk given to the container
     instance. The current options are `"dev"`, `"basic"`, and `"standard"`. The default is `"dev"`. For more information,
-    the see [instance types documentation](/containers/platform-details).
+    the see [instance types documentation](/containers/platform-details#instance-types).
 
 - `max_instances` <Type text="string" /> <MetaInfo text="optional" />