Editorial and Corrections Policy
Technical content should be useful, reproducible, and clear about its limits.
Sources and updates
We prefer primary specifications and standards. Publication dates come from the article source. A Last updated date appears only when a material change is explicitly recorded; repository history provides the change record.
Examples and safety
Examples should be neutral, inclusive, and technically reproducible. Security-sensitive tools state their limitations; for example, decoding a JWT does not verify its signature.
Corrections
Report a factual, translation, accessibility, or privacy issue to [email protected] with the page URL and evidence. Confirmed issues are corrected on affected pages; matching locale versions are updated when the same issue applies.