Editorial Policy and Evidence Standards
Evidence first
Product claims are attached to a documented version. Release notes, tagged source files and primary Windows documentation take precedence over an unverified mirror or marketing statement. A source link is evidence for the product behavior it describes, not a guarantee about the file returned by a separate service.
Claims we avoid
No guaranteed FPS increase, fixed percentage RAM reduction, fake install count, invented user review or manufactured expert biography is used. Pricing or licensing statements describe the project, not an assurance about third-party download offers.
Updates and corrections
A documentation-review date records when source material was checked. It is not a test date or a software-release date. When a release changes, review its tagged documentation, affected instructions and structured data together. Record substantive changes rather than refreshing dates without changes.
Reader intent
A page has one primary task. Related synonyms are grouped rather than creating near-identical pages for every phrase. Sources, limitations and a way to check the outcome belong beside the instructions, not only in a footer.