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.
I would rewrite the passage in several different manners and allow your
client to choose. In this case, the double-edged vs. two-edged sword
debate is meaningless to me - I'm not familiar with the expression. My
reaction to it is negative and I wonder, would the client want their
product to be perceived negatively?
I think that's one of the problems with metaphors, idioms, etc. How can
we be sure the audience understands it? If our charge as technical
communicators is to produce understandable information, I'd drop the
whole metaphor in favor of clear writing.
Examples:
1 Increased XXX capacity enables significantly lower cost functionality
(and I am not sure what actually means), but it also increases
complexity.
2 Consider the trade-offs when deciding to increase XXX capacity; as
capacity increases, cost is lowered but complexity is increased.
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
