# Learning to Proof Read
**URL:** https://boards.straightdope.com/t/learning-to-proof-read/267834
**Category:** Factual Questions
**Created:** [October 6, 2004, 1:26pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834 "2004-10-06T13:26:27Z")
**Posts on this page:** 16
**Page:** 1
### Author:  [@Adoptamom\_II](https://boards.straightdope.com/u/Adoptamom_II)
#### Post date: [October 6, 2004, 1:26pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/1 "2004-10-06T13:26:27Z")
I need to learn to proof read my own typing. Currently, when I read over something I’ve typed, I “see” what is supposed to be there instead of what is actually typed on the page.
Suggestions?
---
### Author:  [@Jurph](https://boards.straightdope.com/u/Jurph)
#### Post date: [October 6, 2004, 1:32pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/2 "2004-10-06T13:32:20Z")
Practice proofreading (one word!) others’ work instead of your own, and have someone proofread your work as well. I wouldn’t even consider publishing an article before allowing at least two other people to read it, because even I have trouble seeing the faults in my own writing. One possible cure is to write your draft _very_ early, and set it aside for a few days. That way, when you come back to it, none of the substance remains in your immediate memory, and you can approach it as though it were not your own.
Like anything else, it takes practice. Good luck!
---
### Author:  [@missbunny](https://boards.straightdope.com/u/missbunny)
#### Post date: [October 6, 2004, 1:39pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/3 "2004-10-06T13:39:38Z")
Try reading it backwards - at least for typos, it’s easier to pick them out.
Of course reading backwards won’t help you find grammatical errors.
---
### Author:  [@Grossbottom](https://boards.straightdope.com/u/Grossbottom)
#### Post date: [October 6, 2004, 1:52pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/4 "2004-10-06T13:52:43Z")
Read it out loud in a fake accent, as if you were orating the contents. It’s the dorkiest, but best way of proofreading your own writing.
---
### Author:  [@Colophon](https://boards.straightdope.com/u/Colophon)
#### Post date: [October 6, 2004, 2:51pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/5 "2004-10-06T14:51:16Z")
I’m a professional proofreader — well, subeditor — and I use various techniques. As **missbunny** said, reading a line backwards is good for spotting typos, but I rarely use it as it is a pain in the backside. Generally I read a line at a time, using a pen or a sheet of paper to prevent me from skipping ahead a line. Make a point of looking at each individual word; don’t read a sentence at a time like you would normally.
Oh, and read it _on paper_. It is damn near impossible to proofread on screen.
Also, it is a fact of life that you will instantly spot the glaring error that you missed as soon as the work is published. Or, in, this case, posted…
---
### Author:  [@Colophon](https://boards.straightdope.com/u/Colophon)
#### Post date: [October 6, 2004, 2:53pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/6 "2004-10-06T14:53:13Z")
I should add that if you really want to be sure you spot everything, you should do two reads: one “word by word” to catch typos, bad spacing etc, and then another one where you’re reading “for sense” to make sure that the work hasn’t been garbled in editing.
---
### Author:  [@Adoptamom\_II](https://boards.straightdope.com/u/Adoptamom_II)
#### Post date: [October 6, 2004, 4:12pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/7 "2004-10-06T16:12:20Z")
excellent suggestions - thanks! 🆒
---
### Author:  [@ouryL](https://boards.straightdope.com/u/ouryL)
#### Post date: [October 6, 2004, 5:03pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/8 "2004-10-06T17:03:49Z")
I find actually reading it after typing it is the best. I skim read alot and my notes tend to be mnemonic(shorthand). Whenever I write for a prolonged bit, I always read each sentence or so before continuing. Many time I have come back and discovered my beginning paragraph “missing” - having been replaced with “gibberish”. My bad! :eek: :eek: :eek: :eek: :eek: :eek: :eek: 😃
---
### Author:  [@Hello\_Again](https://boards.straightdope.com/u/Hello_Again)
#### Post date: [October 6, 2004, 7:22pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/9 "2004-10-06T19:22:29Z")
If you aren’t already doing this, let your work “rest” – at least overnight but preferably a day or more – without looking at it before you begin your proofreading session. Read something else, like a magazine or a chapter from a novel, before returning to your work.
As **Colophon** noted, always proof a printed copy, you miss a lot on screen.
---
### Author:  [@zut](https://boards.straightdope.com/u/zut)
#### Post date: [October 6, 2004, 7:52pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/10 "2004-10-06T19:52:26Z")
I’m not an expert, but I’ve heard that it’s useful to print your proof version in a different font and size than you write it in. For example, if you typically use Times 12 point, do your proofing in 10-point Helvetica (for example). This forces line breaks in different places, and also makes the words visually _look_ different, so you’re more apt to catch an error that you’d otherwise gloss over because it looks familiar.
---
### Author:  [@spingears](https://boards.straightdope.com/u/spingears)
#### Post date: [October 6, 2004, 9:11pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/11 "2004-10-06T21:11:59Z")
> [@Hello Again](#):
>
> If you aren’t already doing this, let your work “rest” – at least overnight but preferably a day or more – without looking at it before you begin your proofreading session. Read something else, like a magazine or a chapter from a novel, before returning to your work.As **Colophon** noted, always proof a printed copy, you miss a lot on screen.
Put off proofreading at least two days, more if possible. Works on solving math problems too.
> [@zut](#):
>
> I’m not an expert, but I’ve heard that it’s useful to print your proof version in a different font and size than you write it in. For example, if you typically use Times 12 point, do your proofing in 10-point Helvetica (for example). This forces line breaks in different places, and also makes the words visually _look_ different, so you’re more apt to catch an error that you’d otherwise gloss over because it looks familiar.
Both of the above are good approaches. Also try bolding the entire document to make it look different.
---
### Author:  [@Harriet\_the\_Spry](https://boards.straightdope.com/u/Harriet_the_Spry)
#### Post date: [October 7, 2004, 12:34am UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/12 "2004-10-07T00:34:12Z")
Crisp Publications has a good book for about $10-15 on building proofreading skills. It has practice exercises and lots of tips. I found it useful.
I would also recommend really learning the spelling and grammar check settings of your word processor (assuming you use one). You can do things like delete “ass” from the dictionary, so it gets flagged as a misspelling, if it’s a word you’re unlikely to use in business writing. Also, you can set it to watch out for things like 2 spaces after every period, etc.
And, of course, don’t take any spelling or grammar checker as gospel.
---
### Author:  [@Zoe](https://boards.straightdope.com/u/Zoe)
#### Post date: [October 7, 2004, 5:49am UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/13 "2004-10-07T05:49:47Z")
When proofing, read the material aloud in a robot voice. Well…maybe not _too_ loud.
---
### Author:  [@Colophon](https://boards.straightdope.com/u/Colophon)
#### Post date: [October 7, 2004, 10:33am UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/14 "2004-10-07T10:33:31Z")
> [@Harriet the Spry](#):
>
> I would also recommend really learning the spelling and grammar check settings of your word processor (assuming you use one). You can do things like delete “ass” from the dictionary, so it gets flagged as a misspelling, if it’s a word you’re unlikely to use in business writing. Also, you can set it to watch out for things like 2 spaces after every period, etc.
Eye wood recommend toe tally switching of yore spell chequer. Their worse then useless, ass they give yew falls confidence - well, this sentence as bin past buy the spell cheque sew it must bee write!
---
### Author:  [@AllShookDown](https://boards.straightdope.com/u/AllShookDown)
#### Post date: [October 7, 2004, 11:39am UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/15 "2004-10-07T11:39:27Z")
When I was doing a lot of data entry I’d proofread by spelling each word to myself as I went over it.
---
### Author:  [@Hello\_Again](https://boards.straightdope.com/u/Hello_Again)
#### Post date: [October 7, 2004, 3:13pm UTC](https://boards.straightdope.com/t/learning-to-proof-read/267834/16 "2004-10-07T15:13:14Z")
Also, for those pesky grammatical questions that you feel you ought to have learned by now, but somehow haven’t – such as when to use _that_ and when to use _which_ – I recommend the uniquly helpful tome _Woe is I: The Grammarphobe’s Guide to Better English in plain English._