Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

docs(scripts): rewrap the snapshot comment and drop stray dashes

Yudhi Armyndharis467f893cffb4
diff --git a/docs/11-operational-runbooks.md b/docs/11-operational-runbooks.md
index d9453daf3..1498ccbf3 100644
--- a/docs/11-operational-runbooks.md
+++ b/docs/11-operational-runbooks.md
@@ -616,7 +616,7 @@ User-managed files outside that list (for example the project-level `.env`) must
# (.api-key from BOOTSTRAP_KEY_FILE when that is set)
#
# The database paths resolve exactly like the app: MAIN_DATABASE_NAME / DATABASE_NAME from the
-# environment, then ./.env, then <data dir>/.env.generated, otherwise the fixed ./data defaults — they
+# environment, then ./.env, then <data dir>/.env.generated, otherwise the fixed ./data defaults; they
# are NOT derived from OPENWA_DATA_DIR. A missing source database fails the run (no silent empty
# backup), the finished archive is checked to contain every configured database, and with the sqlite3
# CLI present the databases are snapshotted online via .backup (otherwise plain-copied with a
diff --git a/scripts/lib-env.sh b/scripts/lib-env.sh
index b36664d07..252a450b5 100644
--- a/scripts/lib-env.sh
+++ b/scripts/lib-env.sh
@@ -18,7 +18,7 @@
# Deliberately conservative: only a plain `KEY=value` line is honoured. Blanks around the `=` and the
# value, and CRLF line endings, are tolerated as dotenv tolerates them. A value carrying quotes or a
# `#`, and a `KEY: value` line, are reported and skipped rather than guessed at, because a silently
-# mis-parsed path is the exact failure this exists to prevent. Nothing here exports anything — each
+# mis-parsed path is the exact failure this exists to prevent. Nothing here exports anything: each
# key is looked up by name, so a stray entry in an operator's .env can never reach the script's own
# environment.
diff --git a/scripts/restore.sh b/scripts/restore.sh
index c03721ffe..becf19660 100755
--- a/scripts/restore.sh
+++ b/scripts/restore.sh
@@ -20,7 +20,7 @@
# Both resolve EXACTLY like the app: the environment first, then ./.env, then
# .env.generated (the archive's copy when it carries one, else the data dir's),
# otherwise the fixed ./data default (see lib-env.sh). They are NOT derived
-# from OPENWA_DATA_DIR — restoring there would write databases the app never
+# from OPENWA_DATA_DIR; restoring there would write databases the app never
# reads (fresh-empty boot + new master key).
# OPENWA_DATA_DIR data directory to restore non-DB state into (default: ./data)
# SESSION_DATA_PATH, BAILEYS_AUTH_DIR, STORAGE_LOCAL_PATH, PLUGINS_DIR
@@ -182,9 +182,9 @@ replace_tree() {
# The data-dir safety snapshot below cannot cover a target that lives OUTSIDE it (a custom
# MAIN_DATABASE_NAME / DATABASE_NAME, SESSION_DATA_PATH, BAILEYS_AUTH_DIR, STORAGE_LOCAL_PATH,
-# PLUGINS_DIR or BOOTSTRAP_KEY_FILE). Preserve such a target separately, so a restore pointed at the wrong archive remains
-# recoverable. OPENWA_RESTORE_SNAPSHOT_DIR takes these snapshots too when it is set: a target on its
-# own mount under a read-only root has no writable place next to it.
+# PLUGINS_DIR or BOOTSTRAP_KEY_FILE). Preserve such a target separately, so a restore pointed at the
+# wrong archive remains recoverable. OPENWA_RESTORE_SNAPSHOT_DIR takes these snapshots too when it is
+# set: a target on its own mount under a read-only root has no writable place next to it.
snapshot_external() {
target="$1"
external_snapshot=""