fix indent

Author: penalosa

src/content/docs/cloudflare-one/tutorials/entra-id-risky-users.mdx

@@ -6,6 +6,9 @@ pcx_content_type: tutorial
 title: Isolate risky Entra ID users
 ---
 
+import { WranglerConfig } from "~/components";
+
+
 Microsoft Entra ID (formerly Azure Active Directory) calculates a user's [risk level](https://learn.microsoft.com/entra/id-protection/howto-identity-protection-investigate-risk) based on the probability that their account has been compromised. With Cloudflare Zero Trust, you can synchronize the Entra ID risky users list with Cloudflare Access and apply more stringent Zero Trust policies to users at higher risk.
 
 This tutorial demonstrates how to automatically redirect users to a remote browser when they are deemed risky by Entra ID.
@@ -83,7 +86,6 @@ To get started quickly, deploy our example Cloudflare Workers script by followin
    - `<TENANT_ID>`: your Entra ID **Directory (tenant) ID**, obtained when [setting up Entra ID as an identity provider](#1-set-up-entra-id-as-an-identity-provider).
    - `<CLIENT_ID>`: your Entra ID **Application (client) ID**, obtained when [setting up Entra ID as an identity provider](#1-set-up-entra-id-as-an-identity-provider).
 
-   import { WranglerConfig } from "~/components";
 
    <WranglerConfig>
 

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

@@ -7,13 +7,14 @@ sidebar:
 ---
 
 import {
-    Render,
-    PackageManagers,
-    Steps,
-    FileTree,
-    Tabs,
-    TabItem,
-    TypeScriptExample
+	Render,
+	PackageManagers,
+	Steps,
+	FileTree,
+	Tabs,
+	TabItem,
+	TypeScriptExample,
+	WranglerConfig
 } from "~/components";
 
 This guide instructs you through:
@@ -176,8 +177,6 @@ You create bindings by updating your `wrangler.toml` file.
 1. Copy the lines obtained from [step 2](/d1/get-started/#2-create-a-database) from your terminal.
 2. Add them to the end of your `wrangler.toml` file.
 
-   import { WranglerConfig } from "~/components";
-
    <WranglerConfig>
 
    ```toml

src/content/docs/d1/tutorials/build-an-api-to-access-d1/index.mdx

@@ -13,7 +13,7 @@ languages:
   - SQL
 ---
 
-import { Render, PackageManagers, Steps, Details } from "~/components";
+import { Render, PackageManagers, Steps, Details, WranglerConfig } from "~/components";
 
 In this tutorial, you will learn how to create an API that allows you to securely run queries against a D1 database.
 
@@ -223,8 +223,6 @@ Make a note of the displayed `database_name` and `database_id`. You will use thi
 1. From your `d1-http` folder, open the `wrangler.toml` file, Wrangler's configuration file.
 2. Add the following binding in the file. Make sure that the `database_name` and the `database_id` are correct.
 
-    import { WranglerConfig } from "~/components";
-
     <WranglerConfig>
 
     ```toml

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

@@ -5,7 +5,7 @@ sidebar:
   order: 2
 ---
 
-import { Render, PackageManagers, Steps, FileTree, Details, Tabs, TabItem } from "~/components";
+import { Render, PackageManagers, Steps, FileTree, Details, Tabs, TabItem, WranglerConfig } from "~/components";
 
 Workers KV provides low-latency, high-throughput global storage to your [Cloudflare Workers](/workers/) applications. Workers KV is ideal for storing user configuration data, routing data, A/B testing configurations and authentication tokens, and is well suited for read-heavy workloads.
 
@@ -163,8 +163,6 @@ 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):
 
-	import { WranglerConfig } from "~/components";
-
 <WranglerConfig>
 
 ```toml

src/content/docs/workers/configuration/sites/start-from-existing.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 1
 ---
 
-import { Render, TabItem, Tabs } from "~/components";
+import { Render, TabItem, Tabs, WranglerConfig } from "~/components";
 
 <Render file="workers_sites" />
 
@@ -36,8 +36,6 @@ To deploy a pre-existing static site project, start with a pre-generated site. W
 
 2. Add your site’s build/output directory to the `wrangler.toml` file:
 
-   import { WranglerConfig } from "~/components";
-
    <WranglerConfig>
 
    ```toml

src/content/docs/workers/configuration/sites/start-from-scratch.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 2
 ---
 
-import { Render } from "~/components";
+import { Render, WranglerConfig } from "~/components";
 
 <Render file="workers_sites" />
 
@@ -50,8 +50,6 @@ The template project contains the following files and directories:
 
 - Change the `name` property to the name of your project:
 
-  import { WranglerConfig } from "~/components";
-
   <WranglerConfig>
 
   ```toml

src/content/docs/workers/configuration/sites/start-from-worker.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 3
 ---
 
-import { Render, TabItem, Tabs } from "~/components";
+import { Render, TabItem, Tabs, WranglerConfig } from "~/components";
 
 <Render file="workers_sites" />
 
@@ -19,8 +19,6 @@ If you have a pre-existing Worker project, you can use Workers Sites to serve st
 
 2. Add configuration to your `wrangler.toml` file to point to it.
 
-   import { WranglerConfig } from "~/components";
-
    <WranglerConfig>
 
    ```toml

src/content/docs/workers/configuration/smart-placement.mdx

@@ -9,6 +9,8 @@ sidebar:
     text: Beta
 ---
 
+import { WranglerConfig } from "~/components";
+
 By default, [Workers](/workers/) and [Pages Functions](/pages/functions/) are invoked in a data center closest to where the request was received. If you are running back-end logic in a Worker, it may be more performant to run that Worker closer to your back-end infrastructure rather than the end user. Smart Placement automatically places your workloads in an optimal location that minimizes latency and speeds up your applications.
 
 ## Background
@@ -43,8 +45,6 @@ To enable Smart Placement via Wrangler:
 
 2. Add the following to your Worker project's `wrangler.toml` file:
 
-   import { WranglerConfig } from "~/components";
-
    <WranglerConfig>
 
    ```toml

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

@@ -11,7 +11,7 @@ sidebar:
 
 ---
 
-import { TabItem, Tabs, Steps, Render } from "~/components"
+import { TabItem, Tabs, Steps, Render, WranglerConfig } from "~/components"
 
 Workers Logs lets you automatically collect, store, filter, and analyze logging data emitted from Cloudflare Workers. Data is written to your Cloudflare Account, and you can query it in the dashboard for each of your Workers. All newly created Workers will come with the observability setting enabled by default.
 
@@ -29,11 +29,9 @@ Minimum required Wrangler version: 3.78.6. Check your version by running `wrangl
 
 You must add the observability setting for your Worker to write logs to Workers Logs. Add the following setting to your Worker's `wrangler.toml` file and redeploy your Worker.
 
-	import { WranglerConfig } from "~/components";
-
 <WranglerConfig>
 
-```toml
+	```toml
 	[observability]
 	enabled = true
 	head_sampling_rate = 1 # optional. default = 1.