Use plain, direct English.
- Write for fast comprehension and skimming. Put the main point first and use short, straightforward sentences.
- Keep necessary technical terminology, but avoid jargon, cryptic shorthand, inflated vocabulary, academic phrasing, corporate language, rhetorical flourishes, and wording that sounds clever for its own sake.
- Ssimplify the language and sentence structure, not the underlying concept.
- Keep related information together and avoid jumping between high-level concepts and implementation details without a clear transition.
- Use a neutral, practical, collaborative developer tone. Avoid sounding smug, self-important, promotional, condescending, or overly formal.
- Prefer high-signal communication over high-volume communication.