"Obvious" warnings - drawing the line

["David Downing" <DavidDowning -at- users -dot- com>]

I've been following the thread about warning that are so obvious as to
be stupid, and it seems that the burning question -- and the practical
one for technical writers -- is: Where do you draw the line between
something that "anybody oughta know" and something that people may
legitimately not be aware of and thus have a legitimate need to be
warned against?  Okay, it's probably general knowledge that you
shouldn't point a loaded gun at any living thing that youwant to stay
that way, but is it general knowledge that an unplugged TV can still
give you a nasty shock because of static electricity? 


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  Your monthly sponsorship message here reaches more than
  5000 technical writers, providing 2,500,000+ monthly impressions.
  Contact Eric (ejray -at- raycomm -dot- com) for details and availability.

Buy RoboHelp Deluxe starting at only $798: you'll get RoboDemo, the hot new
software demonstration tool that's taking the Help authoring world by storm,
together with RoboHelp Office. Learn more at http://www.ehelp.com/techwr-l
---
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.