WHAT COUNTS AS A CORRECTION
A correction fixes a material factual error.
Examples include an incorrect vendor capability, an inaccurate description of the application, a broken causal statement, a mislabeled comparison or another claim that could reasonably affect the reader's decision.
Typos and purely stylistic edits can be fixed without a formal correction note because they do not change the underlying meaning.
HOW WE HANDLE IT
Verify, correct and review connected pages.
- Confirm the issue against the best available source.
- Correct the affected claim rather than only adding qualifying language around it.
- Review internal links, comparisons and related software pages for the same issue.
- Update the recommendation logic if the corrected fact changes capability fit.
PRODUCT CHANGES
A vendor changing is not the same as our page being wrong.
If a vendor changes a feature, plan or workflow after publication, the page needs an update. If the page was inaccurate at the time it was published, that is a correction.
This distinction matters because software content can become stale even when it was originally accurate.
REPORTING AN ISSUE
Use the contact route to flag material errors.
If you believe a page contains a factual error, use the contact page and include the URL, the disputed claim and the source or evidence that supports the correction.
Commercial pressure or affiliate status is not a reason to change factual or recommendation content.