Re: And Or situations
Most of the instances when I've seen "and/or" in a technical document, the biggest problem with it was that there was no explanation as to when it should be "and," and when it should be "or." And there needed to be one.
That's bad writing. It is frustrating when non-writers say they have a clear document when what makes the document clear to them are the implications and allusions in the document that the non-writer has corrected with inferences and assumptions that the average reader will not make. Too many times, I have heard, "Everyone knows this." No, not everyone.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
Learn more: http://bit.ly/ZeOZeQ
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com
Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
References:
And Or situations: From: Cardimon, Craig
Re: And Or situations: From: Gene Kim-Eng
Previous by Author:
Re: And Or situations
Next by Author:
Re: And Or situations
Previous by Thread:
RE: And Or situations
Next by Thread:
RE: And Or situations
Search our Technical Writing Archives & Magazine
Visit TechWhirl's Other Sites
Sponsored Ads