diff --git a/src/content/docs/workers/development-testing/index.mdx b/src/content/docs/workers/development-testing/index.mdx
index 681fbf97a703acd..fb224a60221c3a3 100644
--- a/src/content/docs/workers/development-testing/index.mdx
+++ b/src/content/docs/workers/development-testing/index.mdx
@@ -302,11 +302,15 @@ If `experimental_remote: true` is specified in Wrangler configuration for any of
 
 - [**Durable Objects**](/workers/wrangler/configuration/#durable-objects): Enabling remote connections for Durable Objects may be supported in the future, but currently will always run locally.
 
+- [**RPC on service bindings**](/workers/runtime-apis/bindings/service-bindings/rpc/): While you can make `fetch()` calls on remote service bindings, you cannot currently call RPC methods on remote service bindings.
+
+- [**Workflows**](/workflows/): Enabling remote connections for Workflows may be supported in the future, but currently will only run locally.
+
 - [**Environment Variables (`vars`)**](/workers/wrangler/configuration/#environment-variables): Environment variables are intended to be distinct between local development and deployed environments. They are easily configurable locally (such as in a `.dev.vars` file or directly in Wrangler configuration).
 
 - [**Secrets**](/workers/wrangler/configuration/#secrets): Like environment variables, secrets are expected to have different values in local development versus deployed environments for security reasons. Use `.dev.vars` for local secret management.
 
-- **[Static Assets](/workers/wrangler/configuration/#assets)**: Static assets are always served from your local disk during development for speed and direct feedback on changes.
+- [**Static Assets**](/workers/wrangler/configuration/#assets) Static assets are always served from your local disk during development for speed and direct feedback on changes.
 
 - [**Version Metadata**](/workers/runtime-apis/bindings/version-metadata/): Since your Worker code is running locally, version metadata (like commit hash, version tags) associated with a specific deployed version is not applicable or accurate.
 
diff --git a/src/content/partials/workers/bindings_per_env.mdx b/src/content/partials/workers/bindings_per_env.mdx
index fb7126434ca7987..aadcb2b1c218565 100644
--- a/src/content/partials/workers/bindings_per_env.mdx
+++ b/src/content/partials/workers/bindings_per_env.mdx
@@ -4,9 +4,9 @@
 
 ## Local development
 
-During local development, your Worker code always executes locally and bindings connect to locally simulated resources [by default](/workers/development-testing/#remote-bindings).
+**Local simulations**: During local development, your Worker code always executes locally and bindings connect to locally simulated resources [by default](/workers/development-testing/#remote-bindings). This is supported in [`wrangler dev`](/workers/wrangler/commands/#dev) and the [Cloudflare Vite plugin](/workers/vite-plugin/).
 
-You can configure [**remote bindings** during local development](/workers/development-testing/#remote-bindings), allowing your bindings to connect to a deployed resource on a per-binding basis.
+**Remote binding connections:**: Allows you to connect to remote, deployed resources on a per-binding basis. Supported in [`wrangler dev --x-remote-bindings`](/workers/development-testing/#using-wrangler-with-remote-bindings) and the [Cloudflare Vite plugin](/workers/development-testing/#using-vite-with-remote-bindings).
 
 | Binding                                 | Local simulations | Remote binding connections |
 | --------------------------------------- | :---------------: | :------------------------: |
@@ -25,13 +25,11 @@ You can configure [**remote bindings** during local development](/workers/develo
 | **Queues**                              |        ✅         |             ✅             |
 | **R2**                                  |        ✅         |             ✅             |
 | **Rate Limiting**                       |        ✅         |             ❌             |
-| **Service Bindings (multiple Workers)** |        ✅         |             ✅             |
+| **Service Bindings (multiple Workers)** |        ✅         |          ✅ [^1]           |
 | **Vectorize**                           |        ❌         |             ✅             |
-| **Workflows**                           |        ✅         |             ✅             |
+| **Workflows**                           |        ✅         |             ❌             |
 
-- **Local simulations:** Bindings connect to local resource simulations. Supported in [`wrangler dev`](/workers/wrangler/commands/#dev) and the [Cloudflare Vite plugin](/workers/vite-plugin/).
-
-- **Remote binding connections:** Bindings connect to remote resources via `experimental_remote: true` configuration. Supported in [`wrangler dev --x-remote-bindings`](/workers/development-testing/#using-wrangler-with-remote-bindings) and the [Cloudflare Vite plugin](/workers/development-testing/#using-vite-with-remote-bindings).
+[^1]: While you can make `fetch()` calls on remote service bindings, you cannot currently call RPC methods on remote service bindings.
 
 ## Remote development