
A technical document, such as a set of instructions or a report, can be grammatically correct and still leave a reader unsure what action to take or what a result means. The reader needs to understand the information, not spend time working out what a sentence means. Consistent wording is one way to reduce that risk.
ASD is the Aerospace, Security and Defence Industries Association of Europe. STE means Simplified Technical English. ASD-STE100 is its standard for technical documentation; I am referring to Issue 9, published on 15 January 2025. It combines writing rules with a controlled dictionary. The rules guide sentence structure and word choice. The dictionary gives approved words and meanings, generally assigning each word one approved meaning and part of speech. It favours familiar, specific wording and reduces unnecessary variation in synonyms1.
Used consistently, the standard is intended to make technical instructions easier to understand, review, translate, and maintain. It gives a team a shared way to reduce variation in its documentation.
Clear wording still needs a technical check. The author and reviewer need to confirm an instruction is technically correct, safe, and suitable for its context. ASD-STE100 supplies the writing rules; engineering review checks the instruction against the equipment and task.
Spelling is a project decision
I’m Scottish, and I force my writing to use British English. ASD-STE100 defaults to American spelling, but Rule 1.14 allows another official directive to apply. For my writing, that directive is British English2.
Keep exact spelling in product names, quotations, source code, commands, and interface identifiers. They may need to match something outside the document.
Names need the same care. A computer form or typeface may not preserve how someone writes their name. I have written about the raised *c* in Scottish surnames, and the compromises computers impose, in Scottish Last Names on Computers.
Clear wording also depends on how measurements are written. SI symbols and spacing carry meaning: for example, write a space between a value and its unit symbol, as in 36 °C. I have a separate guide to special symbols used in engineering reports, including ways to enter characters that are awkward to type.
Requirement words need care
In specifications, words such as MUST, SHALL, SHOULD, and MAY can carry defined meanings. BCP 14 (Best Current Practice 14) is the IETF convention set out in RFC 2119 and clarified by RFC 8174. The key words have their special meanings only when they are uppercase and the document invokes BCP 14. Under RFC 2119, SHALL means the same as MUST, SHOULD is a recommendation, and MAY means an action is optional.3
ASD-STE100’s recurring-error list directs writers from ordinary uses of *shall* and *should* to *must*, and from *may* to *can*. These recommendations apply to writing in STE. The difference matters for *should*: BCP 14 *SHOULD* is a recommendation, while the STE list directs the ordinary verb *should* to *must*. Replacing a BCP 14 *SHOULD* with *MUST* changes a recommendation into a requirement. Similarly, *can* may describe ability or permission; it does not always preserve the optional meaning of BCP 14 *MAY*. Identify which convention governs the requirement, and preserve its intended force4.
YANG is a language for describing network equipment configuration and state data. The current IETF guidance for documents containing YANG data models is RFC 9907, which superseded RFC 8407 in March 2026. It invokes BCP 14 for those documents. That is an example of a convention being stated for a specific type of document; BCP 14 does not automatically apply to every engineering document5.
Choose terms for the system
Terminology changes need the same care. There is no universal replacement: choose terms that describe the actual roles. For a bus transaction, *initiator* and *target* may fit when one component starts the transaction and another receives it. Check the applicable standard and interface documentation, and preserve enough context for readers to find older names6.
This is about shared engineering terminology; some adults choose “master” and “slave” for consensual, negotiated relationships, which is a different context7.
Technical documents should avoid irrelevant assumptions about a reader’s gender, sexuality, pronouns, partners, or family. Where personal details matter, use the name and pronouns a person gives you. A terminology change still needs to preserve the defined meaning of a technical term. Current RFC Editor and IETF authoring guidance separately encourages inclusive language; it is guidance for authors, not an inclusive-language requirement in ASD-STE100 or RFC 99078.
The guidance points to NISTIR 8366, which NIST now lists as withdrawn (20 February 2025)9.
Keep claims tied to evidence
These are my editorial rules, separate from ASD-STE100. I keep documented facts, my recollection, inference, and proposed wording distinct. If a measurement record or source is missing, I say so instead of filling the gap with a plausible detail. A confident draft does not turn an unverified statement into evidence.
Describe engineering work precisely
I start with the actual problem or observation, then explain what I tried, why I chose that approach, and what happened. I include the relevant constraints and trade-offs, and use first person only for work I personally did. I also distinguish work that was designed, implemented, tested, or validated; those words describe different stages. If the evidence does not establish a result or my contribution, I leave that point open.
The Engineering Council and Royal Academy of Engineering’s Statement of Ethical Principles includes critical thinking, evidence, communicating uncertainty, inclusive outcomes, and responsibility for the effects of emerging technologies such as AI10.
I’ve also questioned whether the Engineering Council is a good ethics gatekeeper. The IET Rules of Conduct also place responsibility for professional decisions and actions on the individual member11.
These are useful principles when deciding how much trust to place in a technical document, or in a tool that helped write it.
For a procedure, check the action against the equipment and the requirement as well as checking the wording.
- ASD-STE100 Issue 9, Parts 1 and 2.
- ASD-STE100 Issue 9, Part 1, Rule 1.14.
- RFC 2119 and RFC 8174, which together define BCP 14.
- ASD-STE100 Issue 9, Part 2 entries for *can*, *may*, *must*, *shall*, and *should*.
- RFC 7950 defines YANG. RFC 9907 is the current guidance and obsoletes RFC 8407.
- John Blyler, “What Is the Best Way to Purge Master and Slave Terms From Engineering Documents?”, *Design News*, 25 May 2021. This is an example of context-dependent terminology, not authority for current interface names.
- The UK Kink Guide: Master/slave dynamic, describing that distinct consensual, negotiated personal context.
- RFC Editor Style Guide and IETF Internet-Draft Author Resources: Language and style.
- NISTIR 8366, *Guidance for NIST Staff on Using Inclusive Language in Documentary Standards*; NIST lists it as withdrawn.
- Engineering Council and Royal Academy of Engineering, Statement of Ethical Principles.
- IET Rules of Conduct.