#SpellcheckCannotSaveYou: a bit of explanation

This has gotten a little attention in the last month or so, mostly thanks to June Casagrande (a fantastic editor-person who’s written a number of highly accessible grammar and style books, most of which I own). One thing that some folks don’t quite understand is why it’s “cannot” and not “won’t” or “will not.”

Simple. And it’s got NOTHING to do with the fucking apostrophe (which kills a hashtag every time, y’know).

I don’t care whose software it is; the fact is, no spellcheck program is able to save you from yourself. It is incapable. It is unable. It CANNOT save you. It can ensure you won’t have any egregious misspellings, but when it comes to homonyms, it cannot save you. If the word’s spelled correctly, but still the wrong word, spellcheck is unable, incapable, powerless to save you.

It’s not a case of it being unwilling to perform, or uninterested in doing the job.

It cannot perform that duty. Only a human brain in conjunction with human eyes and reasoning abilities can parse the difference between cleaver and clever. No spellchecker will flag either of those words, unless for some reason you have manually told it to. (You did know you have that kind of control, right? Like, telling the program to always flag the word “pubic” to save you from mortification?)

Spellcheck cannot save you from errors stemming from correctly spelled words used incorrectly. Not that it will not (although technically, that’s true — it won’t save you, but there’s more to the sense behind the phrasing), but that it cannot. It is not capable. It is unable. It cannot perform that action.

Spellcheck cannot save you.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s