Corrections

Reporting a problem

Email corrections@fpsing.com. To help us act quickly, include:

• The article URL.
• The specific sentence or claim that is wrong.
• What it should say, if you know.
• Anything that supports that — a patch note, a developer post, a clip, or simply “I tested this and here is what happened”.

You do not need to prove your case to report something. If you think a guide is wrong, tell us and we will check.

We aim to acknowledge reports within two working days. Verified errors are corrected as soon as we have confirmed them.

How corrections are displayed

We treat three kinds of change differently.

Material corrections

A factual error that could have led a reader to act wrongly — an incorrect requirement, a wrong recommendation, a misattributed statement. These are:

• Fixed in the article body.
• Marked with a dated correction note at the foot of the article stating what was wrong and what it now says.
• Reflected in the article’s updated date.

We do not silently edit a material error out of existence. The note stays up.

Clarifications

Where something was accurate but ambiguous enough to mislead, we rewrite it and add a dated note. No claim was wrong, so it is not labelled a correction — but the change is still disclosed.

Routine live-service updates

This is the important distinction for a publication covering games that change every few weeks.

When a guide is revised because the game changed — a weapon was rebalanced, a map was adjusted, a quest step was altered — that is not a correction. The article was accurate when published; the world moved. These changes update the article and its updated date, but they are not labelled as corrections, because implying we made an error when the developers changed the game would be its own form of inaccuracy.

A correction means we were wrong. An update means the game is different now. We keep those separate, and we say which one a change was.

What we will not do

• Re-date unchanged articles. An updated date on FPSing means the content changed. See our editorial standards.
• Delete an article to make an error disappear. If a piece is beyond fixing we archive it with a note explaining why.
• Remove accurate coverage on request from a company or individual who simply dislikes it.

Complaints

If you have reported something and are not satisfied with how it was handled, write to editorial@fpsing.com and ask for it to be escalated. Include your original report so we can see what happened.