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.
<snip>
>In the world of Standards, we follow standards (metastandards?) set by
folks
>like ISO. We have key words. The words "must," "shall," and "will" denote
things
>that are mandatory. The words "should" and "may" denote things that are
>optional.
In addition to ISO standards, there are legal implications. The words shall,
will, should,
might, and may have very specific legal meanings, especially in Requests for
Proposals,
Proposals, bids, and contracts.
If you are writing such documents, check with your legal staff when you
rewrite around
these words.
I don't think user manuals require as much restriction to meet legal
requirements.
However, for warnings and cautions, you often need these words for accuracy.
For example:
"Caution: You may loose data if you select the Faster Integrity option and
a power
failure occurs while data is being processed."
"Caution: You will loose data if you accidently type "del a*.* " instead of
"del a:*.*"
In the first case, it is possible that the power failure can occur at a time
when your
data has already been processed and saved.
In the second case, DOS *will* erase your autoexec.bat file and other files
(assuming
you are working from the C drive on a DOS machine, as is the context for
this example).
In body text and procedures, edit those extra words. If deleting the word
legally or
linguistically changes the meaning, put it back in.
-----Part II---------
Similarly, I'd like to get opinions on using "the foobar menu is displayed"
vs
"the foobar menu appears."
My training and experience with PCs tells me that novices are often
intimidated
by computers, and that "appears" is too much like magic. While "is
displayed" is
passive, the reader does not need to know who/what displays the menu.