A Day for Catching Mistakes
National Proofreading Day was started by a woman to honor her mother, who loved correcting people. That is the most relatable origin story for a writing holiday I have 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, which makes it the perfect day to go correcting errors. I love that 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 is where I part ways with the usual advice, because most people think proofreading means hunting for spelling and grammar errors, and that is only the smallest part of the job.
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 am checking for far more than grammar, spelling, and punctuation. Those matter, and you should fix them. But the errors that actually damage a book are contextual, and you will 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 actually 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 is more important than any comma.
That is 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 are 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 quietly is worse than a typo, because it pulls the reader out of the story and makes them stop trusting you.
My Three-Pass 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
Here is how I actually do it, and it relies on one thing above all: distance.
I read a piece right after I write it, which catches the obvious stuff. Then I read it again the next day, after a night has passed, which is where most of the real corrections happen. A night of distance lets you read what is actually 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 is genuinely right with truly fresh eyes.
Three passes, spread out over time. The spacing is the whole trick. If you write something and proofread it five minutes later, you will miss half the mistakes, because you are 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 rather than 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 are 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.
The Log That Keeps a Book Consistent
For catching the consistency errors, the contextual ones, you cannot 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 is 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 will not remember that you gave a minor character green eyes in chapter three, and you will absentmindedly give him brown ones in chapter eighteen. It is not carelessness, it is just how memory works across a long project. The log is what protects you from your own drift. It is the difference between a book that feels solid and consistent and one that quietly contradicts itself and loses the reader’s trust.
What This Means for Writers
The real lesson of Proofreading Day, for anyone serious about writing, is to expand your definition of the word.
Proofreading is not a janitorial task you do at the end to sweep up typos. It is a layered review of your whole work. There is the surface layer, grammar and spelling and punctuation, which matters and which a tool can help with. And there is the deeper layer, structure and sense and consistency, which no tool can do for you, because it requires actually 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 not just whether the sentence is correct, but whether it is the right sentence, in the right place, saying the right thing, about characters who are still themselves. That is real proofreading, and it is one of the things that separates a finished book from a polished one.
One more thing, and it is the part of this most writers skip. Proofread your own work hard, every pass I described, but then hand it to someone else. You cannot fully proofread your own writing, because you know what it is supposed to say and your brain quietly supplies it. A second set of eyes catches what yours never will. For my nonfiction, my go-to editor is Jennifer, and she finds things I would swear were not there. Self-review gets you most of the way. A real editor gets you the rest. If you are serious about a book, budget for both.
So on March 8, do not 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.