apply suggested changes

Author: dario-piotrowicz

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

@@ -1323,15 +1323,13 @@ A common example of using a redirected configuration is where a custom build too
 
   This configuration points `main` at the user's code entry-point and defines the `MY_VARIABLE` variable in two different environments.
 
-- Then, the user runs a custom build, which might read the user's Wrangler configuration file to find the source code entry-point:
+- Then, the user runs a custom build for a given environment (for example `staging`). This will read the user's Wrangler configuration file to find the source code entry-point and environment specific settings:
 
   ```bash
-  > my-tool build
+  > my-tool build --env=staging
   ```
 
-  We'll assume that `my-tool` is specifically targeting the `staging` environment (for instance set by the user with some option of `my-tool`).
-
-- This `my-tool` generates a `dist` directory that contains both compiled code and a new generated deployment configuration file, containing only the settings for the given environment.
+- `my-tool` generates a `dist` directory that contains both compiled code and a new generated deployment configuration file, containing only the settings for the given environment.
   It also creates a `.wrangler/deploy/config.json` file that redirects Wrangler to the new, generated deployment configuration file:
 
   <FileTree>