Archive for the ‘Word retrieval errors’ Category

On the error watch

March 9, 2022

I’ll start with straightforward typos, where it’s getting the fingers to hit the intended keys that’s at issue, and then work out from there. From Greg Morrow on Facebook earlier today (exchanges lightly edited):

GM: My Dad’s got the 9-inch double-serrated Wüsthof bread knife and it is sweet. I don’t cover it exactly, I just want one exactly like it.

AZ > GM: Entirely beside your point, but I don’t cover it exactly is a beautiful example of a keyboard typo: cover for covet because R is next to T.

(more…)

Today’s stunning word retrieval error

November 27, 2018

From Ned Deily on Facebook:

Today’s Revisionist Word Fail (as seen in another FB group): “today marks the 40th anniversary of the assignation of Mayor George Moscone and Supervisor Harvey Milk.”

A form-based, rather than meaning-based error, but possibly prompted by spelling rather than pronunciation; the error was in writing, after all.

(more…)

Annals of error: name retrieval in the news

November 23, 2018

The error, as reported in HuffPo (among many other news sources) on the 13th: by Jenna Amatulli,

New Zealand Newspaper [the Gisborne Herald] Flubs Stan Lee’s Obituary, Writes ‘Spike Lee Dies’

(#1)

Inadvertent errors in retrieving words are common, especially in speech. Some are primarily motivated on phonological grounds, some primarily on semantic grounds, but typically both effects are relevant (some details in a moment). Inadvertent errors in retrieving proper names are particularly common, because everyone experiences a monumental number of proper names, with new ones popping up on a daily basis. In this context, Spike Lee for Stan Lee would be an entirely unsurprising error in name retrieval.

(more…)