Quiz — Chapter 12: Editing and Revision

Target: 70%+ before moving on. Answers and explanations are hidden — try each question before expanding.

Section 1 — Multiple Choice

Q1. Three activities get lumped under "editing." Which one changes what you say and the order you say it in? A. Proofreading B. Copyediting C. Revision D. Line editing

Answer **C.** Revision — literally *re-vision*, seeing again — is the big stuff: content and structure, what you say and the order you say it in (§12.1). Proofreading (A) catches surface errors; line editing (D) and copyediting (B) sharpen sentences and words. Mixing the three is exactly what produces a clean-but-mediocre document.

Q2. What is the correct order of the six-level editing hierarchy, top to bottom? A. Proofreading → words → sentences → paragraphs → structure → content B. Content → structure → paragraphs → sentences → words → proofreading C. Structure → content → sentences → paragraphs → proofreading → words D. Content → sentences → words → structure → paragraphs → proofreading

Answer **B.** The hierarchy descends from largest scope to smallest: content → structure → paragraphs → sentences → words → proofreading (§12.2). A is the hierarchy upside-down — starting at the bottom, which guarantees rework. C and D scramble the levels. The rule is absolute: descend the ladder; never start at the bottom.

Q3. Why does working top-down save effort rather than just reorganizing it? A. Higher levels are easier than lower levels B. A change at any level can delete or invalidate the work below it, so settling high levels first means you never polish text that won't survive C. Spell-check works better on a finished structure D. It lets you skip the lower levels entirely

Answer **B.** The whole argument: cut a section and its perfectly-edited sentences vanish with it; reorder the structure and beautifully-flowing paragraphs now jar (§12.2). Top-down means your scarce sentence-attention is spent only on survivors. A is false (top levels are often harder). C is trivial and not the reason. D is wrong — you do every level, just in order; you're refusing to do the lower work *twice*.

Q4. In §12.3, after the structure pass, Priya Sharma's memo was deliberately left "clunky and slightly redundant." Why not smooth it immediately? A. Because the memo was already good enough B. Because smoothing is level 4–5 work, and the structure (level 2) wasn't yet final — polishing might polish a sentence about to move or be cut C. Because redundancy is good for emphasis D. Because the director preferred rough drafts

Answer **B.** Smoothing prose is sentence-and-word work; doing it before the structure is committed risks the exact rework the hierarchy exists to prevent (§12.3). The temporary redundancy (the decline mentioned twice) is a normal artifact of moving content around, resolved cleanly in the later passes. A, C, and D misread the point: letting a draft be temporarily ugly is the *price* of not doing work twice.

Q5. Which self-editing technique is described as the single most effective, costing "nothing but planning"? A. Reading backwards sentence by sentence B. Changing the font C. The 24-hour gap (letting the draft go cold) D. Hunting one error type at a time

Answer **C.** The 24-hour gap converts you from the document's author (who reads intention) into its first real reader (who reads the page) (§12.4). Nothing about your skill changes overnight — your *relationship to the draft* changes. A, B, and D are all useful techniques, but the gap is the highest-yield, and it's free if you schedule for it.

Q6. Reading backwards, sentence by sentence, is best reserved for the bottom of the hierarchy because it: A. Is faster than reading forwards B. Deliberately destroys narrative flow, which makes it useless for checking logic but ideal for inspecting each sentence in isolation C. Catches structural problems better than reading aloud D. Is the only way to find typos

Answer **B.** Stripping the flow is the whole mechanism: it stops your brain autocompleting, so each sentence stands alone for clarity and surface errors (§12.4). That same destruction of sequence makes it *poor* for logic and structure (C is backwards) — which is why it belongs at the last rung, where logic is already settled. A is irrelevant; D overstates (reading aloud and format changes also find typos).

Q7. A reviewer returns a draft whose recommendation is buried in the last paragraph — but spends all their comments on commas and word choice. Which feedback rule did they violate most? A. Be kind B. Be specific C. Lead with the level — respect the hierarchy on someone else's draft too D. Say thank you

Answer **C.** Nothing wastes a writer's time like thirty grammar nits and no comment that the whole thing is in the wrong order (§12.5, Rule 1). The highest-level problem (structure) must be diagnosed and stated first. The comma comments may even be moot if paragraphs move. A and D are about receiving or tone; B (specific) they arguably *were* — about the wrong things.

Q8. "I had to read this paragraph twice to figure out the main point." Why is this better feedback than "This paragraph is bad"? A. It's longer B. It reports the effect on the reader as data the writer can act on, rather than a verdict they can only accept or resist C. It's kinder in tone D. It avoids naming the problem

Answer **B.** "This paragraph is bad" is a judgment; "I had to read it twice" reports what happened in a reader's head — information the writer can't argue with and *can* act on (§12.5, Rule 3). The most useful feedback often takes the form "As a reader, I [did X / felt Y]." A is irrelevant; C is incidental; D is false — it locates the problem precisely (the main point is hard to find).

Q9. When a reviewer says "I didn't understand this part," the worst response is to: A. Ask them to point to the exact spot B. Explain the part out loud, clearly and convincingly, to the reviewer C. Thank them and revise the passage D. Write the explanation into the document

