Latest
What You Have to Decide Before Anybody WritesWriting It Before You Need ItCross Training Covered Everything Except the Role That Mattered MostBehind the Book: You Don’t Own Anything AnymoreBehind the Book: The Woke VirusBehind the Book: Galactic InvasionWhat’s New at The Writing King: Week of November 8, 2026Alexander Zhidkov: Decision MakingJessi Szurek: Expand Your RangeYou Don’t Own Anything AnymoreThe Budget Decided How My Department Was ShapedWhy Your Competitor’s Book Is Working and Yours Would NotWhy Are These Guys Smiling? A Business Book That Became a Wrestling MemoirPangram Wants to Decide Who Gets PublishedWhat You Have Enough Material For Right NowWhen a Book Is the Wrong ToolThe Woke VirusGalactic InvasionChatGPT Turns Four: From a Free Research Preview to GPT-6What’s New at The Writing King: Week of November 1, 2026Diwali: The Festival of Lights and the Story Behind the LampsHow Much Water and Power Does Heavy AI Use Take? I Ran My Own NumbersBad Boys: Ride or Die (2024)Vesuvius Day: The Teenager Who Wrote Down Pompeii’s Last DayAnti-Communism Week: Remembering the Writers Communism SilencedVoyager 1 One Light-Day: Fifty Years to Travel One Day of LightVellum Added an Optional AI Feature. A Pile-On Killed It in a Day.Are AI Subscriptions Losing Money? The Gym Membership Math Says NoAI Terms Every Writer Should Know, and Why Each One MattersWorking While Sick: What 24/7 On Call Cost MeHe Banned AI From His Writing Group. His Own Cover Got Called AI Slop.Who Writes the Fake Fan Mail Authors Get? Inside the Scam CompoundsSMS Appointment RemindersJoe Rockey: Ghostwriting His BookDarrell Stern: Stop Being Invisible, Become UnmissableFree BooksHow to Turn Your Expertise Into a Book People Want to Read | The Expert MethodWhat’s New at The Writing King: Week of October 25, 2026Challenger Remembrance Day: The Engineer Who Wouldn’t SignJoel Salomon: The Truth About MoneyReddit Is Putting Up a Login Wall. Wikipedia Won’t Be Far Behind.Victoria Chemko: The Body Is the First TechnologySir Patrick Stewart: A TributeA Year in the Bank: ADHD, Face Blindness and the Freedom to Walk Out | The Impossible Puzzles Show, Episode 326A Yale Economist Says We Won’t Be Missed. He Forgot the Bread Line.Walter Koenig: A TributeAI Has Paid Off Outside Tech. Apollo Is Reading the Wrong Scoreboard.I Don’t Post Bad ARC Reviews. I Send the Author a Note.The Little Red Book of Stuff That Works!Your Kids Are Your Own Fault
The Writing King Your Ethical Ghostwriter. Your Story, Done Right.

National Proofreading Day: Proofreading Is More Than Grammar

TL;DR: National Proofreading Day is March 8, created in 2011 to promote error-free writing. But real proofreading is bigger than catching typos. The dangerous errors are paragraphs in the wrong order, scenes that say the wrong thing, and characters who change eye color halfway through the book. Here’s the history, my three-pass method, and the simple log that keeps a whole book consistent.

A Day for Catching Mistakes

A woman started National Proofreading Day to honor her mother, who loved correcting people. That’s the most relatable origin story for a writing holiday I’ve ever heard.
Share on X

National Proofreading Day is March 8. It was created in 2011 by a corporate trainer named Judy Beaver, in honor of her mother Flo, who loved to correct people. Beaver picked March 8 because it was her mother’s birthday. That makes it the perfect day to go correcting errors. It’s a great origin story. We all know a Flo.

The day exists to promote a simple, unglamorous, essential habit: review your writing before you send it or publish it. Even the best writers make typos and slips, especially when moving fast.

