Corrections Policy
Technical information can become wrong when an app updates, Android changes a menu, or a file is replaced. Corrections should change the affected statement and, when useful, explain what was corrected.
What to Report
- Incorrect version, package, file size or checksum.
- A broken internal or download link.
- Installation steps that no longer match a current Android interface.
- A comparison claim that is no longer accurate.
- A security or permission statement that does not match the tested file.
How to Submit a Correction
Send the page URL, the exact sentence or data point and the evidence that shows the problem to [email protected]. Specific reports can be checked much faster than a general message saying that an article is wrong.
Dates and Material Changes
We do not change timestamps merely to make an old page appear new. When a correction or update materially changes the guidance, the visible modified date may change with it.
Priority Corrections
Security, download, package-identity and version errors take priority because they can directly affect what a reader installs. Broken links and outdated Android menu paths are also corrected promptly when reproduced. Minor wording changes are lower priority unless they alter the meaning of the guidance.
What Happens After a Report
A correction is checked against the relevant file, platform documentation or other direct evidence where possible. If the report is confirmed, the affected passage or data field is changed. If the evidence is inconclusive, the page should describe the uncertainty rather than replacing one unsupported claim with another.
Corrections Should Preserve Context
When a version number, checksum or Android menu path changes, the correction should not remove surrounding context that readers still need. If an older statement was correct at the time but is no longer current, the page can distinguish historical behavior from the present state rather than pretending the earlier information never existed.