- User Manuals Are An Example Of Information Utility Management
- User Manuals Are An Example Of Information Utility Bill
- Example Of Information System
On Linux and other Unix-like operating systems, man is the interface used to view the system's reference manuals.
Description
man Canon vixia hf r11 user manual. is the system's manual viewer; it can be used to display manual pages, scroll up and down, search for occurrences of specific text, and other useful functions.
Each argument given to man is normally the name of a program, utility or function. The manual page associated with each of these arguments is then found and displayed. A section number, if provided, will direct man to look only in that section of the manual. The default action is to search in all of the available sections, following a pre-defined order and to show only the first page found, even if page exists in several sections.
Mar 01, 2017 Great Examples of perfect Product Documentation and Help Guides: The manual that is provided by BigCommerce is designed and presented in such a way to attract the visitors to the site. There are also links that are given for Chat and Community Forum in order to contact the support team in case of any of the queries. Municipal Financial Reporting and Accounting Manual Department of Communities, Cultural Affairs and Labour Province of Prince Edward Island 30. An accrued liability is a developing, but not yet enforceable, claim by another person, which is accumulating with the passage of time or the receipt of service. Example of validating the structure of an indexed file Example of a Rebuild options file Example of calling Rebuild from a COBOL program Example Relative File Definition Sequential Files Example Record Sequential File Definition - Fixed Length Records Example Record Sequential File Definition. Feb 17, 2014 The examples I show are examples of what makes great end user documentation. 1 - Write great titles. Great end user documentation consists of titles that are specific, and often in the form of performing a task. This not only makes it easier for your end users to find what they are looking for, but it helps you write better articles. Find your owner manual, warranty, and other information here. Print, read or download a PDF or browse an easy, online, clickable version. Access quick reference guides, a roadside assistance card, a link to your vehicle’s warranty and supplemental information if available.
Syntax
General Options
-h, --help | Print a help message and exit. |
-V, --version | Display version information and exit. |
-Cfile, --config-file=file | Use configuration file file rather than the default of ~/.manpath. |
-d, --debug | Print debugging information. |
-D, --default | This option, when used, is normally specified as the first option; it resets man's behaviour to its default. Its use is to reset those options that may have been set in $MANOPT. Any options that follow -D will have their usual effect. |
--warnings[=warnings] | Enable warnings from the groff text formatter. This may be used to perform sanity checks on the source text of manual pages. The warnings is a comma-separated list of warning names; if it is not supplied, the default is 'mac'. See the 'Warnings' node in the groffinfo page for a list of available warning names. |
Options: Main Modes of Operation
-f, --whatis | Equivalent to the whatis command; displays a short description from the manual page, if available. |
-k, --apropos | Equivalent to the apropos command; Search the short manual page descriptions for keywords and display any matches. |
-K, --global-apropos | Search for text in all manual pages. This option is a brute-force search, and is likely to take some time; if you can, you should specify a section to reduce the number of pages that need to be searched. Search terms may be simple strings (the default), or regular expressions if the --regex option is used. |
-l, --local-file | Activate 'local' mode. Format and display local manual files instead of searching through the system's manual collection. Each manual page argument will be interpreted as an nroff source file in the correct format. No cat file is produced. If a dash ('-') is listed as one of the arguments, input will be taken from stdin. When this option is not used, and man fails to find the page required, before displaying the error message it attempts to act as if this option was supplied, using the name as a file name and looking for an exact match. |
-w, --where, --location | Don't actually display the manual pages; instead print the location(s) of the source nroff files that would be formatted. |
-W, --where-cat, --location-cat | Don't actually display the manual pages, but do print the location(s) of the cat files that would be displayed. If -w and -W are both specified, print both, separated by a space. |
-c, --catman | This option is not for general use and should only be used by the catman program. |
-Rencoding, --recode=encoding | Instead of formatting the manual page in the usual way, output its source converted to the specified encoding. If you already know the encoding of the source file, you can also use manconv directly. However, this option allows you to convert several manual pages to a single encoding without having to explicitly state the encoding of each, provided that they were already installed in a structure similar to a manual page hierarchy. |
Options: Finding Manual Pages
-Llocale, --locale=locale | man will normally determine your current locale by a call to the C function setlocale which checks the values of various environment variables, possibly including $LC_MESSAGES and $LANG. To temporarily override the determined value, use this option to supply a locale string directly to man. Note that it will not take effect until the search for pages actually begins. Output such as the help message will always be displayed in the initially determined locale. |
-msystem[,..], --systems=system[,..] | If this system has access to other operating system's manual pages, they can be accessed using this option. To search for a manual page from (for example) the 'NewOS' manual page collection, use the option -m NewOS. The system specified can be a combination of comma delimited operating system names. To include a search of the native operating system's manual pages, include the system name man in the argument string. This option will override the $SYSTEM environment variable. |
-Mpath, --manpath=path | Specify an alternate manpath to use. This option overrides the $MANPATH environment variable and causes option -m to be ignored. A path specified as a manpath must be the root of a manual page hierarchy structured into sections as described in the man-db manual (under 'The manual page system'). To view manual pages outside such hierarchies, see the -l option. |
-Slist, -slist, --sections=list | The list is a colon- or comma-separated list of `order specific' manual sections to search. This option overrides the $MANSECT environment variable. (The -s spelling is for compatibility with System V.) |
-esub-extension, --extension=sub-extension | Some systems incorporate large packages of manual pages, such as those that accompany the Tcl package, into the main manual page hierarchy. To get around the problem of having two manual pages with the same name such as exit, the Tcl pages were usually all assigned to section l (lowercase L). However, it is now possible to put the pages in the correct section, and to assign a specific 'extension' to them, in this case, exit(3tcl). Under normal operation, man displays exit in preference to exit(3tcl). To negotiate this situation and to avoid having to know which section the page you require resides in, it is now possible to give man a sub-extension string indicating the package of the page. Using the above example, supplying the option -e tcl to man will restrict the search to pages having an extension of *tcl. |
-i, --ignore-case | Ignore case when searching for manual pages. This option is the default. |
-I, --match-case | Search for manual pages case-sensitively. |
--regex | Show all pages with any part of either their names or their descriptions matching each page argument as a regular expression, as with apropos. Since there is usually no reasonable way to pick a 'best' page when searching for a regular expression, this option implies -a. |
--wildcard | Show all pages with any part of either their names or their descriptions matching each page argument using shell-style wildcards, as with apropos --wildcard. The page argument must match the entire name or description, or match on word boundaries in the description. Since there is usually no reasonable way to pick a 'best' page when searching for a wildcard, this option implies -a. |
--names-only | If the --regex or --wildcard option is used, match only page names, not page descriptions, as with whatis. Otherwise, this option has no effect. |
-a, --all | By default, man will exit after displaying the most suitable manual page it finds. Using this option forces man to display all the manual pages with names that match the search criteria. |
-u, --update | This option causes man to perform an inode-level consistency check on its database caches to ensure that they are an accurate representation of the filesystem. It will only have a useful effect if man is installed with the setuidbit set. |
--no-subpages | By default, man will try to interpret pairs of manual page names given on the command line as equivalent to a single manual page name containing a hyphen or an underscore. This supports the common pattern of programs that implement a number of subcommands, allowing them to provide manual pages for each that can be accessed using similar syntax as would be used to invoke the subcommands themselves. For example, the command: displays the manual page: To disable this behaviour, use the --no-subpages option. For example: will instead show the manual pages for both git and diff: |
Options: Controlling Formatted Output
-Ppager, --pager=pager | Specify which output pager to use. By default, man uses pager -s. This option overrides the $MANPAGER environment variable, which in turn overrides the $PAGER environment variable. It is not used in conjunction with -f or -k. The value may be a simple command name or a command with arguments, and may use shell quoting (backslashes, single quotes, or double quotes). It may not use pipes to connect multiple commands; if you need that, use a wrapper script, which may take the file to display either as an argument or on standard input. | ||||||||||||||||||||
-rprompt, --prompt=prompt | If a recent version of less is used as the pager, man will attempt to set its prompt and some sensible options. The default prompt looks like:..where name denotes the manual page name, sec denotes the section it was found under and x the current line number. This is achieved by using the $LESS environment variable. Supplying -r with a string will override this default. The string may contain the text $MAN_PN which will be expanded to the name of the current manual page and its section name surrounded by '(' and ')'. The string used to produce the default could be expressed as It is broken into three lines here for the sake of readability only. For its meaning see the manual for less. The prompt string is first evaluated by the shell. All double quotes, back-quotes and backslashes in the prompt must be escaped by a preceding backslash. The prompt string may end in an escaped $ which may be followed by further options for less. By default, man sets the -ix8 options. If you want to override man's prompt string processing completely, use the $MANLESS environment variable described below. | ||||||||||||||||||||
-7, --ascii | When viewing a pure ASCII manual page on a 7-bit terminal or terminal emulator, some characters may not display correctly when using the latin1 device description with GNUnroff. This option allows pure ASCII manual pages to be displayed in ASCII with the latin1 device. It will not translate any latin1 text. The following table shows the translations performed: some parts of it may only be displayed properly when using GNU nroff's latin1 device.
This option is ignored when using options -t, -H, -T, or -Z and may be useless for versions of nroff other than GNU's. | ||||||||||||||||||||
-Eencoding, --encoding=encoding | Generate output for a character encoding other than the default. For backward compatibility, encoding may be an nroff device such as ascii, latin1, or utf8 as well as a true character encoding such as UTF-8. | ||||||||||||||||||||
--no-hyphenation, --nh | Normally, nroff will automatically hyphenate text at line breaks even in words that do not contain hyphens, if it is necessary to do so to lay out words on a line without excessive spacing. This option disables automatic hyphenation, so words will only be hyphenated if they already contain hyphens. If you are writing a manual page and want to prevent nroff from hyphenating a word at an inappropriate point, do not use this option, but consult the nroff documentation instead; for instance, you can put '%' inside a word to indicate that it may be hyphenated at that point, or put '%' at the start of a word to prevent it from being hyphenated. | ||||||||||||||||||||
--no-justification, --nj | Normally, nroff will automatically justify text to both margins. This option disables full justification, leaving justified only to the left margin, sometimes called 'ragged-right' text. If you are writing a manual page and want to prevent nroff from justifying certain paragraphs, do not use this option, but consult the nroff documentation instead; for instance, you can use the '.na', '.nf', '.fi', and '.ad' requests to temporarily disable adjusting and filling. | ||||||||||||||||||||
-pstring, --preprocessor=string | Specify the sequence of preprocessors to run before nroff or troff/groff. Not all installations will have a full set of preprocessors. Some of the preprocessors and the letters used to designate them are: eqn (e), grap (g), pic (p), tbl (t), vgrind (v), refer (r). This option overrides the $MANROFFSEQ environment variable. zsoelim is always run as the very first preprocessor. | ||||||||||||||||||||
-t, --troff | Use groff -mandoc to format the manual page to standard output. This option is not required in conjunction with -H, -T, or -Z. | ||||||||||||||||||||
-T[device], --troff-device[=device] | This option is used to change groff (or possibly troff's) output to be suitable for a device other than the default. It implies -t. Examples include dvi, latin1, ps, utf8, X75 and X100. | ||||||||||||||||||||
-H[browser], --html[=browser] | This option will cause groff to produce HTML output, and will display that output in a web browser. The choice of browser is determined by the optional browser argument if one is provided, by the $BROWSER environment variable, or by a compile-time default if that is unset (usually lynx). This option implies -t, and will only work with GNU troff. | ||||||||||||||||||||
-X[dpi], --gxditview[=dpi] | This option displays the output of groff in a graphical window using the gxditview program. The dpi (dots per inch) may be 75, 75-12, 100, or 100-12, defaulting to 75; the -12 variants use a 12-point base font. This option implies -T with the X75, X75-12, X100, or X100-12 device, respectively. | ||||||||||||||||||||
-Z, --ditroff | groff will run troff and then use an appropriate post-processor to produce output suitable for the chosen device. If groff -mandoc is groff, this option is passed to groff and will suppress the use of a post-processor. It implies -t. |
Section Numbers
The section numbers of the manual are listed below. While reading documentation, if you see a command name followed by a number in parentheses, the number refers to one of these sections. For example, man is the documentation of man found in section number 1. Some commands may have documentation in more than one section, so the numbers after the command name may direct you to the correct section to find a specific type of information.
The section numbers, and the topics they cover, are as follows:
section # | topic |
---|---|
1 | Executable programs or shellcommands |
2 | System calls (functions provided by the kernel) |
3 | Library calls (functions within program libraries) |
4 | Special files (usually found in /dev) |
5 | File formats and conventions eg /etc/passwd |
6 | Games |
7 | Miscellaneous (including macro packages and conventions), e.g., man, groff |
8 | System administration commands (usually only for root) |
9 | Kernel routines [Non standard] |
Exit Status
When it terminates, man will return one of the following exit status:
0 | Returned upon successful program execution. |
1 | Returned if there was a usage, syntax, or configuration file error. |
2 | Returned if there was an operational error. |
3 | Returned if a child process returned a non-zero exit status. |
16 | Returned if one or more of the pages, files, or keywords searched for did not exist or was not matched. |
Environment
man makes use of the following environment variables:
MANPATH | If $MANPATH is set, its value is used as the path to search for manual pages. |
MANROFFOPT | The contents of $MANROFFOPT are added to the command line every time man invokes the formatter (nroff, troff, or groff). |
MANROFFSEQ | If $MANROFFSEQ is set, its value is used to determine the set of preprocessors to pass through each manual page. The default preprocessor list is system-dependent. |
MANSECT | If $MANSECT is set, its value is a colon-delimited list of sections and it is used to determine which manual sections to search and in what order. |
MANPAGER, PAGER | If $MANPAGER or $PAGER is set ($MANPAGER is used in preference), its value is used as the name of the program used to display the manual page. By default, pager -s is used. The value may be a simple command name or a command with arguments, and may use shell quoting (backslashes, single quotes, or double quotes). It may not use pipes to connect multiple commands; if you need that, use a wrapper script, which may take the file to display either as an argument or on standard input. |
MANLESS | If $MANLESS is set, man will not perform any of its usual processing to set up a prompt string for the less pager. Instead, the value of $MANLESS will be copied verbatim into $LESS. For example, if you want to set the prompt string unconditionally to 'my prompt string', set $MANLESS to ‘-Psmy prompt string’. |
BROWSER | If $BROWSER is set, its value is a colon-delimited list of commands, each of which in turn is used to try to start a web browser for man --html. In each command, %s is replaced by a file name containing the HTML output from groff, %% is replaced by a single percent sign (%), and %c is replaced by a colon (:). |
SYSTEM | If $SYSTEM is set, it will have the same effect as if it had been specified as the argument to the -m option. |
MANOPT | If $MANOPT is set, it will be parsed prior to man's command line and is expected to be in a similar format. As all of the other man specific environment variables can be expressed as command line options, and are thus candidates for being included in $MANOPT it is expected that they will become obsolete. Note: all spaces that should be interpreted as part of an option's argument must be escaped (preceded with a backslash). |
MANWIDTH | If $MANWIDTH is set, its value is used as the line length for which manual pages should be formatted. If it is not set, manual pages will be formatted with a line length appropriate to the current terminal (using an ioctl if available, the value of $COLUMNS, or falling back to 80 characters if neither is available). cat pages will only be saved when the default formatting can be used, that is when the terminal line length is between 66 and 80 characters. |
MAN_KEEP_FORMATTING | Normally, when output is not being directed to a terminal (such as to a file or a pipe), formatting characters are discarded to make it easier to read the result without special tools. However, if $MAN_KEEP_FORMATTING is set to any non-empty value, these formatting characters are retained. This may be useful for wrappers around man that can interpret formatting characters. |
MAN_KEEP_STDERR | Normally, when output is being directed to a terminal (usually to a pager), any error output from the command used to produce formatted versions of manual pages is discarded to avoid interfering with the pager's display. Programs such as groff often produce relatively minor error messages about typographical problems such as poor alignment, which are unsightly and generally confusing when displayed along with the manual page. However, you might want to see them anyway, so if $MAN_KEEP_STDERR is set to any non-empty value, error output will be displayed as usual. |
LANG, LC_MESSAGES | Depending on system and implementation, either or both of $LANG and $LC_MESSAGES will be interrogated for the current message locale. man will display its messages in that locale (if available). |
Files
The following files are used by man:
/etc/manpath.config | The man-db configuration file. |
/usr/share/man | A global manual page hierarchy. |
/usr/share/man/index.(bt|db|dir|pag) | A traditional global index database cache. |
/var/cache/man/index.(bt|db|dir|pag) | An FHS compliant global index database cache. |
Examples
View the manual page for the man command.
View the manual page for man, with no hyphenated words or justified lines.
Related commands
apropos — Search the manual pages for a keyword or regular expression.
info — Read Info documents.
whatis — Display short manual page descriptions.
info — Read Info documents.
whatis — Display short manual page descriptions.
What is a User Guide? A User Guide explains how to use a software application in language that a non-technical person can understand. In general, user guides are part of the documentation suite that comes with an application for example, Data Sheets, Release Notes,Installation Guides andSystem Administration Guides.
Technical Writers will often create a Documentation Plan before writing their user guide. This defines the scope, size, delivery format and resources required to produce the actual user guide.
As the name implies, User Guides are written to help people understand an software application or IT system. They are also called User Manuals. When writing a User Guide, use simple language with short sentences. This writing style helps the user understand the application.
Our User Guide templates can be used to create user guides, user manuals, getting started guides and other types of technical documents. A User Guide is an online or printed book that describes how to use a software application.
User Guides are the first port of call when something needs to be read. As many people read user guides when frustrated and after having lost patience with the software, you need to write your material to address their concerns quickly.
User Guides are often written for non-technical individuals. The level of content and terminology differs considerably from, for example, a System Administration Guide, which is more detailed and complex.
This rest of article offers some guidelines to consider when writing your User Guide, such as:
- Identifying your audience
- Writing sections
- Defining style guide and standards
- Delivery formats
Identifying Your Audience
As with all types of writing, the first step is to define your TARGET AUDIENCE. Your target audience are the people who will user your document. As different readers have different requirements, you need to consider their specific requirements. Use this template to learn more about the target audience for your projects and what they want to achieve, for example, read your user guide, visit your website or buy your product.
The worksheets include 130 points you can use to capture demographic date so that you have a more holistic view of their wishes, desires, fears, and preferences.- Identify the target audience
- Identify their level of technical knowledge
- Identify how they will use the guide
Audience Definitions
In the planning process, develop an audience definition that identifies:
- The user
- The system
- The tasks
Software is used to do specific things. Users want to know what the software can do for them, for example, how to print a page in landscape.
They are generally not interested in the nitty-gritty technical details; they want to click a button and get a result. The User Guide is to teach them how the software helps them to do something.
Depending on the guide in question, you may need to address several audiences. For example:
- Programmers who will troubleshoot the program
- IT Managers who want to know the resources the program requires
- Project Managers who want to confirm that the original requirements were met.
If you are writing for more than one audience, develop an audience definition for each one. Examine the definitions and see if you can address all audience types with one document. In many situations, you may need to write a number of documents, of which the users guide is only one.
- When planning, use the audience definition to focus your decisions.
- When writing, the audience definition serves as a guide for the documentation team and as a benchmark for evaluating the results.
Here are some questions that will help define your audience's needs:
- Where will they use the document, for example, in the office, at home, in their car?
- How much experience have they of using your application?
- Is this guide an upgrade to an existing application?
- Is your application new? If so, you may want to include a Getting Started document to introduce the software.
- How will they use the user guide?
- Will they install the software by themselves or do so over the internet?
- What level of detail is required?
- Will graphics help their understanding of how to use your product?
Writing the User Guide
Each user guide is comprised of front page, body sections, and a back page. The following section describes what each of these needs to contain.
Front Page (cover pages)
Include a cover page, table of contents, and a preface, if necessary.
Cover and Title Page
If the user guide is copyrighted, include a copyright notice.
Copyright © 2020 The Name Of Your Company.
Place the copyright notice on the cover (and also the title page).
Disclaimer
Include a standard disclaimer inside the front cover that outlines the Terms and Conditions for using this guide.
Preface
Use this section to reference other documents related to the software. Make sure you refer to the correct release number for all software and documents that you refer to. If necessary, include a section on 'How to use this guide' as an introduction.
Contents
You must include a table of contents. the only exception is if your guide is less than ten pages, in which case you should probably refer to it as a Getting Started guide or Reference Guide.
If this user guide is more than twenty pages, include an index at the end of the document.
Body of the guide
This is the heart of the guide. In the main body, separate the procedures (also called instructions) from reference materials. This will help the user navigate their way through the guide much faster.
Procedures
Procedures help the user perform specific tasks. They are also known as instructions or tasks. Examples of these may include:
- When, why, and how you can perform a task, for example, printing a document, cropping an image, uploading a file.
- What the screen will show after you perform a task, for example, an updated view of your bank balance.
- Examples of tasks and program operation.
Writing procedures
Writing procedures involves the following tasks:
- Identifying the major tasks
- Separating each major task into subtasks
- Writing a series of steps that walk the user through each subtask
- Using an 'if-then' approach when explaining decisions that users can make.
Chunking text
Breaking large pieces of information into smaller piece of information is called 'chunking.'
When writing user guides, you can separate information by menu options and their respective consequences, for example, showing the user the results of each action.
Subtasks that need to be performed can be divided into chunks. Each chunk can form a new chapter or section within the guide.
Use a consistent format for each section, for instance:
- Introduce each section with an overview of the task to be performed
- Describe the inputs and outputs. In other words, what the user must enter into the system and what the system will do as a result.
- Describe the procedures for accomplishing these tasks.
Number your steps
When writing procedures, number each step and use the imperative form of verbs, for example:
Press ENTER
User Manuals Are An Example Of Information Utility Management
or
Click 'Yes' and press ENTER to submit your details.
Using the If-Then Approach
When users are allowed to make decisions, use an If-Then approach to show the different result for each decision they make.
If you choose 'Yes,' the program will make Firefox your default web browser. If you choose 'No,' it will set Opera as your default browser.
Use diagrams to illustrate more complicated procedures.
Reference Materials
User turn to reference material when they need detailed information on a specific topic, for example, settings or parameters they must enter.
Reference materials can include:
- Program options, for example, different menus and buttons that are presented to the user
- Keyboard options, for example, hold AltGr and 4 to show the Euro symbol
- Error messages that may arise when you use the application
- Troubleshooting tips to resolve these issues
- Frequently asked questions that the user may have about the software
Back Matter
Add a Glossary of Terms and an Index towards the end of the document.
Glossary
The glossary should cover all acronyms and industry terms used in the document. Help the user understand your material. Do not alienate them by using jargon and assuming that they know the meaning on these words.
- A short glossary can appear at the front before the table of contents
- A larger glossary should appear in the back matter.
Highlight glossary terms (by italics, for instance) the first time they appear in text.
Index
Any guide longer than 20 pages benefits from an index. An index helps users locate specific items very fast without having to search through the entire document manually. Large documents without an index are impossible to use efficiently.
Establishing Standards
As well as writing the guide, you also need to consider how the document will be delivered, for example, as a book, online or a PDF.
Areas that need consideration include:
- Format (the design and layout of the pages)
- Style (elements affecting readability, such as font, size, color)
- Other requirements that are specific to each delivery format. For example, PDFs may need security settings applied so material cannot be copied; partner logos may need to be added; terms and conditions may need to be updated.
User Manuals Are An Example Of Information Utility Bill
Document Format and Structure
If you are writing a user guide for a client, rather then your own company, check if they use a specific style guide or have a preference for how the document should be presented. Check this with the client during the planning phase.
Use a document map to organize the guide. To do this:
- Use headings for organizing information.
- Include page numbers and section titles on every page, either in footers or headers.
- Consider using dual columns. This lets you put headings in the left-hand column and the text in the right-hand column.
Style
Use an appropriate style. Decide on the technical level of your language, how you address the user, and conventions that are required.
Technical Language
Match the level of technical language with the audience ¯s level of proficiency. Always underestimate the knowledge of your readers rather than overestimate it.
Limit technical terms to those the user will encounter. If you must define a large number of terms, use a glossary to supplement definitions in the text.
Addressing the User
When writing procedures, use the active voice (e.g. Click this) and address users directly (write 'you' rather than 'the user').
When explaining an action, use the 'command' form of the verb:
'Choose an option from the menu and press [ENTER].'
Presenting your material
You can improve the readability of your documents by using specific formats to distinguish different types of information.
For example, you can distinguish the user's input from the system's response by:
- Indenting text
- Using columns to layout text
- Providing illustrations or photographs that highlight key areas
- Using different fonts and type features (bold, italics and underline)
Nonverbal devices, such as icons or diagrams, help supplement verbal instructions.
Example Of Information System
Special Requirements
If the guide is to be used outdoors, in a car, or on the move, make sure the font size is large enough to read easily.
Use spiral biding so the book does not to break easily, and high-quality paper so the text does not smudge or leave stains on the reader's hands.
PS - Download the User Guide Templates here