Technical Writing Writing Process 2 — Questions and Answers
Question 1: What is the difference between editing and proofreading?
- Editing addresses content and structure; proofreading catches surface errors (Correct answer)
- They are the same
- Proofreading changes meaning
- Editing only fixes spelling
Correct answer: Editing addresses content and structure; proofreading catches surface errors
Editing improves clarity, organization, and completeness, while proofreading catches typos, punctuation, and formatting errors.
Question 2: What is a content audit in technical writing?
- Systematic review of existing documentation to assess accuracy and gaps (Correct answer)
- A grammar check tool
- A publishing checklist
- A style guide
Correct answer: Systematic review of existing documentation to assess accuracy and gaps
A content audit evaluates existing docs for accuracy, completeness, relevance, and alignment with current product features.
Question 3: Which tool type do technical writers use to manage structured content reuse?
- Component Content Management System (CCMS) (Correct answer)
- Word processor
- Email client
- Version control only
Correct answer: Component Content Management System (CCMS)
A CCMS stores content as reusable components that can be assembled into multiple deliverables, enabling single-sourcing.
Question 4: What is the purpose of a writing template in technical documentation?
- Provide a consistent structure for a recurring document type (Correct answer)
- Replace the need for editing
- Automatically generate content
- Check for broken links
Correct answer: Provide a consistent structure for a recurring document type
Templates standardize structure and formatting so writers can focus on content rather than document design each time.
Question 5: At what stage should usability testing of documentation occur?
- Before final publication, ideally with real users (Correct answer)
- Only after publication
- During initial planning
- It is not necessary
Correct answer: Before final publication, ideally with real users
Usability testing with real users before publication reveals where documentation fails to meet user needs.
Question 6: What does version control for documentation help teams do?
- Track changes, collaborate, and revert to previous versions (Correct answer)
- Publish automatically
- Check grammar
- Generate PDFs
Correct answer: Track changes, collaborate, and revert to previous versions
Version control (e.g., Git) lets documentation teams track revisions, manage contributions, and recover previous document states.
What is the difference between editing and proofreading?