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: USAGE: "Therefore" and "thus" From:Tracy Boyington <tracy_boyington -at- OKVOTECH -dot- ORG> Date:Mon, 27 Oct 1997 11:58:24 -0600
> >The word "thus" is a little harder sometimes, because engineers
> >use it as shorthand for "in this way," "as a consequence of
> >this action," "this demonstrates that," or like phrases. I
> >usually try to figure out what the logical conclusion (if any )
> >the engineer was trying to indentify, then see if the structure
> >of the paragraph lets me get by without the conclusion
> >identifier. If not, I still replace "thus" with something more
> >friendly, because I find "thus" to be especially pretentious.
You could always change it to IF, THEN, ELSE. ;-)
I agree (I think) with what Carol says... see if the sentence make sense
without it. If they're still necessary but "thus" and "therefore" sound
too stuffy in your documentation, replace them with something more
user-friendly.
Tracy
--
==============================================
Tracy Boyington tracy_boyington -at- okvotech -dot- org
Oklahoma Department of Vocational and Technical Education
Stillwater, OK, USA http://www.okvotech.org/cimc/home.htm
==============================================