Corrections Policy

Screenshot interfaces change. Keyboard layouts differ. Manufacturer updates can rename a button or move a setting. When a guide becomes inaccurate, the useful response is to correct the instruction—not merely to change a date.

What to report?

• The URL of the guide.
• Device brand and model when relevant.
• Operating system or software version.
• The exact step that did not match.
• What appeared on the screen instead.
• A non sensitive screenshot when it helps explain the difference.

How a correction is reviewed

We compare the report with current primary documentation and, when possible, reproduce the workflow or cross check the relevant device/software behavior. A single report can reveal a real version difference, but it can also reflect a custom keyboard mapping, managed device policy or app specific restriction, so the cause is checked before rewriting a universal instruction.

What changes after verification?

We update the affected step, nearby explanation, troubleshooting advice and related pages when the same fact appears in more than one place. If the old behavior still applies to earlier versions, the correction should preserve that distinction instead of replacing it with an equally incomplete new statement.

Material versus cosmetic changes

A material correction changes what the user needs to do or understand. Spelling, punctuation and layout improvements can be fixed silently. A material technical change should be reflected in the actual page content and, where the site displays review information, in the review record as well.

Contact us

Use the Contact page for corrections. Do not include passwords, authentication codes, private customer records or other sensitive information in a screenshot sent with a report.