Error Free?

 

(Flickr photo "Disney's annoying mistake" by Glenn Loos-Austin)

Writer’s Digest published an article by Craig Silverman in their November/December 2009 issue called “Regret the Error?” about having errors in our published works.

We’ve all seen typos and factual errors in books. As much as the authors pray their works will hit the market in pristine condition, errors can be overlooked and be copyrighted right along with the good stuff. Readers have varying degrees of tolerance. I’ve used the example before of a former cop who read a novel and was thoroughly enjoying it until he reached the point where the MC “flicked the safety off his Glock.” Glocks don’t have the type of safety that can be “flicked.” The cop laid the book down and never picked it up again.

I’ve read where an author populated her Texas setting with prairie dogs in an area too rocky for the critters. They don’t live in that part of the state. I didn’t stop reading the book, but at this point it’s about all I remember of it.

Writers are responsible for their content’s accuracy just as they’re responsible for catching typos and spelling and grammatical errors. According to Silverman:

Accuracy is an ethical and professional responsibility for all writers, and a significant error in a book or article can ruin your reputation.

Silverman writes nonfiction, but the statement is just as true for fiction writers. Someone will know when the author has scrimped on research and may respond as the cop did–never pick up the work again.

Preventing errors isn’t always a fool-proof process, but things can be done to avoid them. Silverman suggests we acknowledge our weaknesses:

  • What words do I always misspell?
  • Does my process, or lack thereof, for keeping track of my research cause me to make mistakes?
  • Do I have a tendency to get names wrong?

Answering these honestly will prompt us to double check our weakest areas. Having a quiver of knowledgeable and experienced critique partners with fresh eyes for the work also helps. (Author K.M. [Tarin] Weiland wrote an excellent article for AuthorCulture, “Never Miss a Typo Again,” which includes ideas like having your Adobe Reader read your work to you. Miss Adobe has a pecular voice, but this technique works.)

Errors can slip through despite our best efforts, and Silverman’s remedy is one guaranteed to keep him in the good graces of his readers: Acknowledge the fact that you can make mistakes:

. . . you need to realize (and acknowledge) that you’re human, and humans make mistakes. Those who present themselves as infallible gods are first to be renounced.

After you and your critters have checked your work, there will be fewer errors–hopefully no errors–but it’s always possible something slipped by. Silverman says to “be up front with readers about wanting them to help you identify mistakes. Create a system for correcting them.” He calls this his “Statement of Accuracy” and provides a place on his website for readers to report the errors they’ve found, then he posts the latest corrections on an RSS feed or readers can sign up to receive the information via email.

He says he enjoys the feedback from his readers:

Even though they’re pointing out your mistakes, it’s satisfying when someone takes time to read and respond to your work.

About Linda W. Yezak

Author/Freelance Editor/Speaker (writing and editing topics).
This entry was posted in Writing Tips and tagged , , , , , , . Bookmark the permalink.

8 Responses to Error Free?

  1. K.M. Weiland says:

    I don’t know that I’ve ever stopped reading a book because a factual error (but then I’m OCD that way). I’m willing to cut authors just a little bit of slack because I know from personal experience how easy it can be to miss a fact.

    Like

  2. pprmint777 says:

    I’venever stopped reading either, especially over something that minor. But I admit, I have stopped watching particular TV shows when they consistently misrepresent things.

    Like

  3. pclement says:

    Hi,
    I wanted to introduce myself to you. I am a friend of Jessica and she recommended your blog to me. I have recently (in the last 4 months) begun to blog myself. I was looking to make contact with other bloggers. I am still trying to learn more about it. I have subscribed to yours because it looks so informative. I also noticed in an older post you mentioned meeting Terry Burns at an upcoming conference. Would that be the one in Marshall this weekend? If so, I am attending that one and would like to meet you. Any friend of Jess is a friend of mine.

    Peggy Clement
    http://www.the workofhishands.wordpress.com

    Like

  4. Shaddy says:

    I must say that it bothers me to a great degree when I see a spelling error or something similar in a book or article. I’m like K.M. I’m too obsessive-compulsive to stop something I’ve started.

    Like

  5. Charlene Ang says:

    I’ve also had the displeasure of reading a book that I’m thoroughly enjoying, only to find a glaring typo or two inside. But because I was already right in the middle of the book, I didn’t want to stop just because of that. However, I once found an error in a story summary written on the back cover of a book I was thinking of buying. Needless to say, I didn’t buy it after that.

    P.S. I think you meant to type:

    “Writer’s Digest published an article by Craig Silverman in [their] November/December 2009 issue called “Regret the Error?” about having errors in our published works.”

    and

    “Even though they’re pointing out your mistakes, it’s satisfying when someone takes time to read and [respond] to your work.”

    Like

  6. Linda Yezak says:

    Charlene, how funny! Thanks for finding my own typos. I’ve been convinced for ages that I need a proofreader before I post my own work primarily because I tend to write so early. Any pre-coffee posts are likely to be brimming with errors.

    Anyone else checking for mistakes in this post, too late. Charlene caught them and I changed them!

    Like

Leave a reply to Linda Yezak Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.