Corrections standard
Corrections Policy
Corrections should make published stories more accurate and useful without hiding what changed or creating unnecessary new URLs.
Correction categories
We prioritize factual issues, broken links, missing attribution, outdated practical details, privacy concerns, and errors that could mislead readers.
Style preferences and broad rewrite requests may still lead to better wording, but they are not treated as factual corrections by default.
How to request a correction
Send the article URL, the exact issue, the paragraph or caption involved, and the source or context that helps verify the request.
Review workflow
Editorial messages are reviewed by priority. Factual corrections, privacy concerns, broken pages, and date-sensitive reader safety issues are handled before general suggestions.
How accepted corrections appear
Accepted corrections should update the article in place, preserve the canonical URL, and use the article's modified timestamp when the change affects reader understanding.
What may be declined
Requests may be declined when the article is already accurate, the source is unsupported, the change would remove useful context, or the request is mainly promotional.
Urgent or broken-page issues
If an article, hub, image, or internal link is broken, send the URL through the contact page and mention that it is a public page issue.
What we check before changing a page
A correction should improve the published record for future readers, not only satisfy a preference. We check whether the requested change is factual, whether it affects meaning, and whether it needs an article update, caption update, metadata change, or internal-link fix.
When a correction touches a date, place, route, technical concept, or product workflow, the review should preserve enough context that readers understand why the update happened.
When a note becomes a larger update
Some messages reveal that a story needs more context rather than a small correction. In that case, the article can be expanded while keeping the same canonical URL and a clear modified date.
Reader-visible transparency
Small typo fixes may simply improve the page. Larger corrections should leave the article more understandable for the next reader, with updated context, stable internal links, and a modified date when the change affects meaning, timing, attribution, or practical guidance. The goal is a better public record, not a hidden rewrite, so future readers can trust what changed and why. Readers should also be able to trace the corrected article from the same old link.