RE: Help on Procedure Writing

Subject: RE: Help on Procedure Writing
From: bryan -dot- westbrook -at- amd -dot- com
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Wed, 5 Dec 2001 16:50:33 -0600

Check the archives around March 2000 for a previous discussion of this (I just read some of it today).


-----Original Message-----
From: Steve Hudson [mailto:steve -at- wright -dot- com -dot- au]
Sent: Wednesday, December 05, 2001 4:43 PM
To: TECHWR-L
Subject: RE: Help on Procedure Writing


Generally User Manuals have instructions, not procedures. Procedures must
state who, what, where, when and why. Instructions tell How.


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr

Have you looked at the new content on TECHWR-L lately?
See http://www.raycomm.com/techwhirl/ and check it out.

---
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.


Previous by Author: RE: Printing PDF File
Next by Author: RE: converting word to html
Previous by Thread: RE: Help on Procedure Writing
Next by Thread: RE: Help on Procedure Writing


What this post helpful? Share it with friends and colleagues:


Sponsored Ads