diff --git a/apps/site/pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md b/apps/site/pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md
index e30a18b495d8b..d4d84c6c2e04d 100644
--- a/apps/site/pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md
+++ b/apps/site/pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md
@@ -58,8 +58,8 @@ node --env-file=.env --env-file=.development.env app.js
 
 > Note: if the same variable is defined in the environment and in the file, the value from the environment takes precedence.
 
-But there may be a problem: if the file doesn't exist, it will return an error.
-To avoid this, you can use the `--env-file-if-exists` flag.
+In case you want to optionally read from a `.env` file, it's possible to avoid
+throwing an error if the file is missing using the `--env-file-if-exists` flag.
 
 ```bash
 node --env-file-if-exists=.env app.js