Corrections Policy
How we handle screenshot instructions that become outdated, ambiguous or wrong after operating-system and device updates.
Screenshot behavior changes. When a shortcut, menu, save location or feature is no longer accurate, the page should be corrected rather than quietly leaving conflicting instructions in place.
What triggers a correction
Official documentation changes, an operating-system update, a verified reader report, or a mismatch discovered during review can trigger a correction.
How we verify
We reproduce the issue where possible and compare it against current first-party documentation or the exact model manual.
Legacy methods
Older methods can remain when they still help users with older hardware, but they should be labelled by device generation or software version.
Ambiguous save locations
If a location varies because of OneDrive, iCloud, Gallery apps or a configurable folder, the guide should say so rather than giving one path as universal.
Screenshots and visuals
Outdated interface images should be replaced when they can mislead the user about which control to press.
Reader reports
A report is a useful signal, not automatic proof. The correction is made after checking reliable documentation or reproducible behavior.
Frequently asked questions
Will old-device methods be deleted?
Not necessarily. Useful legacy instructions can stay with clear labels.
How quickly should a serious error be fixed?
As soon as it is verified.
Do spelling and punctuation corrections count?
Yes, editorial quality includes clarity and accurate labels.
What if official sources disagree?
The page should describe the scope/version of each source rather than pretending there is one universal behavior.