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.
> -----Original Message-----
> From: Mason, Catheryn
>
> When I use repeated steps, I specify the condition to be met
> first, then
> specify the steps to be repeated. For example, "If
> additional transport
> facilities are required, repeat steps 2 and 3." In other
> words, I supply the
> reason or outcome first, followed by the action.
---
FWIW, I tend to look at itterative parts of a procedure the same way that I
look at programming. If the reader should perform the conditional steps at
least once, then I write in 'post-conditioned' mode. That is, the procedure
is something like:
2. blah blah
3. blah blah
Repeat steps 2 and 3 until you have entered all your transport
requirements.
However, if the reader may omit the conditional steps entirely, I write in
'pre-conditioned' mode. That is, the procedure is something like:
2. If you have transport requirements:
a. blah blah
b. blah blah
For me, the flow seems more logical.
Just my two eurocents.
Geoff Lane
Cornwall, UK
geoff -at- gjctech -dot- co -dot- uk
