Correction log checklist for pages that readers may reuse

A reusable page needs a correction log when a changed claim could alter a reader’s decision, implementation, or citation.

The first checklist item is impact. Ask whether the old sentence could have changed what someone did. A typo rarely needs a correction note. A changed deadline, compatibility status, eligibility rule, safety warning, API behavior, or legal reference usually does. The correction log is for meaningful movement, not every edit.

The second item is source. Record which source caused the change. If an official page changed, link or name that source. If a reader reported the issue, say that the page was revised after reader feedback and then name the source used to verify the fix. Avoid vague phrases such as “updated for accuracy” when the update changes a practical conclusion.

The third item is the old and new claim. These can be short. The reader does not need a full diff, but they do need to know whether the page became stricter, looser, broader, narrower, or simply clearer.

The fourth item is date. The date of correction is different from the date the source was originally checked. Keep both when timing matters. A page can have an old source check and a recent correction, or a recent source check with no correction.

The last item is follow-up. If the correction implies related pages may also be stale, record which pages need review. That prevents one fixed page from hiding the same error elsewhere.

Correction log checklist for pages that readers may reuse

// COMMENTS

ON THIS PAGE