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.
snip<And, I'll throw in the advice I give to reviewers. Make your
comments as specific as possible,
use questions as little as possible, and ...>snip
I'm not sure who wrote this section, but I wondered why they said "use
questions as little as possible." I often use questions as a way to
suggest changes or new information, or as a way to indicate a section
needs more clarity and give a little guidance. Perhaps there are better
ways to do this?
Maybe we're talking about different types of editing. Most of mine
involves editing technical writing done by programmers--I often don't
have the ability to add new information or resolve questions that come
up during reading. I have to ask questions. The problem I've found is
that questions, as opposed to suggestions or outright changes, garner
the least amount of response.
Applied Technical Systems, Inc. (ATS)
Bremerton, Washington USA
Developers of the CCM Database