docs: reworded a couple of built-in agent descriptors

Agents.md

@@ -945,13 +945,13 @@ Coyote comes packaged with some useful built-in agents:
    `other:<label>` via a design-time `librarian` lookup), which flows into every downstream reviewer, with
    an evidence-cited rejection protocol for convention findings.
 * `coder`: An agent to assist you with all your coding tasks
-* `code-reviewer`: A [CodeRabbit](https://coderabbit.ai)-style graph-based review orchestrator — the deterministic
+* `code-reviewer`: A [CodeRabbit](https://coderabbit.ai)-style graph-based review orchestrator. This is the deterministic
    shell around LLM review judgment. Scripts resolve the diff, the quality bar (`rigor` + `surfaces`: caller-passed,
    read from the active plan's frontmatter, or detected from the diff), repo conventions, matching review-miss
    ledger patterns, and repo-history signals (fix/revert clusters plus prior PR review comments on fragile paths);
    domain linters (tflint, hadolint, actionlint, `buf breaking`) run unconditionally when installed. Changed files
-   are grouped into DOMAIN slices — deterministic proposal, LLM refinement, and an exact-cover gate so no file can
+   are grouped into DOMAIN slices with deterministic proposal, LLM refinement, and an exact-cover gate so no file can
-   be lost — and each slice is reviewed in parallel by a `domain-reviewer` leader with peer messaging between
+   be lost, and each slice is reviewed in parallel by a `domain-reviewer` leader with peer messaging between
    leaders; every leader report passes a completeness gate (mandatory sections present even when clean,
    reject-and-retry once). A synthesis node with NO verdict authority merges findings, `finding-verifier`
    re-validates every 🔴/🟡 on an unskippable graph edge, and a SCRIPT computes the rigor folding
@@ -964,7 +964,7 @@ Coyote comes packaged with some useful built-in agents:
 * `domain-reviewer`: A domain-slice review leader (used by the `code-reviewer` graph). Where `file-reviewer`
    reviews one file in isolation, `domain-reviewer` reviews a group of RELATED changed files (e.g. the DB migration
    plus the queries that use it, the routes plus their handlers, etc.) as one coherent unit: guard symmetry across the
-   slice's sibling paths, literal/enum drift between files, schema↔usage mismatch, and slice-level blast-radius /
+   slice's sibling paths, literal/enum drift between files, schema <-> usage mismatch, and slice-level blast-radius /
    test-adequacy / removed-guard checks reported even when clean. Small slices are reviewed directly with the full
    skill stack; larger ones fan out one `file-reviewer` per file with a sibling roster. Leaders run as parallel
    map branches with teammate messaging armed, so the DB leader can warn the API leader about a renamed column
@@ -985,7 +985,7 @@ Coyote comes packaged with some useful built-in agents:
    the reviewer's assumptions, re-reads the cited code, and returns `VERIFIED` (with quoted evidence), `FALSE`
    (only with proof, e.g. the "missing" guard exists at another path:line), or `UNVERIFIABLE` (kept, marked). Each branch's verdict passes a deterministic contract gate
    (machine-validated JSON, authoritative id stamped from the finding itself, retry once; malformed output
-   records `UNVERIFIABLE` — a bad branch never sinks the run).
+   records `UNVERIFIABLE`, so a bad branch never sinks the run).
    It never re-judges severity. It only tests whether a claim is true. `code-reviewer` uses the verdicts to
    drop provably-false findings before the final report; dropped findings are tallied, never silently vanished.
 * `gatekeeper`: A plan self-containedness gate (via the `plan-gatekeeping` skill). Audits a plan against