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: Using Contractions in Software Manuals From:Laurel Nelson <Laurel_Y_Nelson -at- NOTES -dot- SEAGATE -dot- COM> Date:Tue, 11 May 1999 12:33:53 -0500
Victor: Contractions are harder to read and are more likely to be misread
than the long form, which is why I do not use them. For example, which of
the following is less likely to be misread?
{bmc IMP.BMP} You cannot create a BOM and add future changes in the same
ECO.
{bmc IMP.BMP} You can't create a BOM and add future changes in the same
ECO.
