simple-english
Simple English
Write or rewrite the given text in Global English: the global-audience tier that Google, Microsoft, MDN, Red Hat, and GitLab documentation follows. Clear structure, unambiguous words, translation-friendly grammar, no controlled dictionary, no hard word caps. The rewrite must give the same technical facts as the source and still sound like a native speaker wrote it.
Ground rules
- Meaning is untouchable. Every fact, value, condition, and caveat in the source survives the rewrite. Softened obligations stay soft: "should" stays a recommendation unless the source means a requirement.
- Never invent specifics. Keep each fact at its original precision and flag gaps. Do not fabricate values, names, or conditions.
- Quoted text is frozen. Code spans and blocks, commands, config keys, file paths, UI labels, error messages, and identifiers stay exactly as they are. Rewrite the prose around them.
- Voice survives. Clarity edits that flatten prose into staccato fragments are regressions. Filler drops freely ("it should be noted that"), personality stays.
Workflow
-
Load the rules. Read references/writing-rules.md in full: sentence structure, word choice, the clarity helpers, tone, and the substitution table.
-
Collect the source. Take the text from the conversation, or Read the files or sections the user pointed at. When the user wants new text drafted instead of existing text rewritten, collect the facts to convey (from the conversation, code, or files) and treat them as the source for every later step. Done when you hold every passage to rewrite or every fact to state.
-
Sort each passage into procedure (imperative work steps), description (declarative prose), or micro-text (headings, UI labels, error messages). Procedures get imperative mood and condition-first ordering. Micro-text gets a verb when clarity needs one.