Add details on how to disable remote binding in wrangler dev, getPlatformProxy and the vite plugin

src/content/docs/workers/vite-plugin/reference/api.mdx

@@ -73,6 +73,11 @@ It accepts an optional `PluginConfig` parameter.
   You can inspect the `dist` directory and then run `wrangler deploy -c dist/<auxiliary-worker>/wrangler.json` for each.
   :::
 
+- `remoteBindings` <Type text='boolean' /> <MetaInfo text='optional' />
+
+  Whether or not [remote bindings](/workers/development-testing/#remote-bindings) should be enabled, they are by default.
+
+
 ## `interface AuxiliaryWorkerConfig`
 
 - `configPath` <Type text='string' />

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

@@ -300,11 +300,9 @@ const platform = await getPlatformProxy(options);
 
       **Note:** If you use `wrangler`'s `--persist-to` option, note that this option adds a subdirectory called `v3` under the hood while `getPlatformProxy`'s `persist` does not. For example, if you run `wrangler dev --persist-to ./my-directory`, to reuse the same location using `getPlatformProxy`, you will have to specify: `persist: { path: "./my-directory/v3" }`.
 
-    - `experimental` `{ remoteBindings: boolean }`
+    - `remoteBindings` boolean <MetaInfo text="optional (default: `true`)" />
 
-      Object used to enable experimental features, no guarantees are made to the stability of this API, use at your own risk.
-
-      - `remoteBindings` Enables `getPlatformProxy` to connect to [remote bindings](/workers/development-testing/#remote-bindings).
+      Whether or not [remote bindings](/workers/development-testing/#remote-bindings) should be enabled.
 
 ### Return Type
 

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

@@ -246,6 +246,10 @@ None of the options for this command are required. Many of these options can be
   - Show the interactive dev session.
 - `--alias` `Array<string>`
   - Specify modules to alias using [module aliasing](/workers/wrangler/configuration/#module-aliasing).
+- `--local` <Type text="boolean" /> <MetaInfo text="(default: false) optional" />
+  - Run in local mode. In this mode:
+    - the Worker code is running locally on your machine
+    - all [remote bindings](/workers/development-testing/#remote-bindings) are disabled, which behaves exactly as if there were configured with `remote: false`.
 
 <Render file="wrangler-commands/global-flags" product="workers" />