Technical Writing Rules 5 — Questions and Answers
Question 1: What rule governs heading levels in a technical document?
- Use as many heading levels as needed to organize the content
- Limit heading levels to a maximum of three or four to avoid disorienting readers (Correct answer)
- Use only one heading level throughout a document for consistency
- Headings should never contain verbs or questions
Correct answer: Limit heading levels to a maximum of three or four to avoid disorienting readers
Most style guides recommend no more than three to four heading levels because deeper nesting confuses readers about document structure.
Question 2: The rule of 'chunking' in technical writing means:
- Breaking large files into smaller downloadable pieces
- Grouping related information together into discrete, labeled sections (Correct answer)
- Removing redundant content to reduce word count
- Writing each paragraph as a standalone unit without cross-references
Correct answer: Grouping related information together into discrete, labeled sections
Chunking organizes content into labeled groups so readers can scan, locate, and process related information efficiently.
Question 3: Which rule applies to the use of contractions in technical documentation?
- Contractions are always forbidden in technical writing
- Contractions may be used to create a friendly tone when the audience and context allow (Correct answer)
- Contractions are required in user-facing help content per plain language rules
- Contractions are acceptable only in captions and callouts
Correct answer: Contractions may be used to create a friendly tone when the audience and context allow
Contractions are permitted—and even encouraged by plain language guidelines—in user-facing documents where a conversational tone aids comprehension.
Question 4: What is the rule for hyphenating compound modifiers in technical writing?
- Always hyphenate compound modifiers regardless of position
- Hyphenate compound modifiers before a noun but not after a linking verb (Correct answer)
- Never hyphenate compound modifiers in technical documents
- Hyphenate only when the modifier contains a number
Correct answer: Hyphenate compound modifiers before a noun but not after a linking verb
Compound modifiers are hyphenated before a noun (e.g., 'high-voltage cable') but not when they follow a linking verb (e.g., 'the cable is high voltage').
Question 5: According to readability rules, what is the recommended maximum sentence length in technical prose?
- No more than 10 words per sentence
- No more than 20–25 words per sentence on average (Correct answer)
- No more than 50 words per sentence
- Sentence length has no bearing on technical readability
Correct answer: No more than 20–25 words per sentence on average
Plain language and readability research recommend averaging 20–25 words per sentence to maintain comprehension, especially for non-expert readers.
Question 6: The 'one idea per paragraph' rule in technical writing is intended to:
- Keep all paragraphs exactly the same length
- Help readers identify and process individual concepts without confusion (Correct answer)
- Eliminate the need for transitional sentences
- Ensure documents meet minimum page count requirements
Correct answer: Help readers identify and process individual concepts without confusion
Limiting each paragraph to one main idea makes the document easier to scan, understand, and reference.
Question 7: Which rule describes when a table is preferred over a list in technical documentation?
- Tables are always preferred over lists because they look more professional
- Use a table when comparing multiple attributes across two or more items (Correct answer)
- Use a table only when data contains numerical values
- Tables replace lists whenever there are more than five items
Correct answer: Use a table when comparing multiple attributes across two or more items
Tables excel at showing relationships between items across multiple attributes; lists are better for single-attribute sequences or items.
What rule governs heading levels in a technical document?