# EDIT_BRIEF

# Editing pass: condense, cut provenance, kill slop

Read ~/.claude/skills/deslop/SKILL.md (the prose-tell rules) and manuals/STYLE.md before touching a page.

Goal: a manual page a technician would write. Facts, steps, labels, numbers, tables. Nothing else.

Cut on sight:
- Provenance and sourcing talk in the body: "owners report", "the community", "members", "the group", "the team
  says", "the maker", "according to", "the chat", "the firmware source shows", "per the research note". State the
  fact. If a fact cannot stand without its source, move it to the hidden maintenance block or delete it.
- Meta-commentary: sentences about the page, about verification status, about what is covered elsewhere ("this page
  does not cover"). One draft banner line at the top is the only status text.
- "Check:" sentences in the body. Each becomes one bullet in the hidden bench-check block. In the body, an
  unverified value is written as the value plus the single word "unverified" in a table cell or in parentheses.
- Hedging stacks, transitions (moreover, additionally, note that), "it is worth", "keep in mind", "in general",
  "typically", "simply", "just".
- The AI lexicon: leverage, robust, comprehensive, crucial, ensure, seamless, navigate, underscore, utilize,
  facilitate, journey, landscape. Em-dashes. "Not X but Y" framing. Triplets for rhythm.
- Repeated warnings. The seed warning appears once per page that involves a seed, as one sentence.
- Explanations of why something is designed the way it is, unless the reason changes what the reader does.
- Duplicate content that another page owns: one sentence plus a link.

Keep, byte for byte: firmware strings in quotes, menu labels in bold, numbers with units, file names in backticks,
image lines with their capture comments, the hidden maintenance block (update it when you move items into it).

Shape:
- How-to pages: 50 to 90 lines. Lead paragraph of one or two sentences. "What you need" as a short list. Steps as
  numbered or bulleted imperatives, one action each. "What the machine shows" as a short list of exact strings.
  Troubleshooting as a table: symptom, cause, fix.
- Reference pages (capability sheet, troubleshooting, security FAQ, hardware and spares): tables and one-sentence
  paragraphs; no narrative sections; a security answer is two sentences at most.
- Sentence length varies; a long sentence is followed by a short one. Fragments are allowed in tables.
- Headings keep the `{#anchor}` ids; links between pages stay valid.

Output: the edited page in place, and a reply of five lines: lines before and after, what you deleted by category,
what you moved into the bench block.

Vocabulary (added): the machine engraves. Replace every cut, cuts, cutting, re-cut, recut, etch, print, stamp, burn, mark used for
the machine's action with engrave, engraving, engraved. "Hammer" is a part, never a verb.