How to write a correction note that does not bury the old mistake

A correction note should state what changed, what was wrong, when it was corrected, and which source now supports the updated claim.

Quietly editing an article can fix the text but damage the source trail. Later readers may still have copied the old version, linked to it, or made a decision based on the earlier claim. A correction note keeps the record usable by showing the path from mistake to update. It does not need to be dramatic, but it should be visible enough that a careful reader can understand the change.

A good correction has four parts. First, name the affected claim. Second, describe the old problem without overexplaining. Third, cite the new source or test. Fourth, give the correction date. For example: “Corrected plan limit from 5 projects to 3 projects after checking the vendor pricing page on June 25, 2026.”

The note should avoid blame language unless accountability is relevant. Most corrections are maintenance: a source changed, an earlier interpretation was incomplete, or a screenshot became outdated. The goal is to preserve trust by making the update traceable.

Do not bury the note in a hidden changelog if the mistaken claim was central to the article. Put a short correction near the affected section and a longer note at the end if needed. Readers should not have to compare old versions manually to know what changed.

How to write a correction note that does not bury the old mistake

// COMMENTS

ON THIS PAGE