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.
Sierra Godfrey wrote:
> Ahoy mateys:
> I'm writing a manual which contains several sections with
> setp-by-step directions. I have given the headings of the
> sections imperatives, such as: "Set Network Addresses" and
> "Select the Operation Mode".
and asks for reasons why they should stay as imperatives.
IMO, there is one solid reason why most headings should *not* be set in
imperative mood. This is because imperatives instruct readers immediately to
perform the specified actions in the order presented, rather than advise
them how to do it when the need arises. Misuse of imperative mood for
headings can make imperative / indicative moods near useless as clues to
However, there is one exception: If a heading is major step of a
hierarchical procedure, then it should be set in imperative mood. For
example, if your directions form the set up prodedure for a bridge/router,
you might have:
To configure the unit:
Set Network Addresses
1. blah blah blah
2. blah blah
Select the Operation Mode
1. blah blah
Here the headings are major procedural steps with the numbered steps
providing the finer detail. For this case, I consider imperative mood to be
Just my two eurocents, but HTH,
geoff -at- gjctech -dot- co -dot- uk