diff --git a/CHANGELOG.md b/CHANGELOG.md
index af5035f..29243ac 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -8,6 +8,10 @@ Please choose versions by [Semantic Versioning](http://semver.org/).
 * MINOR version when you add functionality in a backwards-compatible manner, and
 * PATCH version when you make backwards-compatible bug fixes.
 
+## Unreleased
+
+- docs: correct `commands/update-task.md` — checkboxes are ticked by direct body edit, then `vault-cli task update` syncs the derived status; the CLI cannot tick a specific checkbox (it recomputes status from checkbox counts via `statusFromProgress`)
+
 ## v0.116.4
 
 - test: assert the liveness window against `livenessWindow` via the injected waiter instead of a wall-clock tolerance — the previous spec finished in microseconds against a no-op waiter and would have passed for any window value, including zero
diff --git a/commands/update-task.md b/commands/update-task.md
index 8cb16b6..224abea 100644
--- a/commands/update-task.md
+++ b/commands/update-task.md
@@ -23,7 +23,7 @@ The agent handles:
 - Detect task from conversation (file paths, wiki-links, mentions; ranked by confidence)
 - Read current checkbox state from the task file (`[x]` / `[/]` / `[ ]`)
 - Analyze the conversation for completed work (files created/modified, commands run, problems solved)
-- Tick completed checkboxes via `vault-cli task update` (NOT direct Edit on frontmatter)
+- Tick completed checkboxes by direct body Edit (`- [ ]` → `- [x]`), then run `vault-cli task update` to sync the derived status — the CLI cannot tick a specific checkbox (it only recomputes status from checkbox counts via `statusFromProgress` in `pkg/ops/update.go`); direct Edit is on the task body line, never on frontmatter status
 - Determine if the progress is noteworthy (100% complete, major milestone, >20% jump)
 - If noteworthy: append a progress entry to today's daily note
 - If 100% complete: invoke `vault-cli task complete` to finalize