Freebie

Quality docs

Drafts

The purpose of a rough draft is to figure out which parts you understand well enough to document, and which parts you need to research.

Titles

  • Tasks: Use the verbal form: Installing, configuring,…
  • Concepts: Use concrete words that summarize the concept.
  • Referece: Noun or noun phrase that indicates the name of the item and a common noun.
  • Troubleshooting: State the problem that the topic addresses. For example, Cannot connect to the server.

Tasks

Focus on user goals

User-oriented tasks

A user-oriented task is a task that users want to perform whether or not they are using your product. For example, “Trimming strings” rather than “Using the string package to trim strings”.

A task that starts with “Using” or “Working” is a function-oriented task.

A task is an activity that users do, and a goal is an outcome that uses want. To make sure you are focusing on goals, find scenarios. A scenario is a story that shows how a product contributes to solving a business problem. You define key goals for a product, then create a scenario (or path) that helps a user accomplish the goal.

To identify the tasks that are associated with a goal, start with a high-level task and then get more granular:

  1. Identify your users.
  2. Evaluate their goals.
  3. Determine the tasks that those users need to do with your product to meet their goals.
  4. Evaluate to make sure that users have the content to achieve their goals regardless of how or with what product they do so.

Introductions

Users need to understand why you are giving them task information. Give practical reasons.

Steps

Substeps

When a step has substeps, the top-level step should indicate the purpose of the step. Use an action verb:

  1. For each application, configure the client to send data to the server:
    1. Install the…
    2. Open port number…

Optional or conditional steps

The best place to tell users that a step is optional is at the beginning. Conditional steps usually begin with “If”:

  1. (Optional) Set default values…

Concepts

Concept topics provide the necessary vocabulary and context for what users are doing.

Troubleshooting

Troubleshooting documentation must include the following sections:

  • Symptoms of the issue
  • Potential causes of the issue
  • How to resolve the error situation

Structure

Introduction
Define the concept and explain its value to the user.

Revising

You acheive clarity when you revise. Rewriting is when you replace, add, or delete parts of your draft.

Long gerund phrases

Do not begin your sentence with a long gerund phrase:

Original

Importing data with a CSV file from the database is required if you do not connect to the API.

Revision

It takes too long to get to the empty verb is. Instead replace with a straighforward subject and verb. Here, the subject and verb appear after an introductory phrase that indicates a condition:

If you do not connect to the API, [you must import] data…

Long coordinated phrases and clauses

Writing becomes unclear when you string together too many sentences with coordinating conjunctions. Break them up into smaller sentences.

An indication that you need to break up sentences is when you join too many ideas with or.

Too many modifying phrases or clauses

If you have too many relative clauses (who, which, or that), create multiple sentences from the original:

Original

Use the grep command that searches text files recursively to find the string.

Revision

Use the grep command to find the string. It can search text files recursively.

Convert prepositional phrases to clauses

Prepositional phrases can modify a sentence too much. It can make the sentence difficult to comprehend. The following example converts a prepositional phrase to a clause.

Original

To handle long response times (during periods) (of heavy traffic) (on our APIs), the developers looked through the source code (in the company’s repository).

Revision

To handle long response times when API traffic was heavy, the developers looked through the source code.

There is/are

This construction is called an expletive. It is usually paired with a relative clause that uses “are” as well: “There are … that are…”.

To revise, just remove the expletive and relative pronoun.

Original

There are several types of servers that are applicable to your environment.

Revise

Several types of servers are applicable to your environment.

Simpler words

Many complicated words are derived from Latin. Replace latin words with words or phrasal verbs derived from Anglo-Saxon:

Latin-derivedAnglo-Saxon replacement
acceleratespeed up
accomplishdo
acquireget
alignline up
anticipateexpect
approximateabout, roughly
attempttry
completefinish, fill in, fill out
configureset up
considerthink about
construct,fabricatemake
deferput off
demonstrateshow
disconnectcut off
discoverfind, realize
distributegive out, send
documentationdocs, help text
enumeratelist
excludeleave out
evidentclear, plain
functionalityfeatures, ability
generatemake
implementdo, build, put in place
indicateshow, point out
initiate, commencestart, begin
investigatelook into
locatefind
maintainkeep, upkeep
modifychange
notifytell
optimizemake better, tune
performdo
possesshave
providegive
presentgive, show, tell
requireneed
retainkeep
reviewlook at
specifystate, set
sufficientenough
terminateend, stop
transmitsend
utilizeuse
validatecheck, make sure
verifycheck

“that” in relative clauses

Always use “that” in a relative clause. It helps with translation and helps clarify how parts of the sentence relate to each other.

Original

Each error message explains the issue it addresses.

Revision

Each error message explains the issue that it addresses.

Parentheses

Periods go inside parentheses when what is inside the parentheses is a complete sentence.

Lists

Follow these steps:

  • Use a complete sentence for the lead-in sentence.
  • Start each list item with a capital letter unless the first word is never capitalized.
  • Do not nest more than two levels