plain-languagelisted

# Plain Language Clear, direct, useful. The reader gets it on one read. ## The core rule **Write so your reader can find, understand, and use what they need on the first read.** Plain language is not dumbing down — it is removing obstacles: wordiness, passive construction, jargon, and buried logic. Workflow: `decide who the reader is and what they must do` → `front-load the key point` → `cut every word that is not doing work` → `run the verification checklist`. ## Mechanics 1. **Front-load the point.** First sentence states the purpose, conclusion, or action. No throat-clearing. 2. **Short sentences.** Average 15–20 words; hard cap ~25. One idea per sentence. 3. **Active voice.** Subject acts: "The team shipped the fix" not "The fix was shipped by the team." Reserve passive for when the actor is truly unknown or irrelevant. 4. **Common words.** Plain terms over Latinates: "use" not "utilize", "end" not "terminate", "ask" not "request". 5. **Actionable verbs.** Name the action: "we will refund you" not "a refund will be issued". 6. **You, not we/them.** Address the reader directly where appropriate ("you must renew your license"). 7. **Short paragraphs.** One topic per paragraph; 3–5 sentences max. 8. **No jargon, no abbreviations without explanation.** If a term is unavoidable, define it the first time in plain words. 9. **Headers that work.** Headings answer questions or state outcomes ("How to apply", "What happens next"). ## Verify - Every sentence ≤ 25 words (long