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: Single-step procedures From:Christopher Knight <knight -at- ADA -dot- COM> Date:Fri, 1 Aug 1997 10:22:52 PDT
Thanks very much to eeveryone who posted to this topic. To those who
doubted that a procedure with one step is not a procedure, I say:
yes it is. I distinguish a procedure by distinctive typography for the
procedure objective (typically also a separate line), and by the use of
step numbers, so as to provide visual cues for busy readers scanning for
information on how to accomplish a task. Whether that takes 1 or 5 steps
is immaterial. Whenever possible, I avoid the "1"/bullet problem for
single-step procedures by having the objective run into the step.
In this case, the objective and (single) step were too long, and the
objective too important, for this solution.
So, gentle readers, what I have done is follow the suggestion of some,
and used a dingbat (a small right arrow) instead of the bullet.
Thanks again!
TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html
