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.
Yeah, that's what I was going to suggest, except I'd change the first two examples in the OP to maintain the parallelism, even at the cost of losing the initial active verb.
Most places I've worked would NEVER admit to fixing a problem (because that would imply that their software was buggy to begin with!), but they would let us say that we'd made an improvement. So we could say, for example, "improved system response time...", but not, "fixed a problem where system crashed...."
Besides, the users don't care what the vendor did; they care what THEY can now DO that they couldn't do before. Shifting the emphasis to the new capability (which a fix is, since it didn't work before!) tells the user exactly that.
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 mkrupp128 -at- yahoo -dot- com -dot-
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-