Match house writing style, add docs/hints.md

bin/cd-deploy

@@ -134,7 +134,7 @@ notify() {
         -H "Title: ${CD_NAME} deploy" \
         -d "${icon} ${CD_NAME} (${CD_ENV}): ${message}" \
         "${CD_NTFY_BASE_URL}/${topic}" >/dev/null 2>&1 \
-        || warn "ntfy notification failed (deploy outcome itself is unaffected)"
+        || warn "ntfy notification failed (the deploy itself is unaffected)"
 }
 
 # ------------------------------------------------------------------- lock ---

bin/cd-status

@@ -4,7 +4,7 @@
 #
 # Written because "the timer is active" was never proof of anything in this
 # fleet -- the same lesson the uas-ng updater documents. This shows the daemon,
-# the socket, and the outcome of the last deploy for each target.
+# the socket, and how the last deploy for each target ended.
 
 set -Eeuo pipefail
 

bin/cd-target

@@ -9,7 +9,7 @@ itself, so there is exactly one implementation of the matching rules.
 Subcommands:
     resolve --repo OWNER/NAME --branch BRANCH [--host HOST]
         Print shell-quoted KEY=VALUE lines for the matching target.
-        Exit 3 when nothing matches (a normal, non-error outcome: it just
+        Exit 3 when nothing matches (a normal, non-error result: it just
         means this push is not ours to act on).
 
     list [--host HOST]