Documentation review
Documentation pages on Documentation review (5 pages).
This topic brings together 5 pages across the manual:
Checklist: technical review
ReferenceLearning path: 5. Build your toolkitChecklists
A checklist for the subject-matter expert reviewing a documentation change for technical accuracy - what to check, and what's explicitly not their job.
Learning path: 5. Build your toolkitWorked examples
A worked example of a single documentation change moving from branch to merge under a docs-as-code workflow, mirroring a standard code review flow.
Learning path: 5. Build your toolkitWorked examples
A worked example of routing a documentation change through technical and editorial review before publication, with clear, separated responsibilities.
Learning path: 5. Build your toolkitTemplates
A ready-to-copy request template for asking a subject-matter expert or technical reviewer to review documentation changes, with a clear scope and deadline.
Learning path: 2. Build a documentation process
Validate technical documentation before delivery: run validation in parallel with writing, track every change request through a CMS workflow or a ticketing system, and use comparison tools to review updates reliably.