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.
> Please tell me what you believe is meant by "to address something".
To do something about it--that is, fix it in some way.
Looking at it again and deciding not to do anything about it again doesn't count as "doing something about it," in my book.
If you're going to use "addressing an issue" to mean "either fixing it or not fixing it," why not add a one-sentence note just to explain this--i.e. you're undertaking to look at the issue again, but this shouldn't be taken as an undertaking to fix it in the next release or any release.
I suspect this isn't the answer you wanted, Kevin, but that's how I feel. "Addressing issues" makes me think of those endless, useless meetings we're sometimes forced to attend, where an agreement to schedule another pointless meeting is classed as an 'action'.
Stuart
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: 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-
