Capitalizing product names of product features

["Karen Gwynn" <kwgwynn -at- att -dot- net>]

The names of many of the features in the web-based product I am documenting
are similar the words I am using to describe functionality. My style guide
indicates that when describing a feature the feature's name is capitalized
("Enter the primary contact email address in the Email Address field"). But
when I'm talking about the feature and all the things it can do, do I
continue to capitalize the term? ("this email address is the one the ABC
system uses to ...." or "this Email Address ...."). The situation is very
prevalent through the document I am writing as I describe interrelated
features, how to set them up, how they interact, etc. Another example: "When
you set permissions for creating definitions, you define them by functional
area" -- not a very good sentence, but "permissions", "definitions", and
"functional areas" are all things with this system.

 

I'd like to know how others handle the names of features in their
documentation.

 

Karen W. Gwynn

404-435-9975

kwgwynn -at- att -dot- net

 

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com

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

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives