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: Overuse of gerunds in headings From:"Edwin Skau" <eddy -dot- skau -at- gmail -dot- com> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Wed, 5 Apr 2006 09:00:25 +0530
As with other areas in language and linguistics, a "standard" or
"guideline" defines the preferred way of doing or saying something. There
are exceptions. While consistency is desirable, clarity is critical, and
will always override the need to be consistent, when the two clash.
When you deviate from the standard, it makes sense to have your deviations
conform to a recognizable pattern.
> > Whirlers,
> > I have worked in several Pubs departments where the standard heading
> > style was defined as requiring gerunds. That works fine for me when the
> > subject is Installing, Configuring, Restoring...stuff like that.
> > However, for an introductory chapter or section, am I breaking a
> > well-established standard by calling it, for example, "Introduction
> > to..." or "Overview of..."? I usually see, in similar situations, that
> > the author uses "Understanding ..." in order to conform to gerund
> > orthodoxy. For some unknown reason, that "Understanding ..." bugs me.
> > -- Will
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today!. http://www.webworks.com/techwr-l