fixup

Author: emily-shen

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

@@ -868,6 +868,16 @@ To bind other Workers to your Worker, assign an array of the below object to the
 
   - The name of the Worker.
 
+  - To set target a Worker in a specific [environment](/workers/wrangler/environments), you need to append the environment name to the Worker name. This should be in the format `<worker-name>-<environment-name>`. For example, to bind to a Worker called `worker-name` in its `staging` environment, `service` should be set to `worker-name-staging`.
+
+<WranglerConfig>
+
+```toml
+vars = { FOO = "<top-level-var>" }
+[env.staging.vars]
+FOO = "<staging-var>"
+```
+
 - `entrypoint` <Type text="string" /> <MetaInfo text="optional" />
 
   - The name of the [entrypoint](/workers/runtime-apis/bindings/service-bindings/rpc/#named-entrypoints) to bind to. If you do not specify an entrypoint, the default export of the Worker will be used.

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

@@ -83,7 +83,7 @@ kv_namespaces = [
 
 ### Service bindings
 
-To use a [service binding](/workers/wrangler/configuration/#service-bindings) that targets a Worker in a specific environment, you need to include the environment in `service` field. This should be in the format `<worker-name>-<environment-name>`.
+To use a [service binding](/workers/wrangler/configuration/#service-bindings) that targets a Worker in a specific environment, you need to include the environment name in the target worker name that you specify in the `service` field. This should be in the format `<worker-name>-<environment-name>`.
 In the example below, we have two Workers, both with a `staging` environment. `worker-b` has a service binding to `worker-a`. Note how the service binding in the `staging` environment points to `worker-a-staging`, whereas the top-level service binding points to `worker-a`.
 
 <WranglerConfig>