Answer **B.** Of course you *can* explain it — you wrote it. But the reader won't have you standing next to them; if they didn't get it from the page, the *page* failed (§12.6). The verbal explanation is actually the raw material for the fix: write *that* into the document. A, C, and D are all good moves; B is the defensive trap that fixes nothing.

Q10. "Listen for the problem, not the prescription" means: A. Ignore all suggested fixes B. A reviewer is reliable at locating where a document fails but often wrong about how to fix it — take the diagnosis seriously, weigh the prescription C. Only accept feedback phrased as a question D. Reviewers should never suggest solutions

Answer **B.** A reviewer who says "add a summary table here" has noticed something real (they got lost) but their specific fix may not be right — maybe a topic sentence or a reorder serves better (§12.6). Hear the underlying problem; trust yourself on the solution. A is too extreme (you don't ignore fixes, you weigh them); C and D invent rules the chapter doesn't make.

Q11. The working answer to "how many passes is enough?" for anything that matters is: A. Exactly three, always B. At least two passes after the first draft — one global (content/structure) and one local (sentences/words/proof), with a gap between C. As many as possible, with no upper limit D. One careful read is sufficient for any document

Answer **B.** At least two genuine passes — one revision, one editing-plus-proofreading — with the cold gap between if possible (§12.7). One pass gambles; the second catches what the big fixes broke. A is too rigid (stakes scale the number). C ignores diminishing returns. D is the single-pass trap that buries points and misses typos even on short documents.

Q12. You're moving commas back and forth and swapping "however" for "but" and back again on a fourth pass. The chapter's test says you should: A. Keep going until it's perfect B. Stop — when edits stop changing meaning and start churning surface, you're done; ship it C. Start over from the first draft D. Add a fifth pass to be safe

Answer **B.** The diminishing-returns test: when your edits no longer change meaning and just churn surface, you're done (§12.7, §12.8 Mistake 4). Endless polishing is procrastination wearing a productive costume; perfect is the enemy of sent. A and D are the procrastination trap; C discards real progress.

Section 2 — True/False with Justification

State true or false and justify in one sentence.

Q13. If you fixed thirty typos and reworded a few sentences but never changed the content or structure, you revised the document.

Answer **False.** That's proofreading plus a little editing; revision changes *what you say* or *the order you say it in*, and none of that changed — the classic "clean but mediocre" result of mistaking proofreading for revision (§12.1).

Q14. For a two-paragraph email, you must run six literally separate read-throughs to honor the editing hierarchy.

Answer **False.** The discipline scales with stakes: for a short document the six levels collapse into one careful pass with the levels held in mind; the *order* never changes, but the *number* of dedicated passes flexes (§12.2, §12.7).

Q15. Reading aloud and reading backwards belong at the same rung of the editing hierarchy.

Answer **False.** Reading aloud works mid-ladder (sentences and paragraphs — flow, buried points, missing words); reading backwards belongs at the bottom (sentence editing and proofreading) because it *destroys* the flow that logic depends on (§12.4).

Q16. Receiving feedback well means taking every note the reviewer gives you.

Answer **False.** You're still the author and own the final call; the discipline is to *consider* every note seriously — assume the reader's reaction is real — and then choose, rejecting a note because you weighed it and disagree, not because it stung (§12.6).

Q17. The gap between passes matters as much as the number of passes.

Answer **True.** Three frantic passes in one hour are worth less than two passes with a night's sleep between them, because without the gap you're still reading your intention each time rather than the page (§12.7).

Q18. A throwaway Slack message deserves the full editing hierarchy, a 24-hour gap, and a peer-review round.

Answer **False.** Over-applying the machinery to throwaway text is its own mistake — wasted effort, the very thing the book argues against; the skill is *matching effort to stakes*, so a quick note gets one careful read, not a six-level descent (§12.8).

Section 3 — Short Answer

Two to four sentences each. Model answers and rubrics below.

Q19. Explain why you cannot revise and proofread well in the same pass.

Model answer + rubric The two jobs require opposite states of mind: revision is ruthless and reader-focused (you must be willing to delete things you were proud of), while proofreading is patient and literal (you must slow down and read what's actually on the page, letter by letter). You can't hold both at once — too attached to cut, too focused on meaning to see the typos. Separating the passes lets you bring the right mind to each. **Rubric:** names the opposing mindsets (1) and connects to *why* combining them fails at both (1).

Q20. Describe the 24-hour gap and explain the mechanism that makes it work.

Model answer + rubric After finishing a draft, you wait — ideally a day, even a few hours helps — before editing it. It works because when a draft is "hot," it's all still in your head, so you read your *intention* and can't see the gaps, and you're emotionally attached to sentences you just sweated over. The gap lets the intention fade and the attachment cool, so you return as a *different reader* who sees the page, not the plan. **Rubric:** states the technique (1) and explains the hot-vs-cold / intention-vs-page mechanism (1).

Q21. Give the five rules for giving feedback that actually helps (§12.5), in one phrase each.

Model answer + rubric (1) **Lead with the level** — diagnose the highest-level problem first, respect the hierarchy on someone else's draft too. (2) **Be specific** — name the place, name the problem, point at the text. (3) **Describe the effect on you as a reader** — report what happened in your head, not a verdict. (4) **Prioritize** — separate the few must-changes from the many could-improves. (5) **Be kind** — critique the writing, never the writer. **Rubric:** all five named (1 each, partial credit), phrased as the rule's substance not just a label.

Q22. Why is "if the reader didn't get it, the page failed" a more useful stance than "the reader didn't read carefully enough" — even when the reader genuinely was careless?

Model answer + rubric Because you can only control the document, not the reader. You can't ship a careful-reading guarantee alongside your report — every other reader arrives with the same haste, divided attention, and lack of your private context. Treating the confusion as a document problem makes the page more robust for *all* future readers, including the careful ones; blaming the reader fixes nothing and ships the same fragile document. **Rubric:** identifies "you control the document, not the reader" (1) and that fixing the page helps all future readers (1).

Section 4 — Applied Scenario

Q23. Below is the opening of a status memo. (a) Run a global pass only (content + structure): say what you'd cut, what you'd move, and why — don't fix any sentences. (b) Then name what you would deliberately ignore on this pass and which later level it belongs to.

"Over the past month the team has been investigating the intermittent
failures in the nightly batch job. We gathered logs from three
environments and interviewed two on-call engineers. We also briefly
looked at the reporting dashboard, which has some unrelated UI issues
we'll handle separately. After analysis, it is our determination that
the root cause is a connection-pool exhaustion that occurs under the
month-end load spike, and we recommend raising the pool ceiling and
adding back-pressure as the fix."
Answer + rubric (a) **Cut:** the dashboard/UI sentence — the writer says it's "unrelated" and "handled separately," so it's a tangent that dilutes the message (content). **Move:** the recommendation and root cause (the last sentence) to the *front* — it's what the reader most needs, and right now it's buried behind 60+ words of setup (structure; the buried-conclusion failure from [Ch 4](../../part-01-writing-is-thinking/chapter-04-structure/index.md)). A strong global pass yields something like: *"Recommendation first: raise the connection-pool ceiling and add back-pressure to fix the nightly batch failures, whose root cause is pool exhaustion under the month-end load spike. [Then the method/evidence.]"* (b) **Ignore on this pass:** "it is our determination that" (bloat — level 5, words), any sentence rhythm, and any typos (level 6). Those are local work; you fix them only after the structure is committed, on survivors. **Rubric:** cuts the tangent and moves the recommendation up with reasons (1); explicitly defers at least one sentence/word/proof item to its correct lower level (1).

Q24. A peer hands you the draft below and says "be honest." The argument is sound and well-ordered, but the second sentence is genuinely unclear and there are two comma splices. Write a short paragraph of feedback that follows the §12.5 rules.

"Migrating to the managed queue cut our on-call pages by 40%. The
thing that the change did, which was reduce the operational surface,
it meant fewer moving parts for the team to babysit overnight. We saw
the drop within two weeks, the trend has held for a quarter. I
recommend we migrate the remaining two services next."
Answer + rubric A strong answer leads with what *works* (true, and it tells the writer not to touch the parts already right), then addresses the highest-remaining problem — the unclear second sentence — specifically, and only then mentions the splices as a *category*: > *"The structure's great — the 40% headline leads, the evidence and recommendation follow cleanly, so don't touch that. One real snag: the second sentence ('The thing that the change did…') lost me — I think you mean 'the migration reduced the operational surface, so the team had fewer moving parts to babysit,' but as written I had to reread it. Fix that one first. After that, there's a recurring comma-splice pattern (two of them — sentence 3 joins two clauses with just a comma); you'll spot the rest once you're looking. Nice work overall."* **Rubric:** ✅ names what works (not flattery — actionable) ✅ leads with the meaning-level problem before the splices ✅ specific and text-anchored ✅ reports reader experience ("I had to reread it") ✅ groups the splices as a category, not two annotations ✅ kind. The trap is leading with the *visible* comma splices instead of the *important* unclear sentence — visible ≠ important.

Scoring & Next Steps

Score What it means Do this
< 50% The three-way distinction and the hierarchy aren't solid yet Re-read §12.1–§12.3 (the three jobs, the ladder, the descent). Redo Exercises Part A.
50–70% Concepts forming, application shaky Redo Exercises Part B (plan-the-passes, the buried recommendation) and re-read §12.4 (self-editing) and §12.7 (how many passes).
70–85% Solid — proceed Move to Chapter 13. Do the Project Checkpoint (the documented top-down revision) if you skipped it.
> 85% Strong command Try Exercises Part E (reverse-outline a published doc; build your personal revision signature). You're ready to revise for real.

The skill that matters most here isn't memorizing the six level names — it's the order (big before small, always) and the gap (going cold so you read the page, not your intention). If you nailed Q1, Q2, Q3, Q9, and the applied scenarios, you have the part that turns an adequate writer into an excellent one. Onward to Chapter 13: Lab and Technical Reports, where this revision workflow gets applied to the IMRaD structure — because from here on, no document is merely drafted.