A style guide should also support and be supported by a robust template. You can explain features of the template such as styles, macros, shortcut keys, boilerplate text, etc in the style guide.
Like many others, I like to include a list of pet hates and commonly made mistakes, especially those relevant to the topic. And remember, eschew complexity in terminology!!
Terry ************************************************** To view the austechwriter archives, go to www.freelists.org/archives/austechwriter To unsubscribe, send a message to austechwriter-request@xxxxxxxxxxxxx with "unsubscribe" in the Subject field (without quotes). To manage your subscription (e.g., set and unset DIGEST and VACATION modes) go to www.freelists.org/list/austechwriter To contact the list administrator, send a message to austechwriter-admins@xxxxxxxxxxxxx **************************************************
