Catching more instances of wrangler.toml.

Author: Oxyjun

src/content/docs/d1/examples/d1-and-remix.mdx

@@ -20,7 +20,7 @@ To set up a new Remix site on Cloudflare Pages that can query D1:
 
 1. **Refer to [the Remix guide](/pages/framework-guides/deploy-a-remix-site/)**.
 2. Bind a D1 database to your [Pages Function](/pages/functions/bindings/#d1-databases).
-3. Pass the `--d1 BINDING_NAME=DATABASE_ID` flag to `wrangler dev` when developing locally. `BINDING_NAME` should match what call in your code, and `DATABASE_ID` should match the `database_id` defined in your wrangler.toml: for example, `--d1 DB=xxxx-xxxx-xxxx-xxxx-xxxx`.
+3. Pass the `--d1 BINDING_NAME=DATABASE_ID` flag to `wrangler dev` when developing locally. `BINDING_NAME` should match what call in your code, and `DATABASE_ID` should match the `database_id` defined in your Wrangler configuration file: for example, `--d1 DB=xxxx-xxxx-xxxx-xxxx-xxxx`.
 
 The following example shows you how to define a Remix [`loader`](https://remix.run/docs/en/main/route/loader) that has a binding to a D1 database.
 

src/content/docs/d1/examples/d1-and-sveltekit.mdx

@@ -22,7 +22,7 @@ To set up a new SvelteKit site on Cloudflare Pages that can query D1:
 1. **Refer to [the SvelteKit guide](/pages/framework-guides/deploy-a-svelte-kit-site/) and Svelte's [Cloudflare adapter](https://kit.svelte.dev/docs/adapter-cloudflare)**.
 2. Install the Cloudflare adapter within your SvelteKit project: `npm i -D @sveltejs/adapter-cloudflare`.
 3. Bind a D1 database [to your Pages Function](/pages/functions/bindings/#d1-databases).
-4. Pass the `--d1 BINDING_NAME=DATABASE_ID` flag to `wrangler dev` when developing locally. `BINDING_NAME` should match what call in your code, and `DATABASE_ID` should match the `database_id` defined in your wrangler.toml: for example, `--d1 DB=xxxx-xxxx-xxxx-xxxx-xxxx`.
+4. Pass the `--d1 BINDING_NAME=DATABASE_ID` flag to `wrangler dev` when developing locally. `BINDING_NAME` should match what call in your code, and `DATABASE_ID` should match the `database_id` defined in your Wrangler configuration file: for example, `--d1 DB=xxxx-xxxx-xxxx-xxxx-xxxx`.
 
 The following example shows you how to create a server endpoint configured to query D1.
 

src/content/docs/d1/worker-api/d1-database.mdx

@@ -11,7 +11,7 @@ To interact with your D1 database from your Worker, you need to access it throug
 
 ```js
 async fetch(request, env) {
-	// D1 database is 'env.DB', where "DB" is the binding name from the Wrangler.toml file.
+	// D1 database is 'env.DB', where "DB" is the binding name from the Wrangler configuration file.
 }
 ```
 

src/content/docs/hyperdrive/configuration/connect-to-postgres.mdx

@@ -118,7 +118,7 @@ Create a new `Client` instance and pass the Hyperdrive parameters:
 import { Client } from "pg";
 
 export interface Env {
-	// If you set another name in wrangler.toml as the value for 'binding',
+	// If you set another name in the Wrangler configuration file as the value for 'binding',
 	// replace "HYPERDRIVE" with the variable name you defined.
 	HYPERDRIVE: Hyperdrive;
 }

src/content/docs/queues/tutorials/web-crawler-with-browser-rendering/index.mdx

@@ -82,7 +82,7 @@ binding = "crawler_screenshots"
 id = "<GENERATED_NAMESPACE_ID>"
 ```
 
-### Add KV bindings to wrangler.toml
+### Add KV bindings to the Wrangler configuration file
 
 Then, in your Wrangler file, add the following with the values generated in the terminal:
 

src/content/docs/workers/languages/python/how-python-workers-work.mdx

@@ -24,7 +24,7 @@ async def on_fetch(request, env):
     return Response.new("Hello world!")
 ```
 
-…with a wrangler.toml file that points to a .py file:
+…with a Wrangler configuration file that points to a .py file:
 
 <WranglerConfig>
 

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

@@ -1158,7 +1158,7 @@ export default fetch;
 
 You can use module aliasing to provide your own polyfill implementation of a Node.js API that is not yet available in the Workers runtime.
 
-For example, let’s say the NPM package you rely on calls [`fs.readFile`](https://nodejs.org/api/fs.html#fsreadfilepath-options-callback). You can alias the fs module by adding the following to your Worker’s wrangler.toml:
+For example, let's say the NPM package you rely on calls [`fs.readFile`](https://nodejs.org/api/fs.html#fsreadfilepath-options-callback). You can alias the fs module by adding the following to your Worker's Wrangler configuration file:
 
 <WranglerConfig>
 

src/content/docs/workflows/examples/backup-d1.mdx

@@ -120,7 +120,7 @@ Here is a minimal package.json:
 }
 ```
 
-Here is a wrangler.toml:
+Here is a Wrangler configuration file:
 
 <WranglerConfig>
 

src/content/docs/workflows/examples/send-invoices.mdx

@@ -201,7 +201,7 @@ Here's a minimal package.json:
 }
 ```
 
-And finally wrangler.toml:
+And finally Wrangler configuration file:
 
 <WranglerConfig>
 

src/content/partials/hyperdrive/use-postgresjs-to-make-query.mdx

@@ -14,7 +14,7 @@ Create a new `sql` instance and pass the Hyperdrive parameters:
 import postgres from "postgres";
 
 export interface Env {
-	// If you set another name in wrangler.toml as the value for 'binding',
+	// If you set another name in the Wrangler configuration file as the value for 'binding',
 	// replace "HYPERDRIVE" with the variable name you defined.
 	HYPERDRIVE: Hyperdrive;
 }