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: more on Safety words From:"Dennis Hays/The Burden Lake Group, Ltd." <dlhays -at- IX -dot- NETCOM -dot- COM> Date:Mon, 1 Jan 1996 06:00:58 -0800
In my last few contracts, I sat down with the project leader and developers
and had a discussion about the use of WARNING and CAUTION messages.
The consensus was as to hardware:
CAUTION: If the the user does not follow proper procedures he/she may cause
damage to equipment.
WARNING: If the user does not follow proper procedures, he/she may cause a
situation endangering the safety of people.
For software:
CAUTION: The user could cause damage to a record or store false data
(sometimes used also to caution the user about types of classified
data--NOFORN, CLASSIFIED, SECRET, etc.)
WARNING: The user cauld cause a loss of data in the database or cause a loss
of system integrity (not using back-up procedures or disconnecting the UPS).
There's my 2 cents on this thread...
======> Dennis Hays
======> The Burden Lake Group, Ltd.
======> Voice: 518/477-6388
======> Fax: 518/477-5006
======> E-Mail: dlhays -at- ix -dot- netcom -dot- com
