Check the promise before the prose
Ask whether the page still solves the job named by its title. A polished explanation can be stale when the product path, prerequisite, response, or next step has changed underneath it.
- Run the procedure against the current product.
- Test copied commands and expected responses.
- Verify screenshots, labels, limits, and availability.
- Follow every internal and external link.
Compare against change evidence
Review repository history, release notes, OpenAPI diffs, support themes, failed searches, and reader feedback since the last confirmation. Recency alone cannot reveal what changed; these signals can.
Close the loop explicitly
Record the reviewer, the evidence considered, and the next review rule. If the page is wrong, publish through the usual approval flow. If it is correct, confirm it without manufacturing an edit just to change a date.