diff --git a/v2:-Documentation.md b/v2:-Documentation.md
index f775f5e..03947a8 100644
--- a/v2:-Documentation.md
+++ b/v2:-Documentation.md
@@ -91,9 +91,10 @@ Starts the Caddy process, optionally bootstrapped with an initial config file. B
 ```
 $ caddy run
 	[--config <path>]
+	[--print-env]
 ```
 
-Same as `start`, but blocks indefinitely; i.e. runs Caddy in "daemon" mode. On Windows, this is recommended over `caddy start` when running Caddy manually since it will be more obvious that Caddy is still running and bound to the terminal window.
+Same as `start`, but blocks indefinitely; i.e. runs Caddy in "daemon" mode. On Windows, this is recommended over `caddy start` when running Caddy manually since it will be more obvious that Caddy is still running and bound to the terminal window. If `--print-env` is specified, the environment as seen by the Caddy process will be printed before starting. This is the same as the `environ` command but does not quit after printing.
 
 ## stop
 
@@ -101,7 +102,7 @@ Same as `start`, but blocks indefinitely; i.e. runs Caddy in "daemon" mode. On W
 $ caddy stop
 ```
 
-Gracefully stops the running Caddy process. (Note: this will stop any process named the same as the executable file.) On Windows, this stop is forceful and Caddy will not have an opportunity to do a graceful shutdown and clean up any active locks.  A graceful shutdown can be performed by POSTing to  `/stop` Admin endpoint [soon to be implemented](https://github.com/caddyserver/caddy/pull/2671).
+Gracefully stops the running Caddy process. (Note: this will stop any process named the same as the executable file.) On Windows, this stop is forceful and Caddy will not have an opportunity to do a graceful shutdown and clean up any active locks. A graceful shutdown can be performed by POSTing to /stop endpoint [soon to be implemented](https://github.com/caddyserver/caddy/pull/2671).
 
 ## reload