Policy
Technical guides are written from primary standards and provider documentation, reviewed for factual accuracy and updated when provider interfaces or requirements change.
- official sources preferred
- corrections documented
- last-reviewed dates visible
- no copied provider documentation
Source priority
Technical claims that affect a repair path should be checked against RFCs, browser documentation, certificate standards or the official documentation of the provider being discussed. Third-party summaries can help discover an issue but do not replace the primary source for provider-specific settings.
Original explanation
Documentation is summarized and translated into the troubleshooting context rather than copied. Guides explain why a setting matters, what public evidence confirms it, what can be safely changed and how to validate the result afterward.
Corrections
A factual correction should update the affected diagnosis/guide, its last-reviewed date and any linked rule that relies on the same technical assumption. Confirmed facts and likely explanations must remain visibly distinct after the correction.
No manufactured pages
A page is not published merely because a keyword variation exists. Similar queries are consolidated when they share the same user problem and repair path. New indexable routes require distinct utility, search intent or provider-specific instructions.