Corrections policy and log
Technical writing about a moving target produces errors. What matters is what happens next.
What counts as a correction#
| Change | Logged as a correction | Page date updated |
|---|---|---|
| A factual claim was wrong (wrong version, wrong behavior, wrong number) | Yes | Yes |
| A recommendation was based on a mistaken fact | Yes | Yes |
| A dataset row was inaccurate | Yes | Yes |
| A feature shipped, a spec was updated, a product changed | No | Yes |
| Typo, broken link, clearer wording, added example | No | Yes |
Where an error changed the advice a page gave, the correction notice stays visible on the page itself, not only in this log.
How to report an error#
Send the page URL, the sentence you believe is wrong, and, if you have one, a link to the documentation that shows the correct answer. Specification section numbers and vendor support pages get handled fastest. Email corrections@smartlivingweb.com, or use the contact page.
We read every report. We respond to reports that include a source. We do not publish reader submissions as content.
Log#
No corrections have been logged yet on the current set of pages. Entries will appear here with the date, the page, and a plain description of what changed.