Corrections

How we handle corrections

Different kinds of errors get different treatment, and we think the difference matters.

Silent corrections

Typos, broken links, formatting glitches, and minor clarifications that don't change the meaning of the article are corrected without an inline note. The article's last-modified date is bumped.

Inline corrections

Substantive factual errors — wrong KB number, misstated registry path, incorrect behaviour description, outdated fix that no longer works — get an inline note at the point of correction, dated, explaining what was wrong. The freshness badge is also updated.

Retractions

If an article rests on a premise that turns out to be wrong, we retract. Retracted articles get a notice at the top, the original text remains visible (struck through or in a collapsible block), and a follow-up article explaining what we got wrong is published.

What to include in a correction request

• The URL of the article.
• The specific passage you believe is wrong (a quote or a section heading is enough).
• What you believe the correct information is.
• A source we can verify against, if you have one.

You don't need to be polite — we just need the facts. We don't shoot the messenger and we don't argue with people who are right.

How to submit a correction

Email: [corrections email — to be configured by operator]

Please put "Correction:" at the start of the subject line so the editorial inbox routes it correctly.

What we won't correct

We won't change editorial opinion or recommendation in response to vendor pressure. If we say a tool is overkill for a given problem, no amount of vendor outreach will persuade us to soften that line — though we will publish a fair right-of-reply where the facts warrant it. Editorial judgement is the product. We're not going to erode it.

Recent corrections

A public log of substantive corrections will be published here once the site has accumulated any. We will not retroactively erase corrections from this log.

---

This page will be expanded with the operator's working corrections email and the running corrections log.