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.
Geoff Hart raised the question of whether there are any grammar "rules" we
can discard with TW/procedures. Like Geoff, I can't think of any. Whether
you are writing narrative, exposition, or imperative instructions, the same
rules apply. Or at least they have in all the 40 years of writing I have
done so far.
No, I have not whipped out *kewl* Web pages for clients. Nor have I
experienced the joys and agonies of developing screen-size bites for on-line
help/instruction. My expertise is in paper copies of generally lengthy
documents dealing with scientific and engineering projects. And I have
written reams of engineering and administrative procedures, but never
software operating procedures.
So, within the framework of my personal experience, I have to conclude that
grammar does count if you expect to operate within a frame of mutual
comprehension and understanding.
