@@ -20,7 +20,7 @@ Here's a brief explanation of how our test runner works.
 - The set of tests to run, and the dependencies required for each test, are then sent to our test runner service.
 
 <Aside>
-To see what code and environment variables endform detects before running your tests, run `npx endform test --dry-run`.
+To see what code and environment variables endform detects, run `npx endform test --debug` for verbose output that includes this information.
 </Aside>
 
 ### Step 2: Distributed execution
 
@@ -29,7 +29,7 @@ Your tests may depend on things like:
 Endform will try to detect and transfer many commonly used pieces of state to the remote runners automatically.
 You may need to do some additional configuration to transfer more state, depending on your setup.
 
-If you want to understand exactly which state Endform will transfer to the remote runners, you can use the `--dry-run` flag to show the files and environment variables that need to be transferred in order to run your tests: `endform test --dry-run`.
+If you want to understand exactly which state Endform will transfer to the remote runners, you can use the `--debug` flag to show the files and environment variables that are transferred: `endform test --debug`.
 
 ## Automatically transferred state
 
@@ -52,9 +52,6 @@ In order for Endform to reduce its exposure to sensitive data, only some environ
 
 The _values_ of the environment variables are taken while running your `playwright.config.ts`, so using a package like [dotenv](https://www.npmjs.com/package/dotenv) in your Playwright config is supported.
 
-In order to get a better understanding of which environment variables are transferred, you can use the `--dry-run` flag to show the complete set of dependencies of your tests: `endform test --debug`.
-This will print out the environment variables that are transferred to the remote runners.
-
 ## Additional configuration
 
 Endform has two additional ways of transferring state to the remote runners: