§The situation
The OneVillage Client Catalog — Expert Seminars is a 29-slide, client-facing deck. Before it went back out, it needed two things: a clean proofread (typos, grammar, anything that reads as unprofessional) and a pagination check — the Table of Contents page numbers had drifted out of sync with the actual slides. Rather than squint through 29 slides by hand, the whole job was handed to Claude with a link to the live deck.
Claude found the root cause of the pagination drift, corrected the grammar and formatting itself, and — the important part — flagged the things it couldn't know (which presenter, which price) instead of guessing. It didn't stop at the words, either: it checked the visual layer too — whether every page number actually shows, and whether the logo is the right size and consistent on every slide (it turned out to be an oversized image copy-pasted onto ~25 separate slides) — and it read each section’s takeaways against that section’s own summary, catching one agenda that was generic, leftover boilerplate copied from a sibling slide. By the end the deck went from 29 to 27 clean slides. The edits below are the real before-and-afters from that session.
The one instruction that drove it all — “Review this document and edit in line to remove errors, typos, and anything else that would have it not be professional. Then make sure all of the pagination ties from the table of contents to the materials.”
§Six canonical rules this edit applied
1
Run everything through Claude before it leaves your hands. Internal or external, every time. Spell-check passes real words like include vs includes; Claude and a careful read do not.
2
Give Claude the real, current source. A link to the live document, not a stale paste. What Claude reads must be what your reader will see.
3
Ask for two passes, not one. First proofreading (typos, grammar, professionalism); then a consistency & QA pass — TOC vs sections, page numbers that actually show, names, prices, dates, and the visual layer (logo size and placement, nothing oversized or duplicated). Name the mismatch you already suspect.
4
Claude fixes the mechanics; you own the facts. Let it correct grammar and formatting directly. Anything that needs business knowledge — who presents, which price is right — it should flag for you, not decide.
5
Review before you accept. Read the change list. Approve the safe fixes; correct the ones only you know. Claude’s job is to surface, yours is to decide.
6
When you cut or change something, cascade it. Deleting a slide or section moves every page number after it. Tell Claude to carry the change all the way through the TOC.
§The edits — draft vs. final
1 Subject–verb agreement (a real-word error spell-check misses)
Draft“…whose skills includes developing high-performing teams…”
Final“…whose skills include developing high-performing teams…”
Why: “Includes” is a correctly spelled word, so a spell-checker sails right past it. Claude reads for sense, not just spelling, and catches the agreement error. This is exactly the class of mistake that survives a human skim on slide 6.
2 Missing word
Draft“…this seminar design to equip you…”
Final“…this seminar designed to equip you…”
Why: A dropped “-ed.” Small, but on a client-facing slide (16) it reads as careless. Claude flags it and fixes it in place.
3 TOC wording that didn’t match the slide
DraftSlide title: “Navigating Change With a Growth Mindset” / TOC: “…with…”
FinalTitle and TOC now read the same — “Navigating Change with a Growth Mindset.”
Why: The Table of Contents must mirror the slides exactly. Small inconsistencies (capitalization, a shortened title) make a document read as un-proofed. Same pass expanded “Empathy” → “Empathy in the Workplace” and “Stress Less: Transforming Mindsets” to match their slides.
4 Formatting consistency
DraftDouble hyphens -- used where the rest of the deck uses em dashes.
FinalStandardized to em dashes — deck-wide.
Why: Mixed punctuation is a tell that different people wrote different sections. One consistent style across the document looks deliberate and professional.
5 The pagination root cause
DraftOne seminar was missing from the TOC entirely, so every entry after it was numbered one page too low — e.g. “Collective Grief” listed on a page number that didn’t match its actual slide.
FinalAdded the missing line, renumbered the entries after it, and verified the TOC ties to every slide 4→29.
Why: The example you gave (“page 31 on the TOC, 28 in the document”) was the symptom; the missing entry was the cause. Claude traced the drift to its source instead of just nudging one number. When the map doesn’t match the territory, buyers stop trusting the document.
6 A judgment call Claude escalated instead of guessing
DraftSlide 29’s presenter was identical to slide 28’s — it looked like a copy-paste from the neighboring slide.
FinalClaude flagged it and asked. You decided: “Leave 24 as Barbara Walker” — a fact only you knew (Jenn was no longer with OneVillage).
Why: Presenter names, prices, and dates are facts, not typos. Claude corrects mechanics on its own but surfaces anything that needs your knowledge — so it never “fixes” something into being wrong. It also caught a live placeholder (“Host Name / bio”) and a registration link pointing at the wrong Calendly.
7 A change that cascaded
Draft“Delete grief informed workspace entirely, including from the TOC.”
FinalSlide removed; body page numbers auto-renumbered; the manual TOC line and its number column were fixed so nothing after it drifted.
Why: One deletion in the middle of a document moves everything below it. The edit isn’t done until the TOC and every downstream number reflect it. Claude checked whether the page numbers were auto-updating or manual before touching them.
8 Branding consistency — an oversized, duplicated logo
DraftThe white “OneVillage” wordmark was a separate image copy-pasted onto ~25 content slides (not on the slide master), and oversized at 1.99″ wide — slightly different on some slides.
FinalResized to 1.45″ (73%, aspect ratio locked), anchored bottom-right, and applied identically across all 25 slides.
Why: A logo that’s too big — or a different size slide to slide — reads as amateur on a client document. Because it lived as a per-slide image instead of on the master, every copy had to be fixed. The right workflow: resize one as a sample, confirm the size with the human, then replicate it exactly — so you don’t end up with 25 slides at the wrong size. (When branding is duplicated per-slide like this, it also belongs on the slide master so it’s edited once, not 25 times.)
9 Page numbers that actually show
DraftYou can’t assume every slide’s page number is visible — and a stray phantom “14” was floating in the TOC number column.
FinalVerified the number shows on every content slide and confirmed they’re auto-numbering placeholders that renumber themselves after a deletion; removed the phantom “14.”
Why: A TOC only ties to the materials if the page numbers actually appear on the slides — so check that they show, don’t assume. The good news here: because they were auto-numbering placeholders, deleting a slide renumbered the rest automatically; only the manual TOC column needed a human (or Claude) to fix.
10 Generic, leftover content that doesn’t describe its own page
Draft“Navigating Collective Grief” carried a generic group-session agenda — “Establishing a safe space / Exercise to center ourselves / Opportunities to share / A guided conversation” — the same boilerplate it had shared with the (since-deleted) “Group Grief” slide.
FinalClaude read each section’s takeaways against that section’s own summary — 23 of 24 matched; this one didn’t. Its summary promises a framework for collective grief, grounding techniques, and setting boundaries; the agenda reflected none of it. Flagged for a human to retailor rather than silently rewritten.
Why: Leftover boilerplate is the hardest error to catch — every word is spelled right and grammatical; it just describes the wrong thing. It shows up wherever content was copied (from a template or a sibling slide) and never customized. The test: read each section’s takeaways against that section’s own title and summary and ask — would these bullets fit any page, or only this one? If they’d fit anywhere, they’re generic and need rewriting. Because the fix is a content decision, Claude flags it (and can propose a retailored version) instead of guessing. Claude found this one.
§The prompts — copy, paste, adapt
This is the exact sequence that did the job. Swap in your own document link and the specific mismatch you suspect.
1. The master proofread + consistency prompt
Paste this with a link to the live document[paste the document link]
Review this document and edit in line to remove errors, typos, and
anything else that would have it not be professional.
Then go through and make sure all of the pagination ties from the
table of contents to the materials. For example, "Collective Grief"
is page 31 on the TOC and 28 in the actual document.
2. Let Claude make the edits directly
When you want the fixes applied, not just listedDrive my browser and make these changes:
[paste the document link]
3. Review, then approve the safe ones
After Claude shows its change listYes, do the minor fixes.
4. Correct what only you know (own the facts)
Claude flagged a name/price/date it can't verifyDon't replace 24 — leave it as Barbara Walker.
Jenn is no longer with OneVillage.
5. Make a change cascade
Cutting or moving something mid-documentDelete "Grief Informed Workspace" entirely, including from the TOC,
and renumber everything after it.
6. Check the visual layer, not just the words
Branding and page-number QANow check the visual layer: is the page number actually showing on
every slide, and is the logo the same size and position throughout?
Flag anything oversized, missing, or inconsistent before I send it.
One thing to watch: if other people are editing the same live file, Claude will flag the collaborator rather than overwrite their work — that’s what happened here when a teammate was fixing the TOC at the same moment. On a shared client master, either coordinate first or have Claude work from a copy.
§The pre-send check — make it a habit
Before it goes to anyone — internal or external
Ran the whole document through Claude before sending
Gave Claude the live/current file, not a stale copy
Asked for a proofreading pass: typos, grammar, homophones, tone
Asked for a consistency pass: TOC, page numbers, names, prices, dates
Every number in the TOC matches the actual page
Real-word errors checked (its/it’s, include/includes, design/designed)
Formatting consistent — em dashes, quotes, capitalization
No placeholder text or dead links left in (“Host Name,” wrong Calendly)
Every page number is actually visible on every page
Logo is the right size and consistent throughout — not oversized or duplicated slide-to-slide
Each section’s takeaways/agenda actually describe THAT page — no generic or leftover boilerplate copied from another item
Facts you own (names, titles, prices) verified by you, not guessed
Any cut or change cascaded through the TOC and page numbers
§The principle behind all of it
If it has your name on it, it has been through Claude first. Sending is the last step, not the first. Run the document through Claude, read what it found, fix the handful of things only you can, then send. The two minutes it takes is the cheapest insurance there is against a typo — or a wrong page number — reaching a client.
Now practice it. The drill quiz walks you through proofreading a document with Claude, deciding what to fix yourself, and cascading a change.
Go to the drill →