Every section has an address, every claim has a source
Every field type has its own anchor. /api/types.json publishes a documentation link per type, and 67 of the 68 pointed at a fragment that did not exist — they all landed at the top of the reference. They resolve now, and each type carries a real definition in the page's structured data instead of just a name.
Section anchors and a contents list. 337 headings had no id, so a page could only be linked as a whole. Every content section is addressable now, and the longer pages open with an "On this page" list.
The standards are linked. Pages that mention RFC 4180, RFC 2606 and 6761, RFC 4122, ISO 8601, E.164 or JSON Schema draft 2020-12 now link the document that defines them, rather than asking you to take the claim on trust.
Questions answered where they are asked. Use cases, database, mock API, QA, spreadsheet, guide and methodology pages gained an FAQ; the five "alternative to" pages gained a side-by-side table.
Two counts were wrong. The site advertised a vague “60+” in 24 places and the exact number in a handful of others; there are 68 field types. It also claimed nine name locales where there are eight locales — the ninth entry in the dropdown is “any”, which is not one. Both counts are asserted by the test suite now, against the generator itself.
Every page shows when it was last updated, and there is a full-text copy of the site in one file alongside llms.txt.