naming doc addendums ?

["Monique Semp" <monique -dot- semp -at- earthlink -dot- net>]

Hello, TechWR-L-ers,

I have a âgenericâ version of a doc and Iâm preparing customer-specific addenda for (of course) customer-specific info.

There wonât be an addendum for all customers, only for customers whose implementation has been customized to a degree that the generic doc is insufficient (with respect to one-off features, additional options for some generic features, deployment info thatâs different due to some customer system oddity, and the like).

But... I keep going back and forth as to what to name the addenda.

The main doc is âProduct-Name Operatorâs Guideâ.

So, which of the following is better, in terms of finding the doc in a folder with lots of similarly named docs (important not only for me and doc repository users, but also for the customer), making it easily discoverable by customers, and likely other things that I havenât realized the importance of yet?

* Customer-Name Addendum to the Product-Name Operatorâs Guide
* Product-Name Operatorâs Guide: Customer-Name Addendum
* something else?

Thanks for your thoughts,
-Monique

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

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