The record should
stand up to scrutiny.
Accuracy is an ongoing responsibility. Corrections should be visible, specific, and tied to the evidence.
Our corrections policy
Readers can flag factual, sourcing, and translation errors using the form below or the correction form on an article. Identify the passage, explain the problem, and include a supporting source when possible.
How a correction is assessed
Submitting the issue on GitHub creates a public correction request. Continuing from this website only prepares a draft. It does not automatically change an article. The passage should be checked against the underlying source and relevant corroborating evidence. A submitted correction is not a guarantee of a response.
How changes should be recorded
Substantive corrections should appear in a dated note on the affected article explaining what changed and why. Updates that add new information should be distinguished from corrections that repair an error. Translations should be corrected alongside the English source where relevant.
Translation concerns
Machine translations are explicitly marked as unreviewed. Please name the language and include the original passage and suggested wording. Do not submit private identifying details about victims or sources.