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:"Susan W. Gallagher" <sgallagher -at- EXPERSOFT -dot- COM> Date:Tue, 12 Dec 1995 11:18:02 -0800
At 6:01 PM 12/11/95, Karen Mayer wrote:
> 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?)
I use contractions sparingly throughout my user manuals. Were I creating a
true reference guide, I might not use them at all. It would depend on the
product, the audience, and a bunch of other things.
Years ago, technical information was presented in the most formal language
the writer could muster. I remember the user guide for my CPM version of
CalcStar was written *entirely* in the third person and passive voice. It
was absolutely *horrible* -- hard to read and as boring as anything I've
ever read in my life.
Times change, conventions change, and we learn from mistakes -- both our own
and those of others. I know that even those who like to read don't necessarily
want to read what I'm writing, so I try to make the reading as painless as
possible for them. This includes a conversational, informal tone that uses
contractions when not using them would sound overly stiff and formal.