NON-DELIVERY of: Re: Sentence structure

[Lotus -dot- M -dot- a -dot- i -dot- l -dot- Exchange -at- TESSPO-VA -dot- SMTRW -dot- LANGATE -dot- SPRINT -dot- COM]

--7Z9aZTyFrxFuQFpzQYPwH088pMFVoEOb
Content-type: text/plain; charset="us-ascii"


                           Delivery Failure Report

                               Your document:
                            Re: Sentence structure
                         could not be delivered to:
                   Ronni Perry -at- CRWMS at DL-Notes -at- DL_CCMAIL
                                  because:
                   MailEx0010: cc:Mail user name too long.
                                Routing path:
                           DLLN2,DLLN2,DLLN2,DLLN2


                          ________________________




--7Z9aZTyFrxFuQFpzQYPwH088pMFVoEOb
Content-type: text/plain; charset="us-ascii"

RFC-822-Headers:
Comments: To: Karen Mayer
<Karen_Mayer -dot- TOUCH_TECHNOLOGY -at- NOTES -dot- COMPUSERVE -dot- COM>
Comments: cc: Multiple recipients of list TECHWR-L          <TECHWR-L -at- VM1 -dot- ucc -dot- o
kstate.edu>

--7Z9aZTyFrxFuQFpzQYPwH088pMFVoEOb
Content-type: text/plain; charset="us-ascii"

Karen --

  When you are giving an instruction in your documentation, do you first
  give the instruction, then identify the need or condition, or do you
  identify the need or condition first and follow it with the instruction

First state the purpose, then provide the instruction. Doing the reverse
may tempt a reader to perform the action without knowing what will
follow. For example, I would not want a reader to "Press Escape to delete
all data" while simply reading and mindlessly following direction. So, I
would write, "To delete all data, press Escape." Then the reader can say,
"Oh. I don't want to do _that_."


Technical Writer
Computer columnist for _Ohio Valley Computing_
Co-Author of the IDG book _Internet Gizmos for Windows_


--7Z9aZTyFrxFuQFpzQYPwH088pMFVoEOb--