Apply suggestions from code review

Co-authored-by: Pete Bacon Darwin <[email protected]>

Author: dario-piotrowicz

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

@@ -1298,7 +1298,7 @@ When this `config.json` file exists, Wrangler will follow the `configPath` (rela
 Wrangler will display messaging to the user to indicate that the configuration has been redirected to a different file than the user's configuration file.
 
 The generated configuration file should not include any [environments](#environments).
-This is because such a file, when required, should be created based on a target environment's specific values and tools should generate distinct configuration files for different environments.
+This is because such a file, when required, should be created as part of a build step, which should already target a specific environment. These build tools should generate distinct deployment configuration files for different environments.
 
 ### Custom build tool example
 
@@ -1334,7 +1334,7 @@ A common example of using a redirected configuration is where a custom build too
 
   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.
+- 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.
   It also creates a `.wrangler/deploy/config.json` file that redirects Wrangler to the new, generated deployment configuration file:
 
   <FileTree>