Considerate Language
Last edited on 28 Jan 2026
Use language that is inclusive, precise, and free from bias. Favor neutral, descriptive alternatives instead of idioms, metaphors, or phrases rooted in exclusion, ability, culture, gender, or violence.
This guidance is based on the Microsoft Style Guide’s recommendations for bias-free communication. When a term, phrase, or usage is not explicitly covered in our style guide, use the Microsoft guidance on ableist language, negative terms, gender-neutral language, and writing for a global audience as a secondary reference.
General Principles
Use considerate language to reduce unconscious bias and improve clarity across all documentation.
When writing:
- Prefer literal, descriptive wording over metaphors or idioms.
- Use language that is globally understandable and does not rely on cultural context.
- Avoid terms associated with violence, disability, gender, or historical oppression when neutral alternatives exist.
- Write in a straightforward, empathetic tone that is accessible to all readers.
Word Choices to Use and Avoid
Use neutral, descriptive alternatives in place of terms that may carry unintended or exclusionary connotations.
| Do use these words | Do not use these words |
|---|---|
| manufactured | manmade |
| personnel, staff | manpower |
| work-hours | man-hours |
| worker | workman / workwoman |
| humanity, human kind | mankind |
| allowlist / denylist | whitelist / blacklist |
| carried over | grandfathered in |
| main, primary, default | master |
| secondary, standby, replica | slave |
| high availability pair | master/slave pair |
| main branch, default branch | master branch |
| stop responding, terminate | kill |
| stop responding, freeze | hang |
| clear, understandable | dumbed down |
| straightforward, simple | dumb, lame |
| enter | type |
| limited functionality, partially supported | crippled |
| legacy, deprecated | old, obsolete |
| existing knowledge, internal documentation | tribal knowledge |
| send, forward, submit | shoot (an email) |
| check, verify, review | sanity check |
| were ignored, miss the mark | fall on deaf ears |
| weakness, something we overlooked | blind spot |
| extremely, very, unreasonable | crazy, insane |
| chair, chairperson | chairman |
| salesperson, representative | salesman |
| early opportunity, simple task | low-hanging fruit |
| system recovery | white knight |
Violent Metaphors
Avoid metaphors that reference physical harm or violence. For example, avoid phrases like “kill a process,” “shoot an email,” or “hang”.
Use neutral alternatives such as “terminate,” “send,” or “become unresponsive”.
Ableist Language
Avoid language that equates disability with error, limitation, or simplicity. For example, avoid terms such as “dumb,” “crippled,” or “lame”.
Use descriptive alternatives that focus on functionality or clarity.
Gendered Language
Avoid gendered job titles or honorifics. For example, use “chair” or “chairperson” instead of “chairman”.
Cultural Idioms
Avoid idioms and metaphors that may not translate well globally or may rely on cultural context. For example, avoid phrases like “low-hanging fruit,” “white knight,” or “hit the ground running”.
Use clear, literal descriptions instead.
Legacy and Technical Accuracy
If a product, open-source project, or codebase uses a historical or legacy term (for example, a Git repository whose canonical branch is still named master), retain the term only when technical accuracy requires it.
When doing so:
- Use the term factually and neutrally.
- Avoid reinforcing the metaphor or implying endorsement.
- Prefer updated terminology in all new content when possible.