Corrections Policy

Something on this site will be wrong at some point. Patches move limits, interfaces get redesigned, and occasionally we simply misread a source. None of that is avoidable. What happens next is entirely a choice, and this page is the choice written down.

The principle

A site that has never published a correction is not a site that has never made a mistake. It is a site that fixes things quietly, or does not fix them at all. Silent editing is the more common of the two, and it is worse than it looks: it leaves no way to tell whether the version you are reading now is the third attempt or the first.

A correction that nobody can see is not a correction. It is a repair with the receipt thrown away.

So corrections here are dated, described and left in place. If a guide changed because someone caught an error, the page says what was wrong, what it says now, and how long the wrong version was live.

How errors are graded

Not every mistake deserves the same treatment. A typo and a wrong ladder limit are both errors, but only one of them can cost you forty divines. Everything reported gets sorted into one of four levels, and the level determines both the speed and whether a public note gets added.

Level 01 Material

Wrong in a way that changes what you would do

A wrong figure, a wrong limit, a step that does not work, or a source cited as saying the opposite of what it says. Anything a reader could act on and lose something by acting on.

48 hours From confirmation. Dated correction note added and kept permanently.
Level 02 Superseded

Accurate when written, not accurate now

A menu that has moved, a setting that was renamed, a figure a patch has since changed. Nobody got it wrong, but the page no longer describes what is on your screen.

Next review Sooner if reported. Updated date shown, plus a note where the old version could have misled someone.
Level 03 Unclear

Not wrong, but easy to misread

Ambiguous wording, a missing caveat, an example that does not quite land. The facts hold up; the writing does not do them justice.

Rolling Edited as spotted. No note, because nothing false was published.
Level 04 Cosmetic

Typography, links and formatting

Spelling, grammar, a broken link, a table that has come apart on mobile. Worth fixing, not worth a paragraph about it.

Rolling Fixed whenever noticed. No note.

What a correction actually looks like

Policies about transparency tend to describe transparency rather than demonstrate it. Here is the exact component that appears on a corrected guide, rendered as you would see it.

As it appears on a corrected page

Correction

This guide previously stated that a Path of Exile 2 ladder returns the top 5,000 entries. The correct figure is 1,000, per the official developer documentation. The section on missing characters has been rewritten to match.

The incorrect figure was live from 2 August to 12 August 2026.

Reported by a reader. Verified against the official API reference.

Four things are always present, and each one is there because leaving it out is how corrections get used to quietly rewrite history.

What it said before Stated plainly, not implied. A note that only gives the new version tells you nothing about what you may have already acted on.
What it says now, and why The corrected claim with the source that settles it, so the fix is checkable rather than asserted.
How long it was live The window matters. An error up for two days and one up for six months are different problems.
Where it came from Reader report, our own review, or a patch. Credit where a reader wants it, none where they do not.

What will not be changed

Corrections fix errors of fact. They are not a route to editing the site into a different shape, so a few things are off the table regardless of who asks.

  • Disagreement is not error. If the facts are right and you think the judgement is wrong, that is a comment rather than a correction. It may still change the guide, but it will not be logged as a mistake.
  • Accurate information does not come down because someone dislikes it. That includes anything unflattering about a tool, a build, or the limits of the data behind them.
  • Pages are not deleted to make errors disappear. A URL that has been wrong is more useful with a correction on it than gone.
  • Nothing is backdated. A correction carries the date it was made and the window the error was live, even when that window is embarrassingly long.
  • Corrections are not traded. No link, payment or relationship changes whether something gets fixed, or how quickly.

Retired and rewritten guides

Sometimes a guide is not wrong so much as finished. A mechanic gets removed, a feature is retired, a whole league system is replaced. Those pages are not deleted either.

They are marked as retired, with the date and the reason, and left in place so that every link pointing at them keeps working. If a guide has been rewritten heavily rather than corrected, the page says that too, because a reader who bookmarked the old version deserves to know it is not the same article any more.

Credit

If you report something and want your name or handle on the correction note, say so and it goes on. If you would rather stay anonymous, that is the default. Either way the note records that the error came from a reader rather than from our own review, because those are genuinely different things and readers deserve the credit for the first one.

Reporting an error

One specific claim, one link, and how you know. That is enough. The contact page has a template if you want one, and the sources policy explains what counts as evidence when a report is checked.

Report an error Sources policy Editorial policy
Lost your password?