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:Re: Title case in documentation From:Gene Kim-Eng <techwr -at- genek -dot- com> To:Kim Bieler <kimbieler -at- gmail -dot- com> Date:Fri, 20 Apr 2012 08:41:46 -0700
When referring to the actual feature or command, we use whatever case the
user will see on labels, sentence case otherwise. For example, "To
configure permissive overrides, select Permissive Override."
Gene Kim-Eng
On Fri, Apr 20, 2012 at 7:04 AM, Kim Bieler <kimbieler -at- gmail -dot- com> wrote:
> New question: What is the best way to handle the names of features in
> software documentation?
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
