PCX Review

Author: Oxyjun

src/content/docs/browser-rendering/faq.mdx

@@ -25,7 +25,7 @@ If you cannot find the answer you are looking for, join us on [Discord](https://
 Not yet. Local development currently has the following limitation(s):
 - Requests larger than 1 MB are not supported.
 
-To interact with a real headless browser during local development, set `"remote" : true` in the Browser binding configuration. You can learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
+<Render file="remote-binding-note" product="workers" />
 
 ### Will Browser Rendering bypass Cloudflare's Bot Protection?
 

src/content/docs/browser-rendering/how-to/pdf-generation.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 1
 ---
 
-import { Aside, WranglerConfig, PackageManagers } from "~/components";
+import { Aside, WranglerConfig, PackageManagers, Render } from "~/components";
 
 As seen in [this Workers bindings guide](/browser-rendering/workers-bindings/screenshots/), Browser Rendering can be used to generate screenshots for any given URL. Alongside screenshots, you can also generate full PDF documents for a given webpage, and can also provide the webpage markup and style ourselves.
 
@@ -36,14 +36,10 @@ The following example shows you how to generate a PDF using [Puppeteer](/browser
 browser = { binding = "BROWSER" }
 ```
 
-:::note
-
-During local development the configuration above will use a local browser simulation, to instead interact with a real headless browser during local development, set `"remote" : true` in the Browser binding configuration. You can learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
-
-:::
-
 </WranglerConfig>
 
+<Render file="remote-binding-note" product="workers" />
+
 4. Replace the contents of `src/index.ts` (or `src/index.js` for JavaScript projects) with the following skeleton script:
 
 ```ts

src/content/docs/browser-rendering/platform/wrangler.mdx

@@ -46,4 +46,4 @@ const browser = await puppeteer.launch(env.MYBROWSER);
 
 Run `npx wrangler dev` to test your Worker locally.
 
-To interact with a real headless browser during local development, set `"remote" : true` in the Browser binding configuration. You can learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
+<Render file="remote-binding-note" product="workers" />

src/content/docs/browser-rendering/workers-bindings/browser-rendering-with-DO.mdx

@@ -212,7 +212,7 @@ export class Browser {
 
 Run `npx wrangler dev` to test your Worker locally.
 
-To interact with a real headless browser during local development, set `"remote" : true` in the Browser binding configuration. You can learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
+<Render file="remote-binding-note" product="workers" />
 
 ## 7. Deploy
 

src/content/docs/browser-rendering/workers-bindings/reuse-sessions.mdx

@@ -146,7 +146,7 @@ Besides `puppeteer.sessions()`, we have added other methods to facilitate [Sessi
 
 Run `npx wrangler dev` to test your Worker locally.
 
-To interact with a real headless browser during local development, set `"remote" : true` in the Browser binding configuration. You can learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
+<Render file="remote-binding-note" product="workers" />
 
 To test go to the following URL:
 

src/content/docs/d1/best-practices/local-development.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 8
 ---
 
-import { WranglerConfig } from "~/components";
+import { WranglerConfig, Render } from "~/components";
 
 D1 has fully-featured support for local development, running the same version of D1 as Cloudflare runs globally. Local development uses [Wrangler](/workers/wrangler/install-and-update/), the command-line interface for Workers, to manage local development sessions and state.
 
@@ -67,7 +67,7 @@ database_id = "c020574a-5623-407b-be0c-cd192bab9545"
 
 </WranglerConfig>
 
-Note that `wrangler dev` separates local and production (remote) data. A local session does not have access to your production data by default. To access your production (remote) database, set `"remote" : true` in the D1 binding configuration. You can learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings). Any changes you make when running against a remote database cannot be undone.
+Note that `wrangler dev` separates local and production (remote) data. A local session does not have access to your production data by default. To access your production (remote) database, set `"remote" : true` in the D1 binding configuration. Refer to the [remote bindings documentation](/workers/development-testing/#remote-bindings) for more information. Any changes you make when running against a remote database cannot be undone.
 
 Refer to the [`wrangler dev` documentation](/workers/wrangler/commands/#dev) to learn more about how to configure a local development session.
 

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

@@ -280,7 +280,7 @@ Upon successful execution, a new table will be added to your database.
 
 :::note
 
-The table will be created in the local instance of the database. If you want to add this table to your production database set `"remote" : true` in the D1 binding configuration. You can learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
+The table will be created in the local instance of the database. If you want to add this table to your production database set `"remote" : true` in the D1 binding configuration. Refer to the [remote bindings documentation](/workers/development-testing/#remote-bindings) for more information.
 
 :::
 

src/content/docs/d1/tutorials/using-read-replication-for-e-com/index.mdx

@@ -857,7 +857,9 @@ curl -X POST http://localhost:8787/api/product \
 
 :::note
 
-Read replication is only used when the application has been [deployed](/d1/tutorials/using-read-replication-for-e-com/#step-9-deploy-the-application). D1 does not create read replicas when you develop locally. To test it locally, you can set `"remote" : true` in the D1 binding configuration. You can learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
+Read replication is only used when the application has been [deployed](/d1/tutorials/using-read-replication-for-e-com/#step-9-deploy-the-application). D1 does not create read replicas when you develop locally.
+
+To test it locally, you can set `"remote" : true` in the D1 binding configuration. Refer to the [remote bindings documentation](/workers/development-testing/#remote-bindings) for more information.
 
 :::
 

src/content/docs/kv/concepts/kv-bindings.mdx

@@ -60,7 +60,7 @@ export default {
 
 When you use Wrangler to develop locally with the `wrangler dev` command, Wrangler will default to using a local version of KV to avoid interfering with any of your live production data in KV. This means that reading keys that you have not written locally will return `null`.
 
-To have `wrangler dev` connect to your Workers KV namespace running on Cloudflare's global network, set `"remote" : true` in the KV binding configuration. You can learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
+To have `wrangler dev` connect to your Workers KV namespace running on Cloudflare's global network, set `"remote" : true` in the KV binding configuration. Refer to the [remote bindings documentation](/workers/development-testing/#remote-bindings) for more information.
 
 <WranglerConfig>
 

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

@@ -336,9 +336,9 @@ You can view key-value pairs directly from the dashboard.
 
 When using [`wrangler dev`](/workers/wrangler/commands/#dev) to develop locally, Wrangler defaults to using a local version of KV to avoid interfering with any of your live production data in KV. This means that reading keys that you have not written locally returns null.
 
-To have `wrangler dev` connect to your Workers KV namespace running on Cloudflare's global network, you can set `"remote" : true` in the KV binding configuration. You can learn more in our [remote bindings documentation](/workers/development-testing/#remote-bindings).
+To have `wrangler dev` connect to your Workers KV namespace running on Cloudflare's global network, you can set `"remote" : true` in the KV binding configuration. Refer to the [remote bindings documentation](/workers/development-testing/#remote-bindings) for more information.
 
-Refer to the [KV binding docs](/kv/concepts/kv-bindings/#use-kv-bindings-when-developing-locally) for more information.
+Also refer to [KV binding docs](/kv/concepts/kv-bindings/#use-kv-bindings-when-developing-locally).
 
 :::