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: proofing docs From:Estella Clifford <cliff -at- FP -dot- COM> Date:Thu, 15 May 1997 14:18:14 EST
Cathy Carr wrote:
>. . . does anyone have suggestions
>as to how to keep up quality control in documentation that isn't read
>the people who write it? :-)
>I apologize if this is a silly or overly-basic question. You can
>directly if you don't want to bore the more experienced techwhirlers.
In my experience, the person(s) responsible for QA/QC for the product
line can be very helpful with proofing. The Quality person I usually
work with truly has an eagle eye for detail. He is just one of the
people on my list of reviewers, which also includes those doing testing
and the product manager, as well as the developers.
Also, by circulating a document for review, others see it with fresh