plain-writing

Topics in the source

• Write like a person
• Remove
• Prefer
• Check before you hand it over

Plain writing respects the reader's time: every sentence carries something they need, in words they already use. Emoji and decorative symbols. An icon from the design system carries a state; the word carries the meaning. A hook refuses new emoji in files. Filler openers and closers. "Great question", "It's worth noting", "In today's fast-paced world", "I hope this helps", "Let me know if you have any questions". Inflated words. "Leverage", "robust", "seamless", "cutting-edge", "delve", "elevate", "unlock", "empower", "game-changer". Hedging stacks. "It might potentially be possible that". Say what you know and how you know it. Belittling words about the reader's work or business: "just a small shop", "simple little app", diminutives. Internal names. Code names, file paths, team jargon and project nicknames the reader has never seen. Invented facts. Every number, date, quote and comparison must come from a source you can point at. If you have none, cut it. Promised effects. "Faster", "more reliable", "should finish sooner", "so you can...": an effect nobody measured or stated is an invented fact. Say what changed ("sync reuses one connection across pages") and stop. In release notes

This is an excerpt. Refer to the complete source and its current requirements.