add context and improve clarity

Author: edmundhung

src/content/changelog/workers/2025-08-22-wrangler-dev-multi-config-cross-command-support.mdx

@@ -6,18 +6,14 @@ products:
 date: 2025-08-22
 ---
 
-Workers using `wrangler dev` with multiple config files can now communicate with Workers running in separate dev commands using service bindings and tail consumers.
-
-Previously, cross-command communication only worked when using a single config file. Now it works with multiple configs:
+You can run multiple Workers in a single dev command by passing multiple config files to `wrangler dev` (e.g., `wrangler dev --config api.toml --config frontend.toml`). Previously, these Workers could not communicate with Workers running in separate dev commands. Now service bindings and tail consumers work across dev commands:
 
 ```sh
-# Terminal 1
-wrangler dev
-
-# Terminal 2
+# Terminal 1 - Main Application
 wrangler dev --config ./api/wrangler.jsonc --config ./app/wrangler.jsonc
-```
 
-This means Workers can now communicate with each other across separate dev commands, regardless of your development setup.
+# Terminal 2 - Shared Worker (e.g. auth)
+wrangler dev --config ./auth/wrangler.jsonc
+```
 
-Check out the [Developing with multiple Workers](/workers/development-testing/multi-workers) guide to learn more about the different approaches and when to use each one.
+Workers can now communicate with each other across separate dev commands, regardless of your development setup. Check out the [Developing with multiple Workers](/workers/development-testing/multi-workers) guide to learn more about the different approaches and when to use each one.