Comments on: On Writing: Proofreading Methods http://blog.doingtext.com/2009/02/on-writing-proofreading-methods/ Fri, 30 Jul 2010 11:19:04 +0000 http://wordpress.org/?v=2.6.1 By: katrin http://blog.doingtext.com/2009/02/on-writing-proofreading-methods/#comment-260 katrin Mon, 09 Mar 2009 08:06:40 +0000 http://blog.doingtext.com/?p=189#comment-260 Tom, thanks very much for providing a those ideas. They are a great addition. Tom, thanks very much for providing a those ideas. They are a great addition.

]]> By: Tom http://blog.doingtext.com/2009/02/on-writing-proofreading-methods/#comment-259 Tom Sun, 08 Mar 2009 14:20:52 +0000 http://blog.doingtext.com/?p=189#comment-259 Great advice. I'd also add a couple more tips: * Don't just print out your text before you proofread. Also, change the font and the font size. I find courier can be a great font for proofreading and for spotting those little errors that always get left in there somewhere. Changing the font size means that words are in different places, tricking the lazy eye. This helps you spot errors like double spaces too. * Start making a list of the mistakes that you make regularly. Depending on what field you are in, this could be, say, writing millions when you mean billions. Or using American English Z's when you want British English S's. * Best advice? Write clean copy in the first place. It can save you a bunch of time! Great advice. I’d also add a couple more tips:
* Don’t just print out your text before you proofread. Also, change the font and the font size. I find courier can be a great font for proofreading and for spotting those little errors that always get left in there somewhere. Changing the font size means that words are in different places, tricking the lazy eye. This helps you spot errors like double spaces too.
* Start making a list of the mistakes that you make regularly. Depending on what field you are in, this could be, say, writing millions when you mean billions. Or using American English Z’s when you want British English S’s.
* Best advice? Write clean copy in the first place. It can save you a bunch of time!

]]>