What Not To Do Wednesday on Proofreading

ImageI used Grammarly to grammar check this post because sometimes, even a grammar geek like me (or is it I?) could use a proofreading hand.

So, grasshopper, we meet again.

I really hoped we would not meet again. Hoped that I had, finally, exhausted all the What Not To Do’s which one writer could actually manage to do. But alas, such was not the case.

It began with an email, an email that was, in fact, a query to an agent. So you can see that right from the get-go, this was a terribly important email. Because when one is querying, what one is really doing is trying to convince an agent to say, “Yes! Yes! A thousand times, yes! You are the one for me! Send me your manuscript immediately!”

One might even settle for, “Well, possibly you are the one for me. Send me a bit more of your manuscript and we shall see.”

But I think it goes without saying that one wants to send his or her absolute best query. Something bright and shiny and irresistible. At the very least, one wants to send a mistake-proof query. And that’s not difficult, grasshopper, is it? Not when one proofreads an email ten times before sending it.

Except that when one proofreads one’s work, over and over and over again, one might get so used to seeing the same mistake that one doesn’t actually “see” it at all. One might just hit “send” and whoosh! Out rockets the email with an egregious mistake.

Perhaps it’s a glaring grammatical error. Maybe it’s a misspelled word, or a misplaced modifier. Possibly (and I’m not admitting to anything here), it’s the name of two of the characters in your book but you have changed their names several times so that when you send the query the names might be A and B, but in the synopsis following the query, they are C and D.

Sometimes, grasshopper, you need another pair of eyes to proofread and find those egregious mistakes, especially when one is querying.

In writing a query, as in life, you only have one chance to make a first impression. Better make it a good one.

P.S. On this particular post, I scored a 91 out of 100 when I grammar checked on Grammarly. I also checked the afore-mentioned query/synopsis email, just to see if, say, a name snafu would be flagged (They were names with unusual spellings.). It was—along with a comma that didn’t belong in the OPENING sentence.

So, grasshopper, I suppose I can either write a blog post with my query and synopsis and hope that an agent reads it—or use Grammarly to proofread before I hit “send.”

Hi-Ho, Hi-Ho, It’s Off To Write We Go (After We Visit the Cows)

ImageA few posts ago, I mentioned that writing–and writing often–begets better writing. And that inspired me to pen “Becoming a Better Writer: Easier Than You Think” for my last Muffin musing. ICYMI, you can check it out here. (Public Service Announcement: ICYMI stands for In Case You Missed It. It’s embarrassing how long I stared at those letters till I figured it out.)

And for those of you struggling to become a better “tell-a-story-in-an-essay” writer, I’m passing along Linda O’Connell’s excellent tips, over at the Pen and Prosper blog. I read on her blog that she’s giving away a Chicken Soup book to one of the lucky commenters at her Pen and Prosper post. And in my experience, there is nothing like reading 100 Chicken Soup stories to get the feel for writing a Chicken Soup type story/essay.

I’m also including a heads up to the Green River Writers Contest. I like to support writers’ groups and Kentucky is a lovely state. Plus, whatever you’ve been working on to become a better writer is sure to find a category in this contest. (Check out the guidelines for fees and publishing rights.)

Lastly, because all (writing) work and no play makes Cathy a dull girl, I took Cathy-on-a-Stick out on a, uh…uh…whatchamacallit.

(Now see? Writing a sentence like that makes me realize I need to get back to work.)