fix final TOML syntax

Author: penalosa

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

@@ -163,16 +163,15 @@ To bind your KV namespace to your Worker:
 <Steps>
 1. In your `wrangler.toml` file, add the following with the values generated in your terminal from [step 2](/kv/get-started/#2-create-a-kv-namespace):
 
-<WranglerConfig>
+	<WranglerConfig>
 
-```toml
+	```toml
 	[[kv_namespaces]]
 	binding = "<BINDING_NAME>"
 	id = "<BINDING_ID>"
-
 	```
 
-</WranglerConfig>
+	</WranglerConfig>
 
    Binding names do not need to correspond to the namespace you created. Binding names are only a reference. Specifically:
 

src/content/docs/r2/examples/rclone.mdx

@@ -32,10 +32,6 @@ rclone config file
 
 Then use an editor (`nano` or `vim`, for example) to add or edit the new provider. This example assumes you are adding a new `r2demo` provider:
 
-import { WranglerConfig } from "~/components";
-
-<WranglerConfig>
-
 ```toml
 [r2demo]
 type = s3
@@ -46,8 +42,6 @@ endpoint = https://<accountid>.r2.cloudflarestorage.com
 acl = private
 ```
 
-</WranglerConfig>
-
 :::note
 
 If you are using a token with [Object-level permissions](/r2/api/s3/tokens/#permissions), you will need to add `no_check_bucket = true` to the configuration to avoid errors.

src/content/docs/workers/configuration/routing/routes.mdx

@@ -59,7 +59,7 @@ import { WranglerConfig } from "~/components";
 
 ```toml
 routes = [
-	{ pattern = "subdomain.example.com/*", zone_name = "example.com" }
+	{ pattern = "subdomain.example.com/*", zone_name = "example.com" },
 	# or
 	{ pattern = "subdomain.example.com/*", zone_id = "<YOUR_ZONE_ID>" }
 ]

src/content/docs/workers/observability/logs/workers-logs.mdx

@@ -43,20 +43,21 @@ You must add the observability setting for your Worker to write logs to Workers
 
 ### Enabling with environments
 
-[Environments](/workers/wrangler/environments/) allow you to deploy the same Worker application with different configurations. For example, you may want to configure a different `head_sampling_rate` to staging and production. To configure observability for your environment:
-	1. Add the following configuration below `[env.<NAME>]`
+[Environments](/workers/wrangler/environments/) allow you to deploy the same Worker application with different configurations. For example, you may want to configure a different `head_sampling_rate` to staging and production. To configure observability for an environment named `staging`:
+	1. Add the following configuration below `[env.staging]`
 
 
-<WranglerConfig>
+	<WranglerConfig>
 
-```toml
-	[env.<NAME>.observability]
+	```toml
+	[env.staging.observability]
 	enabled = true
 	head_sampling_rate = 1 # optional
 	```
 
-</WranglerConfig>
-	2. Deploy your Worker with `npx wrangler deploy -e <NAME>`
+	</WranglerConfig>
+
+	2. Deploy your Worker with `npx wrangler deploy -e staging`
 	3. Repeat step 1 and 2 for each environment.
 
 ## View logs from the dashboard

src/content/docs/workers/wrangler/migration/v1-to-v2/wrangler-legacy/configuration.mdx

@@ -76,25 +76,27 @@ account_id = "your-account-id"
 FOO = "default FOO value"
 BAR = "default BAR value"
 
-kv_namespaces = [
-  { binding = "FOO", id = "1a...", preview_id = "1b..." }
-]
+[[kv_namespaces]]
+binding = "FOO"
+id = "1a..."
+preview_id = "1b..."
 
 [env.helloworld]
 # Now adding configuration keys for the "helloworld" environment.
 # These new values will override the top-level configuration.
 name = "your-worker-helloworld"
 account_id = "your-other-account-id"
 
-[vars]
+[env.helloworld.vars]
 FOO = "env-helloworld FOO value"
 BAR = "env-helloworld BAR value"
 
-kv_namespaces = [
+[[env.helloworld.kv_namespaces]]
   # Redeclare kv namespace bindings for each environment
   # NOTE: In this case, passing new IDs because new `account_id` value.
-  { binding = "FOO", id = "888...", preview_id = "999..." }
-]
+binding = "FOO"
+id = "888..."
+preview_id = "999..."
 ```
 
 </WranglerConfig>

worker-configuration.d.ts

@@ -1,5 +1,4 @@
-// Generated by Wrangler on Tue Sep 17 2024 00:57:27 GMT-0400 (Eastern Daylight Time)
-// by running `wrangler types -c wrangler-workers.toml --experimental-include-runtime`
+// Generated by Wrangler by running `wrangler types -c wrangler-workers.toml --experimental-include-runtime`
 
 interface Env {
 	API_DOCS_KV: KVNamespace;
@@ -8,4 +7,4 @@ interface Env {
 declare module "*/_redirects" {
 	const value: string;
 	export default value;
-}
+}