future functionality

Subject: future functionality
From: "Field, Kristin" <KField -at- LSAC -dot- org>
To: "TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com>
Date: Thu, 5 Jul 2001 09:31:21 -0400

I am currently updating a user's manual from a year and a half ago written
by a different author. There are several references in the manual of future
funcionality for the particular application I am updating the manual for.
For example, "The XXX allows you to do YYY. In a future release, you will
be able to do ZZZ." Personally, I think this is a bad practice and don't
feel that any future plans for the application should be in a user's
(basically a "How to") manual. I mean, this manual is a year and a half
old, as I mentioned, and the future functionality is still future
functionality.

Wouldn't that be best left to the marketing literature?

Kristin D. Field
Technical Communicator/Proofreader
Law School Admission Council
215.968.1141


^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com

TECH*COMM 2001 Conference, July 15-18 in Washington, DC
The Help Technology Conference, August 21-24 in Boston, MA
Details and online registration at http://www.SolutionsEvents.com


---
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.


Previous by Author: Robohelp Templates
Next by Author: re: future functionality
Previous by Thread: Rule about not using possessive?
Next by Thread: RE: future functionality


What this post helpful? Share it with friends and colleagues:


Sponsored Ads