Proofreading is the step that catches them. But here’s where I part ways with the usual advice, because most people think proofreading means hunting for spelling and grammar errors, and that’s only the smallest part of the job.

Watch: How to proofread your own writing like a pro | Best proofreading tips and strategies, Smart Student

Proofreading Is About More Than Grammar

The typos are the easy part. The errors that wreck a book are bigger: paragraphs out of order, a scene that says the wrong thing, a character whose eyes change color in chapter nine. Proofread for those.
Share on X

When I proofread a book, I’m checking for far more than grammar, spelling, and punctuation. Those matter, and you should fix them. But the errors that damage a book are contextual, and you’ll never catch them with a spell checker.

I read for whether the content itself is right. Are these paragraphs in the correct order, or did I write something out of sequence? Are they saying the right things, making the point I meant to make?

And the big one, especially in a long book, are the characters consistent all the way through? Is the woman I described as tall with blonde hair and blue eyes in chapter two still tall with blonde hair and blue eyes in chapter twenty?

Does a character who hates coffee in the first act suddenly order an espresso in the third? This is proofreading at the level of meaning and continuity, and it’s more important than any comma.

That’s the heart of it. Standard proofreading checks whether your document follows the rules of grammar. Real proofreading checks whether your document follows the rules of what you’re writing about. A book has an internal logic, a set of facts it establishes about its own world and people, and those facts have to stay consistent. Breaking them is worse than a typo, because it pulls the reader out of the story and makes them stop trusting you.

What real proofreading checks, from surface to meaning
Layer What to check Example from the page
Surface Grammar, spelling and punctuation Typos and slips made while moving fast
Structure Paragraphs in the correct order Something written out of sequence
Sense The content says the right things Making the point you meant to make
Consistency Characters stay the same all the way through Tall, blonde and blue eyed in chapter two and chapter twenty
Consistency Traits and habits hold A coffee hater orders an espresso in the third act

What is a three-pass proofreading method?

My proofreading method: read it the day I write it, read it again the next day, then read it once more a week later. Distance is the tool. Fresh eyes see what tired eyes wrote past.
Share on X

When I proofread, I rely on one thing above all: distance.

I read a piece right after I write it. That catches the obvious stuff. Then I read it again the next day, after a night has passed, and that’s where most of the real corrections happen. A night of distance lets you read what’s on the page instead of what you meant to write, because when writing is fresh your brain fills in the gaps and hides the errors from you.

Then, for a book, I read it again about a week later, to make sure it’s right with fresh eyes.

Three passes, spread out over time. The spacing is the trick. If you write something and proofread it five minutes later, you’ll miss half the mistakes, because you’re still too close to it. Let it cool. Come back as a stranger. The errors that were invisible an hour ago will jump off the page a day later. This is the same reason I always write one day and proofread the next instead of doing both in one sitting.

A few concrete tricks make those passes sharper. Read the work out loud, because your ear catches clumsy sentences and missing words that your eye slides right over. Read a section backward, sentence by sentence, when you’re hunting pure typos, because it breaks the flow that lets your brain autocorrect. And check for one kind of error at a time, one pass for spelling, one for punctuation, one for consistency, instead of trying to catch everything at once. Splitting the job makes each pass more focused and more honest.

Three Proofreading Passes, Spread Over TimeRichard's three pass proofreading method laid out over time. The first read comes right after writing, the second the next day, and for a book a third about a week later. After self review the work goes to a second set of eyes.Three Proofreading Passes, Spread Over TimeDistance is the toolSame dayFirst readCatches the obvious stuff.Next daySecond readWhere most real corrections happen.A week laterThird readFor a book, fresh eyes.ThenHand it offA second set of eyes catches the rest.
Three Proofreading Passes, Spread Over TimeRichard's three pass proofreading method laid out over time. The first read comes right after writing, the second the next day, and for a book a third about a week later. After self review the work goes to a second set of eyes.Three Proofreading Passes, SpreadOver TimeDistance is the toolSame dayFirst readCatches the obvious stuff.Next daySecond readWhere most real corrections happen.A week laterThird readFor a book, fresh eyes.ThenHand it offA second set of eyes catches the rest.

