doc-correctness

Verify documentation claims against source code by supplying a target page path to cross-check constants, addresses, and RPC behavior against authoritative implementation sources, ensuring factual accuracy.

Documentation drifts from implementation when code, configurations, or deployments change without corresponding updates, requiring auditing to verify consistency and reduce factual inaccuracy risk.

Yes, you can audit an entire layer or the full documentation set to verify consistency across code, configs, and deployments by locating authoritative sources for each claim.

Documentation auditing works for network parameters and RPC behavior by validating them against actual sources and providing guidance for remediation to ensure spec correctness.

The best way to check factual correctness in technical documentation is to identify and verify claims against implementation sources, confirming accuracy against the knowledge base and primary repositories.

You need to audit docs for spec correctness when verifying alignment between target documentation pages and source code, especially after updates to constants, addresses, or deployment configurations.