Proofreading and Perception

I’d like to have a chat with you, my good reader (I know there’s one of you out there), about perception and how it relates to proofreading. More precisely, I want to talk about how it relates to the lack of proofreading. I even have a concrete example. Shall we?

This restaurant in Rockford IL is offering a “Final Feast” on the supposed last night of our lives, December 20, 2012. For $180 per person one can enjoy a nine-part dinner (an amuse bouche, courses one through three, an intermezzo, courses four and five, a cheese course, and dessert, each with wine pairings) including foie gras, caviar, Dungeness crab, Dover sole, filet mignon, and a chocolate cake adorned with edible 24k gold leaf. Pretty classy, right? Really upper crust, right?

Can someone please explain to me why no one proofread the menu? For that matter, no one proofread the webpage it’s on, either. Nor did anyone proofread their lunch menu, where one can get salad with “musclen,” or “mesclin,” or the actual “mesclun” blend. Yes. All three versions on one page, like some kind of bonus package. But I digress.

For a feast costing $180 a head, featuring such a five-star lineup of dishes and wines, I expect the printed menu (either online or on paper) to be error-free. I expect a high standard for the food AND for the written word in such an establishment. This ain’t EAT AT JOE’S with the one burned-out letter in the vintage neon sign. It’s a place run by an award-winning chef with a stellar reputation. Pity the printing on his menus didn’t receive the same level of attention as his dishes do. There is simply no excuse for “pared” instead of “paired,” or for “chives organic scrambled egg” (I’m pretty sure there should be a comma after “chives,” don’t you think?), or for “Tequilla.” And that’s only in the menu proper. There are also the errors in the text at the top of the web page, where we see that the staff is “exited to show off their . . . talent” and that the wines and liquor choices “will be announce closer to the dinner.”

Honestly, there is no excuse for this kind of sloppiness. As much as I despise using software to do an editor’s or proofreader’s job, in this case I don’t mind saying I think it would have helped. When I first heard about this “Final Feast” I thought it sounded like something I would actually attend, had I the wherewithal to do so. My perception changed when I saw how poorly the menu had been prepared. Perhaps one might say “He’s a chef, not an editor.” True enough, but–he should care as much about the printed description of his dishes as he does about the dishes themselves. As it is, I find I don’t really care that I can’t possibly afford to attend this “Final Feast.” As sloppy as the menu is, part of  me wonders just how perfect the foods will really be.

Perception. It’s powerful stuff.

Carved in stone

Some mistakes are harder to erase than others. In Oklahoma, state representative Mike Ritze sponsored a bill (and donated money) to install a granite monument of the Ten Commandments on the grounds of the state capitol building. The monument is 6 feet tall and 3 feet wide, and it weighs 2,000 pounds.

One potential problem is that it might invite a lawsuit from the American Civil Liberties Union because the monument violates the separation of church and state. But perhaps of more immediate concern is the fact that the granite contains a few spelling errors.

The Fourth Commandment mistakenly says, “Remember the Sabbeth day, to keep it holy.” (The correct spelling is Sabbath.)

The Tenth Commandment says, “Thou shalt not covet thy neighbor’s wife, nor his manservant, nor his maidseruant . . .” That final word, of course, should be maidservant. (Or perhaps this is actually a clever way to get around the rule. “Hey, God’s totally cool with me coveting my neighbor’s maidservant! It’s just the maidseruants I’ve gotta stay away from.”)

Ritze plans to have the misspellings corrected. No word on whether he’s adding another commandment that says, “Thou shalt not skip the spellcheck.”

The photo comes from this site.

Don’t get pregnant by becoming pregnant?

This morning while reading through my G+ feed, I came across this PSA from Bay Harbour Med Spa, forwarded by Eco Press.

The PSA is important, to be sure. Accutane use by pregnant women, or by those who are trying to become pregnant, is a serious matter. However, the problem is this wording:

” . . . if you’re thinking of becoming pregnant or are pregnant, you must NOT do so by becoming pregnant.”

Excuse me? What was that? Don’t get pregnant by getting pregnant?

Oh, okay–what the writer meant was, if you’re pregnant or trying to become pregnant, don’t use Accutane. That’s what they meant. It’s not anything like what they said, though.

