Making sure all imports are at the top of the page.

Author: Oxyjun

src/content/docs/ai-gateway/integrations/aig-workers-ai-binding.mdx

@@ -4,7 +4,7 @@ pcx_content_type: tutorial
 updated: 2024-10-17
 ---
 
-import { Render, PackageManagers } from "~/components";
+import { Render, PackageManagers, WranglerConfig } from "~/components";
 
 This guide will walk you through setting up and deploying a Workers AI project. You will use [Workers](/workers/), an AI Gateway binding, and a large language model (LLM), to deploy your first AI-powered application on the Cloudflare global network.
 
@@ -49,8 +49,6 @@ You must create an AI binding for your Worker to connect to Workers AI. Bindings
 
 To bind Workers AI to your Worker, add the following to the end of your `wrangler.json` file:
 
-import { WranglerConfig } from "~/components";
-
 <WranglerConfig>
 
 ```toml title="wrangler.toml"

src/content/docs/analytics/analytics-engine/get-started.mdx

@@ -9,14 +9,12 @@ head:
 
 ---
 
-import { DirectoryListing } from "~/components"
+import { DirectoryListing, WranglerConfig } from "~/components"
 
 ## 1. Name your dataset and add it to your Worker
 
 Add the following to your Wrangler configuration file to create a [binding](/workers/runtime-apis/bindings/) to a Workers Analytics Engine dataset. A dataset is like a table in SQL: the rows and columns should have consistent meaning.
 
-import { WranglerConfig } from "~/components";
-
 <WranglerConfig>
 
 ```toml

src/content/docs/analytics/analytics-engine/worker-querying.mdx

@@ -8,6 +8,9 @@ head:
     content: Querying Workers Analytics Engine from a Worker
 ---
 
+
+import { WranglerConfig } from "~/components";
+
 If you want to access Analytics Engine data from within a Worker you can use `fetch` to access the SQL API. The API can return JSON data that is easy to interact with in JavaScript.
 
 ## Authentication
@@ -48,8 +51,6 @@ First the environment variables are set up with the account ID and API token.
 
 The account ID is set in the Wrangler configuration file:
 
-import { WranglerConfig } from "~/components";
-
 <WranglerConfig>
 
 ```toml

src/content/docs/browser-rendering/get-started/browser-rendering-with-DO.mdx

@@ -14,7 +14,7 @@ sidebar:
   order: 2
 ---
 
-import { Render, PackageManagers } from "~/components";
+import { Render, PackageManagers, WranglerConfig } from "~/components";
 
 By following this guide, you will create a Worker that uses the Browser Rendering API along with [Durable Objects](/durable-objects/) to take screenshots from web pages and store them in [R2](/r2/).
 
@@ -75,8 +75,6 @@ Configure your `browser-worker` project's [Wrangler configuration file](/workers
 
 Update your Wrangler configuration file with the Browser Rendering API binding, the R2 bucket you created and a Durable Object:
 
-import { WranglerConfig } from "~/components";
-
 <WranglerConfig>
 
 ```toml

src/content/docs/browser-rendering/get-started/reuse-sessions.mdx

@@ -35,7 +35,7 @@ Create a new Worker project named `browser-worker` by running:
 
 ## 2. Install Puppeteer
 
-In your `browser-worker` directory, install Cloudflare’s [fork of Puppeteer](/browser-rendering/platform/puppeteer/):
+In your `browser-worker` directory, install Cloudflare's [fork of Puppeteer](/browser-rendering/platform/puppeteer/):
 
 ```sh
 npm install @cloudflare/puppeteer --save-dev

src/content/docs/browser-rendering/get-started/screenshots.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 1
 ---
 
-import { Render, TabItem, Tabs, PackageManagers } from "~/components";
+import { Render, TabItem, Tabs, PackageManagers, WranglerConfig } from "~/components";
 
 By following this guide, you will create a Worker that uses the Browser Rendering API to take screenshots from web pages. This is a common use case for browser automation.
 
@@ -62,11 +62,9 @@ Configure your `browser-worker` project's [Wrangler configuration file](/workers
 
 Update your Wrangler configuration file with the Browser Rendering API binding and the KV namespaces you created:
 
-import { WranglerConfig } from "~/components";
-
 <WranglerConfig>
 
-```toml
+```toml title="wrangler.toml"
 name = "browser-worker"
 main = "src/index.js"
 compatibility_date = "2023-03-14"

src/content/docs/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers.mdx

@@ -4,7 +4,9 @@ title: Outbound Workers
 
 ---
 
-Outbound Workers sit between your customer’s Workers and the public Internet. They give you visibility into all outgoing `fetch()` requests from user Workers.
+import { WranglerConfig } from "~/components";
+
+Outbound Workers sit between your customer's Workers and the public Internet. They give you visibility into all outgoing `fetch()` requests from user Workers.
 
 ![Outbound Workers diagram information](~/assets/images/cloudflare-for-platforms/outbound-worker-diagram.png)
 
@@ -25,8 +27,6 @@ To use Outbound Workers:
 
 Make sure that you have `[email protected]` or later [installed](/workers/wrangler/install-and-update/).
 
-import { WranglerConfig } from "~/components";
-
 <WranglerConfig>
 
 ```toml

src/content/docs/cloudflare-for-platforms/workers-for-platforms/get-started/configuration.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 1
 ---
 
-import { Render, PackageManagers } from "~/components";
+import { Render, PackageManagers, WranglerConfig } from "~/components";
 
 ## Prerequisites:
 
@@ -115,8 +115,6 @@ cd my-dispatcher
 
 Open the Wrangler file in your project directory, and add the dispatch namespace binding:
 
-import { WranglerConfig } from "~/components";
-
 <WranglerConfig>
 
 ```toml

src/content/docs/cloudflare-for-platforms/workers-for-platforms/get-started/developing-with-wrangler.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 3
 ---
 
-import { Render, PackageManagers } from "~/components";
+import { Render, PackageManagers, WranglerConfig } from "~/components";
 
 To test your [Dispatch Worker](/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#dynamic-dispatch-worker), [user Worker](/cloudflare-for-platforms/workers-for-platforms/reference/how-workers-for-platforms-works/#user-workers) and [Outbound Worker](/cloudflare-for-platforms/workers-for-platforms/configuration/outbound-workers/) before deploying to production, you can use [Wrangler](/workers/wrangler) for development and testing.
 
@@ -54,8 +54,6 @@ export default {
 
 Update the Wrangler file for customer-worker-1 and add the dispatch namespace:
 
-import { WranglerConfig } from "~/components";
-
 <WranglerConfig>
 
 ```toml

src/content/docs/d1/reference/migrations.mdx

@@ -6,6 +6,8 @@ sidebar:
 
 ---
 
+import { WranglerConfig } from "~/components";
+
 Database migrations are a way of versioning your database. Each migration is stored as an `.sql` file in your `migrations` folder. The `migrations` folder is created in your project directory when you create your first migration. This enables you to store and track changes throughout database development.
 
 ## Features
@@ -24,8 +26,6 @@ By default, migrations are created in the `migrations/` folder in your Worker pr
 
 This location and table name can be customized in your Wrangler file, inside the D1 binding.
 
-import { WranglerConfig } from "~/components";
-
 <WranglerConfig>
 
 ```toml