Just Write Click

Technical writing with Continuous Integration and docs-as-code

  • JustWriteClick
  • Contact
  • Books by Anne Gentle
  • Introducing Docs Like Code
You are here: Home / talk.bmc / When user manuals cause a recall

August 8, 2006 by annegentle

When user manuals cause a recall

A postcard insert will be the remedy for an incorrect hotline listing

I wonder what the tech writer’s explanation is on this Honda and Acura Owner’s Manual Correction. Any tech writers for Honda who want to let us know the inside scoop? The story says that the National Highway Traffic Safety Administration has recalled over a million cars and motorcycles because the manual contains incorrect information for NHTSA’s vehicle safety hotline. Reuters reports that it only affects 2006 and 2007 models. They’re sending out postcards to dealers and owners with the corrected information.

I own a 2000 Honda Accord so I looked at the manual just to get an idea of how much text is affected, and in mine it appears in the last column in one page, and it’s only about 9 lines. The paragraph probably measures less than 3 inches by 3 inches.

In looking at the text to be corrected, I was reminded of the great sticker days of a grad school experience I had. As a grad student I worked on instructional materials for science teacher workshops. Once, when a typo got through our many layers of editing, we had to print and then peel-and-stick stickers by hand on a brochure to cover up and correct that typo. I don’t remember exactly how it got through, nor do I recall what we were correcting, but I sure do remember putting stickers on hundreds of brochures.

I know that there’s hardly any fair comparison between a brochure for science teachers and critical safety information for vehicles, but I do know incorrect information can make its way into any deliverable and we’re always on the look out for those last minute corrections. But sometimes our best efforts are thwarted when something makes it to print. Ah, for the correctibility of online doc… but wait, there’s always Google’s cache or the Wayback Machine at archive.org that we can’t just put a sticker on. (although you can request that Google remove a URL if you need to.) Plus, once a product ships with integrated online help, there’s no way to correct help content other than a reinstall.

What are some of your favorite correction memories that you’d like to share? Postcards? White-out? Stickers? Any more creative cover-ups?

Related

Filed Under: talk.bmc Tagged With: Acura, correction, Honda, recall, sticker, typo, whiteout, wite-out

More reading

Bubble graph showing sources of developer support data

I’ve been thinking a lot about developer support at Cisco recently, especially for the way the world works today with multiple cloud providers. This post is a re-publish of my talk from over five years ago, but the techniques and tools for listening and helping others are still true today. At Rackspace, we watched several […]

Cisco DevNet is our developer program for outreach, education, and tools for developers at Cisco. From the beginning, the team has had a vision for how to run a developer program. Customers are first, and the team implements what Cisco customers need for automation, configuration, and deployment of our various offerings. Plus, the DevNet team […]

I had a great talk with Ellis Pratt of Cherryleaf Technical Writing consulting last week. Here are the show notes, full of links to all the topics we covered. Podcasts are great fun to listen to and participate in, if a bit nerve-wracking to think on your feet and make sure you answer questions succinctly […]

At the beginning of this year, I worked hard to summarize my thoughts on API documentation, continuous publishing, and technical accuracy for developer documentation. The result is an article on InfoQ.com, edited by Deepak Nadig, who also was forward-thinking in having me speak to a few teams at Intuit about API documentation coupled with code. Always […]

Recently on Just Write Click

  • A Flight of Static Site Generators: Sampling the Best for Documentation
  • Try a GPT about “Docs Like Code” to ask questions
  • Discipline and Diplomacy: Docs in the Open
  • Let’s Find Out: When Do Static Site Generators Do Rendering?
  • GitHub for Managing Tech Docs

Just Write Click in your Inbox

Enter your email address to subscribe to Just Write Click and receive notifications of new posts by email.

Read More

  • Privacy Policy
  • About Anne Gentle, developer experience expert
  • Books by Anne Gentle
    • Conversation and Community
    • Docs Like Code, a Book for Developers and Tech Writers
  • Woman in Tech Speaker Profile
  • Contact

Books

  • JustWriteClick
  • Contact
  • Books by Anne Gentle
  • Introducing Docs Like Code

Copyright © 2026 · WordPress · Log in