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.
> My only real conccern is that this is a 1-step
> procedure: Slide the thingy to "On". The LED lights
> up. Everything else is description of what it looks
> like, but is shown as numbered steps.
>
> Whether you should number a 1-step procedure at all is
> another conversation, but I certainly wouldn't want to
> make something this simple seem more complicated than
> it is.
I think the writer has to decide whether
what the LED is doing or not doing
is important enough to warrant making
an LED check part of the power-up
procedure. If it isn't, then it should be
left out, or moved to another topic
devoted to interpreting the LEDs.
If it is an important part of power-up,
then it should be converted from an implied
instruction ("the LED will do something") to
an explicit instruction ("check the ..."; "verify
that the ..."; etc.)
NB I'm using "explicit" the way it used to be
used before some lazy editor decided it meant
"X-rated".
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
