← All guides
Writing8 min read

How to Proofread Your Own Writing

A flat illustration of a document page with grey lines of text, one line marked with an orange insertion caret, an orange ring around a typo, and a blue magnifying glass resting over the page.

You have read your essay four times and it looks clean. You submit it. An hour later you open it again and there it is in the first line: a word you typed twice, or a their that should have been there. Proofreading your own writing is genuinely hard, and not because you are careless. This guide explains why your own mistakes hide from you, and gives you a set of passes that drag them back into view.

Why your own typos are invisible to you

When you read someone else's writing, you process the actual words on the page. When you read your own, your brain does something different: it plays back what you meant to write. You already know what the sentence is supposed to say, so you see the intended version rather than the one you actually typed. This effect is strongest right after you finish, when your memory of the intended sentence is freshest.

That is why the mistakes you miss are almost never random. They are missing small words like the, a, and of, doubled words at a line break, and the wrong half of a homophone pair. Your eye supplies the missing word and quietly corrects the wrong one, because it knows what belongs there.

Everything below is really one idea in different clothes: make the text look unfamiliar enough that you read what is on the page instead of what is in your head.

Separate proofreading from editing

Editing and proofreading are two different jobs, and trying to do both at once is a big reason proofreading fails. Editing is about ideas, structure, and clarity: does the argument hold, is the paragraph in the right place, is this sentence saying what I mean. Proofreading is the last pass, and it is about surface errors only: spelling, punctuation, agreement, typos.

Finish the editing first. If you are still moving paragraphs around, there is no point proofreading, because you will only rewrite the sentences you just cleaned. Proofread when the content is settled and you are no longer going to change what it says, only how correctly it says it.

Put time between writing and reading

The single most effective thing you can do is wait. The pull of the intended sentence fades as your memory of it fades, so a draft you proofread the next morning is one you read much closer to how a stranger would. If you have a day, use it. If you only have twenty minutes, use those: even a short break away from the screen resets your eye more than you would expect.

Change how the text looks

You wrote the draft in one font, at one size, on one screen, and your brain has memorised that picture. Break the picture and the words become new again. Any of these helps, and doing more than one helps more:

Read it aloud, or have it read to you

Reading aloud forces you to process every word, because your voice cannot skip ahead the way your eyes can. You will hear the missing word, the sentence that runs out of breath, the comma that should have been a full stop. Read slowly, and read exactly what is printed, not what you meant to print.

Better still, have the computer read it to you. Most phones and browsers have a read-aloud feature. A synthetic voice reads precisely what is on the page with no idea what you intended, so a dropped word becomes an audible stumble. It is also the most reliable way to catch a sentence you never actually finished.

Hunt one kind of error at a time

Trying to catch everything in a single read means you catch less of everything, because attention is a spotlight, not a floodlight. Do several quick passes, each looking for one thing:

Know your own repeat offenders

Everyone has a small set of mistakes they make again and again. Once you know yours, you can hunt them directly: keep a short list at the top of your checklist and search the document for each one. Common ones worth checking:

Where spellcheck and tools help, and where they do not

The spellchecker built into your editor catches words that are not words. It will not catch a real word used wrongly: form when you meant from, or a their that should be there, are all spelled correctly, so they sail straight through. That is exactly the category your own eye misses too, which is the worst possible overlap.

A dedicated proofreading tool goes further, because it reads grammar and usage rather than just spelling, so it can flag the wrong-word and agreement errors that slip past both you and a basic spellchecker. Use one as a genuine second pair of eyes, but keep the final decision yourself. A tool does not know you named a character Sam on purpose, and it will occasionally suggest a change that is wrong for your sentence. Read every suggestion and accept only the ones that are right.

If most of your writing happens inside a browser, in email, a discussion board, or a document editor, a browser extension that checks the text where you wrote it removes the copy-paste round trip and makes the second pass something you will actually do. The point of any tool is the same: it catches a different set of errors than you do, so the two of you together miss far less than either alone.

A checklist you can reuse

Keep this at the top of your notes and run it on every final draft:

None of this makes proofreading glamorous. It stays the least exciting part of writing. But it is the part a reader notices first when it is missing, and getting it right is almost entirely a matter of method rather than talent. Follow the passes, trust the checklist, and the errors that used to survive to the final version stop making it that far.

Read nextHow to Improve the Readability of Your Writing (Without Dumbing It Down)A practical guide to making academic writing easier to read: what a reading level really measures, how to fix the sentences that drag it up, and how to keep your meaning while losing the fog.

Do your own careful pass first, then run the draft through the free proofreader to catch what your eye slid past. It shows you each fix and what changed, so the final call stays yours.

Proofreader

More guides