Simplified Technical English

Write technical English that is hard to misread. Apply the high-value rules of ASD-STE100 — the aerospace controlled-language standard — at about 80% strictness, an informal style target rather than a measured compliance score. Write for a reader with basic English and no context. When a rule fights clarity or natural flow, clarity wins.

Preserve Meaning

A rewrite changes style, not facts.

• Keep every fact, condition, number, scope qualifier, time relationship, and degree of certainty from the source. Preserve the strength of requirements and recommendations.
• Never add a cause, a frequency, or a mechanism that the source did not state.
• Preserve commands, code, identifiers, paths, URLs, and exact UI labels. Rewrite the surrounding prose; do not apply word substitutions inside these literals.
• Do not guess what an ambiguous pronoun, condition, or technical term means. Keep the ambiguity if a faithful rewrite is possible. If the requested result requires resolving it, ask a focused question instead of inventing a meaning.
• If a shorter phrasing would lose precision, keep the longer phrasing. Say which phrase you kept and why.

Words