Technical Writing Style and Tone 2 — Questions and Answers
Question 1: What is nominalization in technical writing?
- Turning verbs into nouns (Correct answer)
- Using numbers as adjectives
- Naming variables
- Capitalizing nouns
Correct answer: Turning verbs into nouns
Nominalization (e.g., 'make a decision' instead of 'decide') weakens clarity and should be minimized.
Question 2: Which term describes unnecessary words that add length without meaning?
- Deadwood (Correct answer)
- Jargon
- Acronyms
- Hedging
Correct answer: Deadwood
Deadwood refers to filler words or phrases that clutter technical writing without adding value.
Question 3: What is the recommended sentence length for clear US technical writing?
- 15–20 words on average (Correct answer)
- 30–40 words on average
- 50+ words on average
- Exactly 10 words
Correct answer: 15–20 words on average
Sentences averaging 15–20 words are easier for readers to process in technical contexts.
Question 4: Which style guide is most commonly used in US software documentation?
- Microsoft Writing Style Guide (Correct answer)
- Oxford Style Manual
- AP Stylebook
- Strunk & White
Correct answer: Microsoft Writing Style Guide
The Microsoft Writing Style Guide is the dominant reference for US software and tech product documentation.
Question 5: What does 'hedging language' mean in technical writing?
- Vague language that avoids commitment (Correct answer)
- Specific numbered data
- Bold claims
- Legal disclaimers
Correct answer: Vague language that avoids commitment
Hedging language uses words like 'may,' 'might,' or 'could' to weaken statements unnecessarily.
Question 6: When writing error messages in US software documentation, which tone is recommended?
- Helpful and non-blaming (Correct answer)
- Apologetic and formal
- Technical and complex
- Casual and humorous
Correct answer: Helpful and non-blaming
Error messages should be constructive and non-blaming, guiding the user to a solution without frustration.
What is nominalization in technical writing?