Consistent terminology throughout

Inconsistent terminology in documentation signals to readers that the codebase was written in separate sessions without coordination — because it usually was. When 'API key' in the authentication section becomes 'token' in the code examples and 'credential' in the error reference, readers must constantly re-orient to confirm these are the same thing. For vibe-coded projects built across multiple AI sessions, terminology drift is nearly universal: each session invents its own names for the same concepts. iso-25010:2011 analysability is directly degraded by terminology inconsistency — the documentation costs more cognitive effort per reading.

Audit the docs for each core concept and pick one term, then enforce it everywhere. For projects with multiple similar concepts, maintain a terminology reference at docs/TERMINOLOGY.md or src/docs/glossary.md:

Update all code examples to match the chosen terms — variable names in code that contradict prose terminology are the most common failure mode. Before evaluating, extract and quote every term used for the same concept across three or more documentation sections.