Corrections & updates
The record should change when the facts do.
Material factual errors, meaningful data revisions, final implementation details, and later evidence that changes an article’s conclusion should be corrected visibly. This page reads explicit correction and update notices from published WordPress Posts and adds them to the public log automatically.
A factual mistake that changes a reader’s understanding of the policy, evidence, scale, timing, or conclusion.
A later official action, revised dataset, court decision, or verified development that changes the available record.
A wording change needed to prevent a reasonable but unintended interpretation of the original article.
Correction policy
Correct visibly. Explain specifically. Preserve the timeline.
The purpose of a correction is not merely to replace a sentence. It is to tell readers what was wrong, what is now accurate, and whether the change affects the article’s broader analysis.
Identify the affected article and claim.
The notice should make clear which fact, number, characterization, date, quotation, scope statement, or analytical conclusion changed.
State the corrected information.
Use direct language. Do not hide the correction inside vague wording such as “this article has been updated” when readers need to know what changed.
Explain the reason.
Distinguish an original reporting error from a later data revision, newly released official document, corrected agency statement, or development that occurred after publication.
Address the conclusion.
Say whether the correction changes the article’s central analysis, changes only a supporting detail, or leaves the conclusion intact.
Date the notice.
Keep the original publication date visible and add the date of the correction or substantive update. Silent replacement is not sufficient for a material change.
Live corrections log
Published corrections and substantive updates.
The log recognizes the structured TED notice type and notice text fields, explicit data-ted-correction or data-ted-update blocks, and article sections labeled Correction, Update, Clarification, or Editor’s note.
Scanning published articles for explicit notices…
What is not normally logged
Not every edit changes the record.
Routine maintenance can be handled without a formal notice when it does not alter the meaning, evidentiary basis, or conclusion of the article.
Spelling and grammar.
Typographical errors, punctuation, capitalization, spacing, and other non-substantive copy edits may be corrected silently.
Links and formatting.
Broken-link repair, accessibility improvements, visual formatting, and code changes that do not affect the article’s substance are not correction events.
Equivalent supporting material.
Adding a mirror, archived copy, transcript, or easier-to-read version of an already cited record does not require a notice unless it changes the claim.
Submit a correction
Specific evidence receives the fastest review.
A disagreement with an editorial conclusion is welcome, but a correction request should identify a verifiable error or a primary record that materially changes the article.
Include the article URL.
Identify the exact page and, when possible, quote the sentence or claim at issue.
Explain the alleged error.
State what is inaccurate, incomplete, misleading, outdated, or unsupported.
Provide the strongest source.
Link the official document, dataset, transcript, research paper, or other record that supports the correction.
Separate rebuttal from correction.
A substantive counterargument may merit a response or article update even when the original factual statement was not erroneous.
Accountability includes accountability for the publication.
Inspect the evidence standards and the source directory used to support the publication’s arguments.