Editorial and correction policy

Prefer official documentation, standards, release notes, source repositories, and reproducible tests. Secondary sources may provide context but should not be the sole support for important technical claims.

Code, commands, calculations, and tool behavior should be checked before publication. Version-sensitive content must state the relevant version or review date when it materially affects the result.

Automation may help outline, translate, or edit content. It is not treated as a source. Names, versions, APIs, numbers, security guidance, and examples require human review or reproducible verification.

The updated date changes only after a material revision. Cosmetic edits do not justify presenting an article as newly updated.

Readers can report a reproducible problem through the public issue tracker. Confirmed errors are corrected in the page and, when useful, noted in the issue history.

Donations and hosting relationships do not buy coverage, ranking, links, or favorable conclusions. Sponsored material, if introduced, must be clearly labeled.