Proofreading Service - Pain in the English
Proofreading Service - Pain in the EnglishProofreading Service - Pain in the English

Your Pain Is Our Pleasure

24-Hour Proofreading Service—We proofread your Google Docs or Microsoft Word files. We hate grammatical errors with passion. Learn More




Member Since

February 10, 2010

Total number of comments


Total number of votes received



Latest Comments

How do I write out .25% ?

  • March 4, 2010, 2:58pm

Coming from a science/engineering background, I think that it's very clear if you write it out "point twenty-five percent."

Like a red herring, but unintentional.

  • February 26, 2010, 12:12pm

You know, after reading this:

I feel pretty comfortable using "red herring" to describe unintentional deception. Given its roots--"neither fish, nor flesh, nor good red herring"...meaning something that was nondescript or neither one thing nor another--and its modern accepted usage, I think it works fine for my purposes.

Like a red herring, but unintentional.

  • February 26, 2010, 12:05pm

The documentation is meant for internal use by fluent (but not always native) English speakers in Southern California.

So far, the page is still called "Red Herrings." Red herring is currently used around the office in this context, but I had reservations about using it in our documentation in that context when I read that it implies intent.

Like a red herring, but unintentional.

  • February 22, 2010, 7:10pm

Thank you all for your responses. I'm liking "will o' the wisp" and maybe "chasing your tail."

Like a red herring, but unintentional.

  • February 10, 2010, 1:41pm

From what I've read, a red herring does imply intentional deception, such as in a play, making it seem to the audience that one character is the villain to distract them from figuring out the actual antagonist.

I'll describe the exact situation.

I work in IT. We're creating a wiki page full of these instances of false leads for troubleshooting. For instance, our admin was trying to find the cause of a reported error in his logs because a web service wasn't running. It turns out that the error has always occurred and had nothing to do with the web service. We wrote it down so that it won't happen again.