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: Contractions in User Guides From:Kim Fawcett <kfawcett -at- DY4 -dot- COM> Date:Tue, 12 Dec 1995 16:12:00 DST
Yes, we do use contractions in my company's documentation. Or rather,
we use them in *some* of our documentation -- our getting started
guides. There's no rule against using contractions in our reference
manuals (none that I know of anyway <grin>), but we don't make the
same effort to include them.
The reason we try to use contractions in our getting started guides is
that we're aiming for a less formal, friendlier tone in those books.
We're trying to avoid intimidating new users, because our products
are very complex. A conversational style seems to work.
I hope that helps. I haven't heard of any research on this topic, but
I'd be interested in anything you find out.
Regards,
- Kim Fawcett
(kfawcett -at- dy4 -dot- com)
----------
From: TECHWR-L
To: Multiple recipients of list TECHWR-L
Subject: Contractions in User Guides
Date: Monday, December 11, 1995 6:01PM
I noticed that quite a few manuals contain contractions these days, and
wondered how widespread their use is. I don't mind them, but I was taught
to write out the words instead. Do you use contractions? If so, why? If
not, why not? (Has any research been done on this topic?)
