Editorial standards

Evidence

Fixes are grounded in vendor documentation, release notes, support pages, and issue trackers wherever those exist. Community reports from forums and Reddit are used as supporting evidence and are labelled as such on every page. A community report is never presented as an authoritative statement of fact.

Every source is listed with its publisher, type, and the date it was last checked. Individual fixes link to the sources that back them.

Safety ordering

Fixes are ordered from most reversible to most invasive. Restarting an application comes before clearing a cache, which comes before reinstalling a component, which comes before changing system settings.

Any step that can cause data loss, alters the registry or firmware, or disables a security feature carries a warning and lists the backups or prerequisites it needs first. Such steps never appear in the "start here" section, and the publishing system rejects an article that tries to put them there.

Verification dates

A "last verified" date means that page's claims were re-checked against its sources on that date, and that every source was re-fetched and still said what the page says it says. Dates are never bumped to make a page look fresh: a verification date only moves when a re-check actually ran. If a page has not been re-verified, it shows when it was last updated instead, and no verification date at all.

How pages are produced

Pages on this site are researched and drafted by an AI pipeline, and they are reviewed and published by it as well. There is no human editor reading each page before it goes live, and saying otherwise would be the kind of claim this page exists to rule out.

What that review is not is a rubber stamp. Every article records its review: the method used, when it ran, and four specific checks — that each claim matches the source cited for it, that every source was reachable when checked, that the fixes are ordered safest-first, and that the page is not a duplicate of one that already exists. An article that fails a check does not publish.

Independently of that review, the publishing system enforces the rules on this page and rejects anything that breaks one: an article with no source, a destructive step placed in the "start here" section, a community report dressed up as vendor documentation, or a verification date that no re-check earned. These hold on every path, and they are the reason automated publishing is safe to run at all.

A person does read this site: corrections sent through the contact page are handled directly, and they take priority over new pages.

Content used purely to develop and test the site is labelled as unverified example content wherever it appears.

Corrections and updates

Software changes, so pages go stale. When a driver, client, or OS update invalidates a fix, the page is flagged for re-research and updated in place rather than duplicated. Where the same problem is asked in several ways, we improve one page instead of publishing near- identical ones.