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.
Although I don't currently use contractions in my functional specs., release
notes, and ref./user manuals, I do enjoy using them in my course material.
I feel that their use brings the formality down one level and makes the
material a little more friendly to the user.
Incidently, I love writing course material, because I'm able to expand the
rules a little and insert a lot of fun graphics, comments, and so on. I'd
like to see this fun element extend to ref/user manuals; however, I'm more
cautious in these areas. Finally, I'd never insert contractions in very
technical information (f. specs. quality plans, design specs.).
I guess (in wrapping up) it really depends on the audience for which you are
writing.
************************************************
Tammy Sudol
Technical Writer - MOSAIC Department
M3i Systems Inc.
tammy -at- m3isystems -dot- qc -dot- ca
************************************************
