For technical writers and developer advocates

A second read for documentation people depend on.

Technical documentation has a practical obligation: a reader should be able to learn a concept, complete a task or look up a precise detail without guessing what the author meant.

Second Read reviews documentation through a documentation-specific editorial pathway. It considers the job the document is meant to do, the order in which readers encounter information, and whether instructions, terminology and explanations support that job.

What the writing has to achieve

A reader arrives with a task or a question. The page should get them to the result, with prerequisites, exact syntax and terms in the order they are needed.

Where drafts tend to go wrong

  • A prerequisite appears after the step that needs it.
  • A term is used before it is introduced.
  • A tutorial tries to cover every option and loses the learner.
  • A friendlier synonym replaces an exact parameter name.
  • A README does not route readers to the right next document.

Different documents, different editorial questions

Tutorials
Guide a learner through a supported experience. The sequence should help the reader learn, not overwhelm them with every possible option.
How-to guides
Help someone who already has a goal. Prerequisites, steps and success criteria should be clear.
Reference
Supports lookup. Names, options, defaults, allowed values and behaviour need precise descriptions.
Explanations
Provide concepts, background and trade-offs, so readers understand why a system works as it does.

Questions a second read asks

  • Does the page's structure match its intended documentation type?
  • Does each prerequisite appear before the reader needs it?
  • Is terminology introduced before it is used?
  • Does any step depend on information the reader has not received?
  • Do headings describe the task or concept that follows?
  • Do product claims have a traceable source in supplied project material?

How Second Read approaches it

  • A documentation-specific pathway that distinguishes tutorials, how-to guides, reference and explanation, and applies a single documentation house style.
  • The product-verification reference for checkable product behaviour, which keeps source inspection, runtime observation and missing evidence distinct.
  • Every suggestion is anchored to the exact passage, explains its reasoning and waits for your decision. When a passage already works, no change is a valid result.

In Studio, choose a writing type such as Documentation (README, tutorial, how-to, reference) or Release notes / product update to route the review to its focused reference.

Synthetic example · the draft

Worked example

A how-to guide tells readers to run a command that requires an access token, but the token prerequisite has not been introduced.

What a useful review does

A useful review anchors the issue to the command and points to an approved setup source if one exists. It does not invent a token name or a successful output.

What Second Read does not claim

  • Editorial consistency is not technical verification: a clear sentence can still describe a command incorrectly.
  • Repository inspection can corroborate source-level details; it does not prove deployed behaviour.
  • Second Read does not replace a subject-matter expert, a test environment or a release-specific verification process.

Read more about the method in how Second Read reviews a draft.

Related guides

Try it on your own terms

See a second read before you apply.

The interactive demo uses a sample review and needs no account. The beta is free and applications are reviewed personally.