Skip to content
MRP Directory
Menu

Report a correction

Prices change, features ship, and we get things wrong. We would rather be corrected than be wrong, and that includes corrections from the vendor.

What we can and cannot do

We will update any factual field when you point us at a first-party page that contradicts what we show, pricing, licensing, a capability, a status, a former name. A screenshot or a PDF works for anything behind a sign-in.

We will not remove a sourced editorial note because a vendor dislikes it. If our reasoning is wrong, argue with the reasoning and we will listen.

1. About you

Working for the vendor is not a problem. It tells us how to weigh what you send.

A work address helps if you write for a vendor. Used only for this submission.

Needed if you work for the vendor, a consultancy or a competing product.

Needed if you work for the vendor.

Features often differ by plan, so this saves a round of questions.

2. What needs correcting

One block per thing. Several products in one go is fine: add a block for each.

Issue 1

Pick the closest. If nothing fits, choose Other at the bottom.

The page on this site where you saw it.

Copy the words or the number from our page.

A plan, edition, version or region, if it is not true for everyone.

If you know when it changed.

Evidence

At least one link or one file. A page on the vendor’s own site, documentation or repository carries the most weight. A screenshot is right for anything behind a sign-in.

The sentence, or the heading to look under.

PNG, JPG, WebP or PDF, up to 5 MB each, 4 files across the whole form. Only the editors see them. Hide customer names and anything confidential first.

3. Before you send

We will check the evidence and update the record if it holds up, noting the new check date. We will not remove a sourced editorial observation because a vendor disagrees with it.

We ask for your name and email so we can weigh what you send and ask a follow-up question. See our privacy page for what we keep and for how long.