Corrections Policy and Log
How we handle verified mistakes · Every correction is logged below with the date and what changed
Why Corrections Matter Here
This site tells people what their devices are telling them, sometimes about life-safety hardware like smoke alarms. A wrong answer is worse than no answer, so we treat verified mistakes as urgent: a correction that changes what a reader should do gets made the same day it is confirmed.
How to Report an Error
Report Through the Contact Page ~2 min
- Open the contact page.
- Include the page URL, the specific claim you believe is wrong, and, if you have it, the source that contradicts it (a manufacturer support article, a manual page, or your device’s actual behavior with model and firmware version).
- Send it. You do not need an account or an email address of your own; the form is enough.
What Happens After
Every report is checked against the manufacturer’s current official documentation. If the site is right, we reply explaining the sourcing. If the site is wrong, we correct the page, update its “last verified” date, note what changed in the correction log below, and, where the fix affects a documented behavior on other pages, sweep those pages for the same mistake.
Correction Log
| Date | Page | What Changed | Why |
|---|---|---|---|
| No corrections issued yet. When one is, it will appear here with the date, the page, what changed, and the source that prompted it. | |||
Undocumented Behavior Is Not an Error
Some readers write in because a page says a behavior is “not documented by the manufacturer” while their own device does something specific. That is the intended state of the page: we only state what the manufacturer documents, and mark the rest as unknown. If you report undocumented behavior, we note it as reader-reported evidence and it can earn a place on the page once corroborated, clearly labeled as such.