What a correction needs
- The page URL and exact statement affected.
- The provider, product, model, software version and market where relevant.
- A current authoritative source and the date it was checked.
- Whether the problem is inaccurate, incomplete, outdated or dependent on a different configuration.
How evidence is evaluated
A newer source is checked for the same model, release, market and use case. Conflicting evidence remains an uncertainty until the difference can be resolved. Corrections should update related guides and specification records as well as the original statement.
Use the review date appropriately
For a time-sensitive purchase or configuration change, verify the current manufacturer, project or provider documentation directly. A published review date does not replace your deployment checks.