docs: wording / less verbose

docs/operators/handbook.md

@@ -552,7 +552,7 @@ 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 recipe version (standard `abra app deploy`)
+1. latest recipe version if no `.env` version (standard `abra app deploy`)
 1. version retrieved from the app `.env` (`abra app deploy` + `TYPE=custom-html:1.7.1+1.27.2`)
 1. latest commit (`--chaos/-C` / `abra app deploy` + no released recipe versions)
 1. latest commit with unstaged changes (`abra app deploy --chaos/-C`)
@@ -561,19 +561,15 @@ to deploy the following kinds of versions with `abra app deploy`:
 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
-is used using `abra app deploy`. This is done to reduce unwanted upgrades (we
-do not automatically choose the latest release).
+The version is chosen using the following priority logic.
 
-The version is chosen using the following logic.
-
-1. version from cli argument
-1. version from .env file
-1. version from deployed app
-1. version from catalogue (if undeployed)
+1. cli argument
+1. `.env` file
+1. deployed app
+1. recipe catalogue (if undeployed)
 
 Use `--ignore-env-version/-i` to deploy the latest release version or commit.
+
 In all cases 3-5, the app `.env` version is **ignored** as a version candidate.
 
 ### `abra app upgrade`