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: Writing clearly From:cjcbrown -at- comcast -dot- net To:"Leonard C. Porrello" <Leonard -dot- Porrello -at- SoleraTec -dot- com> Date:Thu, 20 May 2010 15:02:04 +0000 (UTC)
I might add,
"Before using the word ensure, make sure your audience knows the difference between ensure and insure. "
Connie
----- Original Message -----
From: "Leonard C. Porrello" <Leonard -dot- Porrello -at- SoleraTec -dot- com>
To: "Dana Worley" <dana -at- campbellsci -dot- com>, techwr-l -at- lists -dot- techwr-l -dot- com
Sent: Thursday, May 20, 2010 7:53:49 AM GMT -08:00 US/Canada Pacific
Subject: RE: Writing clearly
Dana makes an excellent point. Writers differ from one another in how
they approach writing. Some writers outline. Some writers brainstorm.
Some writers network. Some writers get drunk (and although this approach
apparently worked for Faulkner, I don't see it working well for tech
writers).
So, a better maxim would be, "ensure that you've said everything that
needs to be said."
Leonard
-----Original Message-----
From: techwr-l-bounces+leonard -dot- porrello=soleratec -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+leonard -dot- porrello=soleratec -dot- com -at- lists -dot- techwr-l -dot- c
om] On Behalf Of Dana Worley
Sent: Thursday, May 20, 2010 6:01 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Writing clearly
On Wednesday, May 19, 2010, 'Technical Writing Plus' wrote:
> But you always should know exactly what it is that you want to say
> (before you put pen to paper).
I disagree with this point. If I am having trouble knowing where to
start, I will begin by typing a
random list of relevant points and work from there. In other words, I
don't always know
exactly what I want to say, but I do have an idea of the points that
need to be covered.
I don't think my writing is more or less clear because of this, but it
certainly helps with
composition.
Gain access to everything you need to create and publish documentation,
manuals, and other information through multiple channels. Choose
authoring (and import) as well as virtually any output you may need. http://www.doctohelp.com/
Â- Use this space to communicate with TECHWR-L readers -
ÂÂ - Contact admin -at- techwr-l -dot- com for more information -
---
You are currently subscribed to TECHWR-L as cjcbrown -at- comcast -dot- net -dot-
Gain access to everything you need to create and publish documentation,
manuals, and other information through multiple channels. Choose
authoring (and import) as well as virtually any output you may need. http://www.doctohelp.com/
- Use this space to communicate with TECHWR-L readers -
- Contact admin -at- techwr-l -dot- com for more information -
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-