Editorial policy and corrections

Who writes errcodex

Everything on the site is produced in-house. There are no guest posts, sponsored pages or paid placements, and no vendor pays to be covered. We use automated tools, including AI, to find what developers search for and to help draft text; every page is checked against official sources, examples are executed where it is safe, and a human editor reviews new and changed pages before publication.

Where the facts come from

• Official documentation of each tool, its manual pages and its release notes or changelog.
• Specifications and registries: RFCs, WHATWG and W3C standards, POSIX, IANA registries.
• Running it: the output of the commands themselves, captured by our verification runner.

Forums, Q&A sites and blog posts can show us which questions are common, but they are never cited as the source of a fact. Every page lists its sources.

What "verified" and "draft" mean

• Verified: every example on the page was executed by our verification runner, in an isolated temporary directory, and the output shown is the real output. The page shows the date and the environment (operating system, shell, tool version). For error pages, the run must actually produce the error message the page is about.
• Draft: the page could not be executed safely in our environment (for example it needs a cloud account, a remote server, administrator rights or an operating system we do not run), or it describes facts such as release dates. It relies on the cited official documentation.

"Verified" certifies the examples, not every sentence: behaviour can still differ with other versions or configurations, which is why each page lists the versions it applies to.

What we never do

• Invent command output, error messages, versions, flags or dates.
• Mark a page verified without running it.
• Recommend disabling security checks without saying so and offering a safer alternative.
• Publish fake authors, testimonials or personal experiences.
• Copy text from other sites.

Corrections

When a command, message, version or claim we published turns out to be wrong, we fix it on the page, re-run its examples, update the page's date and record the change here. If you spot an error, write to dario_admin@resolvia-crm.tech (seehow to report a mistake).

No corrections so far.