Corrections Policy

What counts as a correction

• Factual error — a statement that is materially inaccurate, including statistics, attributions, dates, or quoted claims.
• Outdated guidance — advice that no longer reflects current product behaviour, model capabilities, or platform policy.
• Broken functionality — a documented feature that does not work as described.
• Misleading framing — language that, while technically defensible, leaves a reasonable reader with the wrong impression.

How we correct

Small, non-substantive edits — typos, clarity tweaks, formatting — are made silently. Substantive corrections are made in place with a dated note explaining what changed and why. If a claim is materially wrong, we strike the original wording rather than quietly rewriting history.

Speed

We aim to acknowledge correction requests within two business days, and to resolve straightforward factual fixes within five. Larger investigations — a research note, a benchmark, a model claim — may take longer; we will say so explicitly rather than go silent.

How to report

Send the URL, the specific passage, and the correction you believe is needed (with a source where possible) through the contact page. We read every message, and we credit constructive corrections when the contributor wants to be named.