Ruminating On: Proofreading

I used Grammarly to grammar check this post, because proofreaders are expensive. Truthfully, though, they should be paid a great deal more than they are.


Proofreaders are your last line of defense between editing and publishing. Proofreading is exactly what it sounds like. You are reading a proof—a completed project. A proofreader’ job is to find the errors left behind by the editing process. Proofreading should not involve plot line, sentence structure, word choice, or style. It should only involve errors the likes of missing words, leftover words, AWOL punctuation, and other such problems. Nothing drastic should change in a proofread. Well, that’s the hope anyway; because any plot holes or other inconsistencies should have been caught by your beta reader(s), content editor(s), and line editor(s). And yes, you need every one of those services mentioned. Remember, it takes a village to write a book.


I love proofreaders for two reasons. Firstly, my work being in their capable hands means that I’m that much closer to publication. Secondly, they’re part of the team that makes me sound good, and anyone who strives to make Edward Lorn readable is a hero of mine.


Over the course of two years, I have had the pleasure of working with a vast number of proofreaders. Some know their role, and others don’t. Sad but true. Even those that mean well can try too hard. Those proofers that drop their own personal preference and story ideas may believe they’re doing so to strengthen the work but, in the end, they’re causing more problems. If everything else in the editing process has gone the way it was suppose to, by the time the work has reached proofreading there should be no room for debate. Fix the errors leftover by editing and call it a day. Honestly, you’re not getting paid enough to dilly-dally on whether or not I should be using foul language in my prose, or using vernacular in my dialogue. Neither should you concern yourself with the religious beliefs of the person on page 96. These things might sound like specific complaints of mine, but they’re simply hypothetical. Don’t get me wrong, I love people that point out problems, but, in that stage… there shouldn’t be any problems.


I shall end this with a few words of advice. Just because your proofreader finds numerous missing words does not mean your editor sucks. You must first go over the manuscript and find how much was changed. Editing can create just as many problems as it fixes. This is not your editor’s fault. It’s yours, plain and simple. Also, if your proofreader does in fact correctly highlight plot problems and other such things they shouldn’t have concerned themselves with, do not freak out. Do, however, reevaluate your relationship with your beta readers and editors. You may need to try a different service. If all these people work together, you might want to talk to their boss.


I wrote this blog post for one, very specific reason. One of the most frequently asked questions I receive is, “What’s the difference between editing and proofreading?” Well, there you have it. If you feel anything in this blog was written in error, call me on it in the comment section below.


E.



 •  0 comments  •  flag
Share on Twitter
Published on September 25, 2013 14:22
No comments have been added yet.


Edward Lorn's Blog

Edward Lorn
Edward Lorn isn't a Goodreads Author (yet), but they do have a blog, so here are some recent posts imported from their feed.
Follow Edward Lorn's blog with rss.