Re: What do I call this document type?

[Emoto <emoto1 -at- gmail -dot- com>]

On Tue, Nov 26, 2019 at 4:21 PM Lin Sims <ljsims -dot- ml -at- gmail -dot- com> wrote:

> It's too long for a quick reference (12 pages!), but it isn't a full
> manual.
>
> It covers a subset of features (situations and processes that are unlikely
> to occur are left out), and provides little more than "to do this, perform
> these steps".
>
> There's none of the normal book components, such as a front or back cover
> or a TOC.
>
> I can't call it a reference guide because we use those to provide actual
> reference information such as database field specifications, not how-tos.
>
> I thought about using "<product name> Guide", but to me that implies an
> actual manual.
>
> Suggestions?
>

Quick Start Notes

Handy Function Guide

Tips and Tricks

-Bob
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | https://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