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.
"<snip> but the function doesn't really "do" anything by itself, other
than just sit there. The user implements the function as a tool in order
to carry out his or her bidding (i.e., it allows him or her to save
changes)."
Aha! Herein lies the precise reason I find myself using "lets",
"allows", "provides" etc. Thanks for reminding me! The code is not
alive. It cannot do anything by itself. They say the first step to
recovery is identifying the problem.
"<snip> there's no reason to put "allows you to" in every single
description. Just clutters things up and states the obvious."
I'll repeat this to myself every morning. Eventually, it will sink in.
At the least, everybody's help has been fantastic. I'm over my little
"tech writer's block".
Buy or upgrade to RoboHelp X3 today and receive the WebHelp
Merge Module for FREE ($299 value). RoboHelp X3's all-new
features include conditional text, completely re-engineered
printed documentation output, Context-sensitive Help Toolkit,
single-source layouts, and more!
Order online today at http://www.ehelp.com/techwr-l
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
