Editorial standards

Content review principles

• Problem-first writing: each article must answer a real operational question.
• Actionable steps: readers should leave with exact checks, not broad advice.
• No filler: sections that do not improve a decision are removed.

Accuracy standards

Before publication, we verify DNS commands, provider-specific instructions, and expected outcomes. We favor concrete commands and observable outcomes over vague recommendations.

Technical verification process

1. Reproduce the setup flow in a realistic environment.
2. Validate DNS responses with direct resolver checks.
3. Document at least one known failure mode and fix path.
4. Confirm final healthy state with explicit verification steps.

Update policy

We revise content after major provider behavior changes, repeated support failures, and policy updates. Articles are refreshed when users are likely to misconfigure current defaults.

AI assistance disclosure

AI tools may support drafting and structure checks, but final publication always requires human technical review. Accountability for correctness remains with the is-cool-me team.

Correction policy

If you identify an error, report it via Contact. Critical correctness issues are prioritized. Clarifications and non-critical edits are batched into normal update cycles.