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.
If you've got a friend in the Quality Assurance/Testing department that's
willing to help you out, try them. My QA department has some of the best
"eyes" I've ever seen, and did a great job at identifying errors and
Also, I know this is going to sound strange, but try reading your
documentation sentence by sentence BACKWARD. I really resisted this bit
of advice, but I have to admit it works. This won't help you identify
"content" errors, but because you're looking at sentences out of context,
it's easier to identify grammar/spelling issues.
Other than that, it's an ugly job, but you know how the rest of the
jwesterberg -at- access-health -dot- com