Each pass is spaced out so you read what is on the page, not what you meant to write.

The Log That Keeps a Book Consistent

For catching the consistency errors, the contextual ones, you can’t rely on memory. You need a system, and mine is simple.

I keep a log. Character sheets. As I write a book, I grab a piece of paper or open a spreadsheet, and I write down the details as I create them. This character is blonde, blue eyes, six feet tall, has these traits, this background, this way of speaking. Then as I keep writing, I reference that sheet and add to it, checking each character against what I already established and filling in new details as they appear. It’s a living record of every fact the book has committed to.

Why bother? Because humans drift. We drift exactly the way AI drifts, especially over long periods. When you write a book over months, you won’t remember that you gave a minor character green eyes in chapter three, and you’ll absentmindedly give him brown ones in chapter eighteen. That’s just how memory works across a long project. The log is what protects you from your own drift.

It’s the difference between a book that feels solid and consistent and one that contradicts itself and loses the reader’s trust.

What This Means for Writers

The lesson of Proofreading Day, for anyone serious about writing, is to expand your definition of the word.

Proofreading is a layered review of your whole work. There’s the surface layer, grammar and spelling and punctuation. That matters and which a tool can help with. And there’s the deeper layer, structure and sense and consistency, which no tool can do for you, because it requires understanding what your book is trying to be. That deeper layer is where good writing is protected or lost.

So build the habit. Read your work more than once, with time in between. Keep a log of the facts your book establishes, and hold every page to them. Check whether the sentence is correct and whether it’s the right sentence, in the right place, saying the right thing, about characters who are still themselves. That’s real proofreading, and it’s one of the things that separates a finished book from a polished one.

One more thing, and it’s the part of this most writers skip.

Proofread your own work hard, every pass I described, but then hand it to someone else. You can’t fully proofread your own writing, because you know what it’s supposed to say and your brain supplies it automatically. A second set of eyes catches what yours never will. For my nonfiction, my go-to editor is Jennifer, and she finds things I’d swear weren’t there. Self-review gets you most of the way.

A real editor gets you the rest. If you’re serious about a book, budget for both.

So on March 8, don’t just run spell check and call it done. Pick something you wrote, read it slowly with fresh eyes, and look for the errors a machine would never find. Flo would approve.

National Proofreading Day FAQ

When is National Proofreading Day?
March 8 every year. It was created in 2011 by corporate trainer Judy Beaver in honor of her mother Flo, who loved correcting people. March 8 was Flo’s birthday.
What is the difference between proofreading and editing?
Proofreading is often thought of as catching surface errors like typos and grammar, while editing addresses deeper issues. But strong proofreading should include contextual checks too, whether paragraphs are in the right order, whether the content says what it should, and whether characters and facts stay consistent across the whole work.
What is the best way to proofread a book?
Use distance. Read it right after writing, again the next day after a night has passed, and once more about a week later with fresh eyes. Each pass catches what the last one missed, because the more time between writing and reading, the more clearly you see what’s on the page.
How do you keep characters consistent in a long book?
Keep a log or character sheets. Record each character’s details as you create them, such as appearance, traits, and background, in a notebook or spreadsheet, then reference and update it as you write. Humans drift over long projects, and a written record protects you from contradicting yourself.
Can software proofread for you?
Software can help with the surface layer, grammar, spelling, and punctuation. But it can’t check the deeper layer of structure, sense, and consistency, because that requires understanding what your book is trying to be. The most damaging errors are contextual, and those still require a human reader.

0 comments

No comments yet. Yours can be the first.

Was this useful?

Leave a comment