I left a comment to that effect on the blog entry. We shall see what, if anything, comes of that. Meanwhile, ladies, stay away from Accutane if you’re pregnant or trying to conceive. The two do NOT play well together.

(And yes, I also noted the missing “s” from “clients” in the sentence immediately following this monstrosity.)

 

Let’s cheer on the Cncinnati Reds!

Here’s a fantastic collection of photos showing some astounding that’s-gotta-be-Photoshopped typos on professional sports jerseys. The misspelled player names are fun, but the real wowsers are the team name screw-ups, like the San Francicso Giants (#9), the Kentcuky Wildcats (#11), the Cncinnati Reds (#23), and many more. My favorite might be the way “Navy” is misspelled on the jersey in the inset on photo #20:

(In fairness, that might pass as a phonetic spelling of the team name.)

No insightful commentary from me. Just go enjoy the gallery. And be glad that your typos aren’t usually displayed for all the world to see (and photograph).

(Thanks to Kevin P. for alerting me to this amazing gallery!)

Probably not the kind of pubicity they wanted

The Red Lion Area school district in Pennsylvania tried to drum up some sponsors by creating a snazzy banner to display at football games. I imagine the idea was “Hey, once local businesses see how cool our banner looks, they’ll want to become sponsors and get their names up on the next banner!”

But their banner had a wee bit of a typo.

Don Dimoff, the marketing and communications manager for the district, said:

“Of all the missed letters, it had to be that one. The poor sign company feels horrible because they missed it. The people who hung the sign feel horrible because they missed it. I feel horrible. I’ve been losing sleep and haven’t eaten in two days trying to deal with this.”

The school district has apologized for what they described as an “unfortunate error.”

Cheer up, Red Lion folks! Maybe the banner will attract some sponsors after all—though maybe not the kind you were expecting.

You say employer, I say employee

“Okay, okay,” you say. “Pointing out typos and other copy editing failures is fun and all, but does any of this stuff really matter?”

Well, how about this? In Albuquerque, New Mexico, officials recently wrote up a proposal to increase the minimum wage and change how employees receive tips, hoping to get it on the November ballot. More than 12,000 people signed it, and the proposal seemed on its way to a slam-dunk victory, before someone noticed an error in a key section. Here’s the troublesome passage:

The measure would also require that starting in 2013, employers of tipped employees like waitresses and waiters be paid at least 45 percent of the minimum wage in cash wages from their employers.

See the problem? According to the wording above, who will be receiving the wages here? That’s right—the employers. Obviously, it should be the employees who will benefit from the change in minimum wage and tips, not their bosses. But that’s not what the proposal says. Councilor Ken Sanchez, one of the sponsors, said that if the proposal passes as is, lawsuits will probably be filed against the city.

As you might imagine, changing the wording of a government proposal after it’s been voted on involves just a bit of bureaucracy. Albuquerque city councilors are thinking about letting the current proposal appear on the ballot and also putting up another version with corrected wording. (Sure—that won’t be confusing to voters.)

Whatever happens, this is a good lesson in clear writing, good copy editing, and/or careful proofreading—take your pick.

(Here’s the source of this story.)

 

 

It’s a beautiful day in the . . . whaaaaat?!?

A guy named Ben Akselrod is running for the assembly in the Sheepshead Bay neighborhood of Brooklyn, NY. His campaign sent out mailers that blamed an increase in crime on the policies of his opponent. But check out the highlighted phrase in the mailer:

If you can’t read it, the phrase says the opponent “has allowed crime to go up over 50% in our negrohood.” Yow.

Not to worry! Akselrod says it was just an unfortunate typo. He responded thusly:

“As the candidate, I take full responsibility for this inadvertent error and I am sorry to anyone who was offended by it.”

That’s some inadvertent error, all right. You really have to go out of your way to misspell “neighborhood” as “negrohood.” Most typos aren’t quite so . . . different from the original word.

But even if we give Akselrod’s campaign the benefit of the doubt and assume that the word truly was an unintentional typo rather than a Freudian slip, the mailer still makes him look pretty bad. It contains several other spelling and grammatical errors. For example, we learn of Akselrod’s desire to “Creat” jobs and the fact that he misspelled the very name of the district he wants to represent! Heck, even his name seems like a typo—I mean, is it just me, or do you want to mark up your monitor to change the spelling to “Axelrod”? Clearly, the text wasn’t even run through a spellchecker, much less proofed by human eyes.

Regular readers of GRAMMARGEDDON! will remember that we recently saw another creative misspelling of “neighborhood” on a Boston public school sign. Maybe there’s something in the water on the east coast.

(The photo comes from this article, which provides more details on this incident. I’ll be interested to see how it affects Akselrod’s prospects for election.)

Q: What do you call a neighborhood for hobos?

Nothing instills confidence in your school like seeing a big typo on the sign by the front door.

O no!

Just think: someone (probably many someones) had to write those words, create the sign, proof the sign, drill it into the brick wall, look at it, nod contentedly, and walk away, whistling a happy tune.

The photo comes from the Dudley Street Neighborhood’s Facebook album, and if you check out the comments there, you’ll see that the school posted the photo proudly, then realized their mistake after several people pointed out the error. This article offers a good quote:

“I think we get a big, fat F for the spelling on this sign,” said Matt Wilder, director of media relations for Boston Public Schools. “We are already in the process of fixing it, and it will be taken down today.”

Kudos to the school for acknowledging the error and moving quickly to replace the sign. But this incident just goes to show you that, for good or ill, it’s hard to get away with typos in these days of instant feedback from social media.

 

Signs and Portents

Because I like the word “portents” in combination with “signs,” and for no other reason, I made that the title. I’m sure you’ll deal with it in your own ways.

Well, okay; part of my reason is also that I have this neat pic of a sign, which I’ve quite openly swiped from Amanda Patterson over at The Plain Language Programme (Aussies spell things with extra letters, just like the Brits do).

Here’s your sign. (Apologies to Bill Engvall for stealing his line, but in this case it really is relevant.)

All that’s needed to correct the problem is an “s” and an apostrophe. That’s all. Such a simple fix, yet so very far away . . .

Then there’s the gem I received via a Facebook message from a friend, Janet Deaver-Pack. She shared with me a typo from the cover of the newest catalogue from Bits and Pieces (http://bitsandpieces.com), which features a “secret book box” that I presume is like this one. I presume this, because the same error appears on this item. Look closely at the central “book” title. The last time I checked, something decorated with gold is “gilded.” Perhaps the creator of this product is a union supporter; that might begin to explain the typo.

As Janet said to me, “There are dictionaries in the world.” Of course, some folks need the special “misspeller’s dictionaries” because after all, if you don’t know how to spell the word to start with, how are you supposed to find it?

 

Super Mario and Hitler

I went to GenCon last week and have been thinking a lot about games, so what better time to bring you a trio of game-related typos?

Our first howler comes from New Super Mario Bros. 2, a recent release for the Nintendo 3DS. The Mario games are extremely popular across all Nintendo game systems, so this isn’t exactly a tiny error in an obscure product that no one will ever see.

No, Mario, I don’t want to click OK! That implies my acceptance of the typo hovering right above the button! (The above image is a screenshot I took of a short video that documents the error, proving it isn’t a fake.)

Our second typo is also from the New Super Mario Bros. 2 game, this time from the manual. (Yeah, yeah, I know—errors in an instruction manual? The devil you say!)

According to the note below the cute diagram, co-op play requires two Nintendo 3DS systems, two game cards, and two game cards. Is that Nintendo’s sneaky way of saying you need to buy four game cards? (The above image comes from this article that documents the typo.)

Let’s give poor Mario a break now and turn to our third typo, which comes from the world of Major League Baseball. I can’t improve on the title of the article where I found this typo, so I’ll just echo it here: There are closed captioning typos, and then there’s calling Carlos Pena “Hitler.”

It’s nice to know that Godwin’s law holds even in baseball games. (By the way, the expression on Pena’s face above is crying out for a “WTF?” thought bubble to be Photoshopped above his head.)

Thanks to the GRAMMARGEDDON! readers who alerted me to some of these mistakes. And if you see anything worth spotlighting on the blog, feel free to send it in. Your efforts will be also be appreciated.