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.
Old thread, hopefully new spin on "allow" v. "enable."
Subject:Old thread, hopefully new spin on "allow" v. "enable." From:Ron Rhodes <RRhodes -at- fourthchannel -dot- com> To:"'TECHWR-L Digest' (E-mail)" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 7 Mar 2000 09:42:40 -0500
Techwhirlers,
I have used the word "allow" throughout my career as a tech-writers. And I
really don't have a problem with it even now. But I am wondering if perhaps
"enable" is better when documenting software applications.
EXAMPLE:
Not
The Cost Wizard <ALLOWS> you to add, edit, and delete customized pricing
structures.
Instead
The Cost Wizard <ENABLES> you to add, edit, and delete customized pricing
structures.
"Allows" just sounds too permissive, restrictive, and constraining.
"Enables" sounds more energizing to me. But my Webster's and my Oxford
rendered similar definitions for both words.
Please forgive the hair splitting. I don't lose any sleep over this one. I
was just wondering if anyone could offer some authoritative advice.
Thank you,
Ron D. Rhodes
Lead Technical Writer
fourthchannel, inc.
rrhodes -at- fourthchannel -dot- com
