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 don't do release notes, but I do include chapters titled "Historical Information"
and "Technical Modifications" in some of the manuals I write. I have found that
it's best to write each item in the clearest, least clumsy way. This means that
sometimes I'll have something like your first example, and sometimes it will read
more like your second example.
There are people who want everything to follow a strict format, parallel
construction, blah blah blah. When this results in clear expression, I'm all for
it. When it results in an awkward sentence or paragraph, I would rather deviate
from the path, and make things clear.
Senior Technical Writer
TCF National Bank
jbaer -at- mailbox1 -dot- tcfbank -dot- com
Weakness Through Strength
Fanatics may defend a point of view
so strongly as to prove it can't be true.
Cadorette Johanne wrote:
> Hello all,
> I'm editing release notes and have a list of corrected bugs that are
> written like this:
> "When an entry was copied, it wasn't possible to record its name using
> the name recorder."
> It could also read:
> "When an entry is copied, it is now possible to record its name..."
> I've seen both styles used, but am wondering if one is better than the
> (BTW, not all the bugs are that simple and I'm not sure they could all
> be re-written that way.)
Be a published author! iUniverse gives you: a high-quality paperback, a
custom cover design, and distribution to 25,000 retailers. And it's
affordable. Join our almost 10,000 published authors today. http://www.iuniverse.com/media/techwr
Your monthly sponsorship message here reaches more than
5000 technical writers, providing 2,500,000+ monthly impressions.
Contact Eric (ejray -at- raycomm -dot- com) for details and availability.
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.