Corrections
What we do when we get something wrong, and the record of when we have.
Last updated
The policy
We fix errors in the article and log them here. We do not silently edit a page and let the mistake disappear, because a reader who acted on the wrong figure deserves to be able to find out that it was wrong.
Three categories, treated differently:
- Correction — a factual error. The article is fixed, a note is added to it, and an entry appears in the log below.
- Update — a vendor changed its price or plans and we re-read it. The "Updated" date moves. No log entry, because nothing was wrong at the time.
- Clarification — the facts were right but the wording invited a wrong reading. Fixed in place, noted if the misreading was material.
What counts as material
A wrong price is never cosmetic. Any error in a price, seat limit, free-tier cap, licence or feature claim that a reader might act on gets a logged correction, however small the slip that caused it.
Fixing a misspelled surname or a broken link is housekeeping, and we do not pad the log with it.
Reporting an error
Write to editorial@stackfeature.com with the URL and the specific claim you believe is wrong. Tell us what the correct figure is and where you got it if you can — it makes the check much faster.
Reports about live prices are checked first, since those are the ones someone may be budgeting from.
The log
No corrections have been logged yet. Stackfeature began publishing in 2026, and this page exists from day one so that the first correction has somewhere to go.
An empty corrections page on an established site is not a sign of accuracy. It is a sign that errors are being handled quietly. Judge this page again in a year.