Corrections

Report an error

Use the contact form and say which guide, which section or claim, and what you believe is wrong (with a source, if you have one — a Microsoft Learn page, a release note, a screenshot of current behaviour). The more specific the report, the faster it can be checked and fixed.

What happens next

Every correction report is read. If the claim is confirmed wrong, the guide is fixed, its updated date is bumped, and — for a substantive factual error, not a typo — the change is noted on the changelog. If the report turns out to be a matter of interpretation rather than a factual error, that gets explained back to whoever reported it, not silently ignored.

What doesn't get "corrected"

A comparison guide's honest opinion of where one product beats another isn't an error to be corrected into a more favourable framing — vendors and their partners occasionally ask for exactly that, and the answer is no. Genuine factual errors (a wrong limit, an outdated price, a feature described in the wrong app) are a different matter entirely and get fixed on confirmation.

Credit

Ask to be credited for a correction and you will be, by first name or however you'd like to appear, in the section of the guide or the changelog entry it applies to.

Speed

This is a single-author site with no support SLA. Most corrections are read within days; a fix to the actual guide can take longer if it needs re-verifying against a source first — better a correct guide a week later than a fast, wrong one now.