Key Takeaways — Chapter 12: Editing and Revision
The one idea, if you remember nothing else: Revision is the work, not cleanup. A document becomes good in revision, not in the first draft. The gap between an adequate writer and an excellent one is not talent or grammar — it's whether they revise deliberately or just "fix it up."
"Editing" is really three jobs — done in this order
| Job | What it changes | When |
|---|---|---|
| Revision (re-vision, seeing again) | What you say and the order you say it in — content and structure | First |
| Editing (line editing / copyediting) | How each sentence and word reads | Second |
| Proofreading | The surface — typos, spelling, punctuation | Last |
Tangling them is why a clean document can still be mediocre. The three need opposite mindsets (ruthless vs. patient/literal), so you can't do them well in one pass.
The editing hierarchy is top-down
Content → Structure → Paragraphs → Sentences → Words → Proofreading.
Descend the ladder; never start at the bottom. A change at any level can delete the work below it — cut a section and its perfectly-edited sentences vanish with it; reorder the structure and beautifully-flowing paragraphs now jar. Top-down spends your scarce attention only on text that survives. You're not avoiding the sentence work; you're refusing to do it twice.
Let the draft be temporarily ugly between passes. Smoothing prose before the structure is final risks polishing a sentence you'll move or cut.
Self-editing fights the curse of knowledge
You read your intention, not your sentence. Every technique breaks that spell: - Read it aloud — your ear catches what your eye skips (mid-ladder). Where your mouth stumbles, the reader stumbles. - Read it backwards, sentence by sentence — destroys flow so each sentence stands alone (bottom rung: sentence + proof). - The 24-hour gap — the draft goes cold; you return as a stranger who reads the page. The single most effective technique, and it costs only planning. - Change the format (print it, change the font) and hunt one error type at a time.
Feedback: give it well, take it well
Giving (§12.5): lead with the highest level (respect the hierarchy on others' drafts too) · be specific, point at the text · report the effect on you as a reader ("I had to read this twice"), not a verdict ("this is bad") · prioritize · be kind — critique the writing, never the writer.
Receiving (§12.6): the note is about the document, not you · hear the problem, weigh the prescription · don't explain out loud — put the explanation in the document · you needn't take every note, but consider each seriously.
⚠️ The defensive tell: "Well, what I meant was…" — stop. Your intention is exactly what the reader can't see. Fix the page.
How many passes?
At least two after the first draft for anything that matters — one global (content/structure), one local (sentences/words/proof) — with a gap between (the gap matters as much as the count). Stakes scale it up; safety-critical gets independent review. Stop when edits stop changing meaning and start churning surface. Match effort to stakes — over-revising a throwaway note is its own mistake.