Transparency by design

Corrections policy

How factual errors, unsafe instructions, outdated features, and broken references should be handled.

What to report

A useful correction identifies the page URL, the exact statement or step, the affected software version, and a supporting official source when available. Do not include passwords, personal data, or malware samples.

How corrections are handled

The editorial owner must assess the report, fix material issues, record the modification date, and obtain renewed technical review when security instructions change.

Launch requirement

A public reporting channel and responsible editorial owner have not yet been configured. They must be assigned before production launch.

About this project · Detailed methodology