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: Guide name quandry From:Jean Weber <jhweber -at- WHITSUNDAY -dot- NET -dot- AU> Date:Wed, 19 May 1999 18:33:52 +1000
While I sympathize with those who are caught in the middle of a debate
among co-workers regarding such things as "User Guide" vs "User's Guide"
etc (and are looking for an umpire), I have to ask:
What difference does it make? Is anyone going to be confused by calling the
book by one name or the other? I don't think so.
Surely there are far more important things for us to worry about, that DO
have important consequences on our readers' understanding of whatever-it-is
we're writing about.
Note that I am NOT advocating the wholesale mis-use (or non-use) of
apostrophes, but a bit of prioritising. In this case, all of the titles are
functionally equivalent, quite unambiguous, and in common use. What does it
matter which one you choose? If you and your co-workers (or boss) can't
agree, pull the winner out of a hat or something.