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.
Subject:Troubleshooting Vs Release Notes From:Sion Lane <slane -at- ubq -dot- thrupoint -dot- net> To:techwr-l -at- lists -dot- techwr-l -dot- com Date:Tue, 31 Jan 2012 14:58:18 +0000
I'm wondering if anyone has any guidelines they use to decide what goes
into the Troubleshooting section of a guide and what is more appropriate in
the known issues/limitations section of a release note.
At the moment, I'm working on the theory of 'if it only happens
sometimes/on some devices/on some configurations, it goes in
Troubleshooting' and 'if it always happens whatever you do or whatever
you're using, it goes in the release note'.
Anyone got any better ideas?
--------------------
Note: The information contained in this message may be privileged and confidential
and protected from disclosure. If the reader of this message is not the intended
recipient, or an employee or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Thrupoint, Inc. - ubq
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
