Report precisely
Include the page, section, configuration or version, observed behavior, expected behavior, primary evidence, and whether the issue changes a safety or operating recommendation.
CORRECTION PROTOCOL
Technical corrections should identify the exact claim, current evidence, affected boundary, and practical impact.
Include the page, section, configuration or version, observed behavior, expected behavior, primary evidence, and whether the issue changes a safety or operating recommendation.
Review the stated assumptions, test the relevant boundary, and distinguish a documentation error from environment, cache, version, or integration behavior.
Fix minor wording in place. Record substantive corrections with date, affected claim, prior guidance, corrected guidance, and verification.