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:Len Olszewski <saslpo -at- UNX -dot- SAS -dot- COM> Date:Mon, 27 Oct 1997 20:04:24 GMT
In article <199710271946 -dot- TAA75018 -at- out2 -dot- ibm -dot- net>, Stephen Forrest
<techwriter -at- IBM -dot- NET> writes:
|> At 05:39 PM 10/27/97 GMT, Len Olszewski wrote:
[...]
|> >The second passage eliminates the "therefore", and provides information
|> >the reader might find useful. The causality is still apparent, but the
|> >second passage gives the reader an augmented version with facts the
|> >documentation should be revealing.
|>
|> Sorry, but I think the first paragraph is much better. The second makes my
|> eyes glaze over.
You must therefore be an engineer by training. Just a guess. Anything in
the active voice, or which is informative, does that to them. At least
in my experience. ;-)
So, I guess you are saying you don't have an alternative way to
eliminate "therefore" and "thus"?