Corrections
We work hard to get every fact right, but we will make mistakes. When we do, we fix them in the open. This page explains how to tell us and what happens next.
How to report an error
Email [email protected] with "Correction" in the subject line, and include:
- The page. Paste the link.
- The statement. Copy the sentence, number or step you think is wrong.
- Why. Tell us what you think is correct. A link to a manual, data sheet or code section helps us check it fast.
You don't need to give your name. If you do, we won't publish it without asking you.
What happens next
- We read every report.
- We check the claim against the source: the manual, data sheet or standard.
- If we were wrong, we fix the page.
- If we think the page is right, we reply and explain why.
We aim to reply within a few business days.
Safety errors come first. If an error could get someone hurt, we fix it as soon as we confirm it. If we can't fix it right away, we take the page down until we can.
What we change, and how we show it
| Type of error | What we do | Where it shows |
|---|---|---|
| Typo, grammar or a broken link | Fix it | Not logged |
| Wrong fact, number or spec | Fix it and add a dated note | The page's change log |
| Wrong or missing safety step | Fix it, add a dated note and log it here | The page's change log and this log |
| Wrong verdict (the main answer changed) | Fix it, add a dated note and log it here | The page's change log and this log |
We don't quietly rewrite a page to hide a mistake. The note says what was wrong and what we changed.
Corrections log
Material corrections are listed here, newest first.
| Date | Page | What was wrong | What we changed |
|---|
No corrections yet.
Related
- Our editorial policy explains how we source and check facts.
- How we research and check our guides explains where our facts come from.
Change log: Nov 7, 2026: Reports by email only for launch. Nov 6, 2026: First version. Log starts empty.