Skip to main content
Friendly Geek
Request support

Editorial standards

How Friendly Geek publishes guidance.

This policy explains who writes the guides, how sources and checks are handled, and what the review labels do—and do not—mean.

Applies to 38 currently published guides.

Accountability

Who writes Friendly Geek articles

Articles are assigned to a named human author. AI systems are not presented as authors, cannot approve content and cannot publish directly.

The current library is written by Caleb. The author page lists only public facts supported by the active author record.

Evidence

How sources are selected

  • Sources should directly support the claim or instruction they accompany.
  • Primary and authoritative sources are preferred where accuracy matters.
  • Facts, recommendations and opinion should be distinguishable.
  • Important limitations, assumptions, versions and risks should be stated.
  • Sources are shown on an article when the guide contains source records.

Checking

What the review labels mean

Every published record has a named checker and a review date. “Last checked by” can describe the author checking their own work; it is not evidence of independent review.

“Technical review by” appears only when a reviewer is recorded who is distinct from the article author. At present, 0 published guides identify an independent technical reviewer.

External review should be used where appropriate expertise is available, especially for higher-risk safety, scam, recovery and business-continuity guidance. Friendly Geek does not imply that review occurred when no reviewer is identified.

Corrections

Corrections, material updates and withdrawals

  • Minor errors are corrected through the normal editorial workflow.
  • Material factual corrections should receive a change summary.
  • Unsafe guidance should be corrected or withdrawn immediately.
  • Publication dates are not changed merely to make older content appear new.
  • A modified date changes only when the public guidance changes materially.

To report an error, email [email protected], include the page address and describe the suspected problem.