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: Gerunds in titles and headings From:"Porrello, Leonard" <lcporrel -at- ESSVOTE -dot- COM> Date:Wed, 13 Jan 1999 16:26:00 -0600
In a guide that contains only procedures, of course "procedure" before every procedure is redundant. But if the trainers are really stuck on the word, let them have it, but put it in the training guide title so that it need not be repeated dozens of times. On the other hand, if there is something other than procedures in the training man. . . .
Leonard Porrello
----------
From: KSchommer
Sent: Wednesday, January 13, 1999 4:12 PM
To: TECHWR-L; LCPORREL
Subject: Re: Gerunds in titles and headings
Tech writers in my department like to use the gerund form for headings in =
our manuals: "Adding a Note." However, our instructional designers have =
insisted that we use the form "Note Adding", or even better, "Note =
Addition", so that they can tack the word "Procedure" on the end in the =
related training materials.
Can anyone support my argument that "Procedure" is unnecessary in an OJT =
training guide that consists of nothing BUT procedures?!
