TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: How to treat doc errata? From:"I started out with nothing. I still have most of it left." <sharona -at- INTRANET -dot- COM> Date:Thu, 24 Oct 1996 11:52:51 EDT
>b) inserting a loose page calling attention to the error and giving
>the correct information. These manuals are wire bound and we can't
>fix them.
>c) adding a little blurb in the readme file. No one reads these
>anyway......do they?
I have handled it in the past by inserting a loose page in such
circumstances, and I have seen other vendors do the same. I think
you should put it in the readme file as well. This way the user
has two places not to read it. ;-) Seriously, it never hurts to
have more than one place for information such as this.
