diff --git a/docs/operators/handbook.md b/docs/operators/handbook.md
index 1ad3807..333d749 100644
--- a/docs/operators/handbook.md
+++ b/docs/operators/handbook.md
@@ -545,13 +545,14 @@ with `[version]` `--chaos/-C` or `--ignore-env-version/-i`.
 This is the most flexible command so it can be hard to follow. It is possible
 to deploy the following kinds of versions with `abra app deploy`:
 
-1. latest release version (standard `abra app deploy`)
-2. version retrieved from the app `.env` (`TYPE=custom-html:1.7.1+1.27.2`)
-3. latest commit (`--chaos/-C` / no released recipe versions)
-4. latest commit with unstaged changes (`--chaos/-C`)
+1. latest recipe version (standard `abra app deploy`)
+2. version retrieved from the app `.env` (`abra app deploy` + `TYPE=custom-html:1.7.1+1.27.2`)
+3. latest commit (`--chaos/-C` / `abra app deploy` + no released recipe versions)
+4. latest commit with unstaged changes (`abra app deploy --chaos/-C`)
 5. recipe version or Git hash (`abra app deploy 1.7.1+1.27.2`)
 
-The app `.env` version is used as the recipe checkout version. 
+The app `.env` version is always used as the recipe checkout version if
+present.
 
 For 2), if the app **is undeployed** and there is an app `.env` version
 present, then it will be used. This is the *only time* the app `.env` version
@@ -569,9 +570,11 @@ The app must be deployed already to proceed.
 * a specific upgrade (`abra app upgrade 1.7.1+1.27.2`)
 * force re-upgrade (same version, `abra app upgrade --force`)
 
-The app `.env` version is used as the recipe checkout version. However, it is
-otherwise **ignored** for the version candidate. The "source of truth" for the
-version candidate is the live deployment of the app.
+The app `.env` version is always used as the recipe checkout version if
+present.
+
+However, it is otherwise **ignored** for the version candidate. The "source of
+truth" for the version candidate is the live deployment of the app.
 
 ### `abra app rollback`
 
@@ -581,6 +584,8 @@ The app must be deployed already to proceed.
 * a specific downgrade (`abra app rollback 1.7.1+1.27.2`)
 * force re-downgrade (same version, `abra app rollback --force`)
 
-The app `.env` version is used as the recipe checkout version. However, it is
-otherwise **ignored** for the version candidate. The "source of truth" for the
-version candidate is the live deployment of the app.
+The app `.env` version is always used as the recipe checkout version if
+present.
+
+However, it is otherwise **ignored** for the version candidate. The "source of
+truth" for the version candidate is the live deployment of the app.