duo-naming-and-notation

How to name things, design symbols, and write reference material so users derive the answer instead of memorizing it — and how to handle the near-misses, overloaded tokens and silent misreadings that produce confident wrong behaviour. Use when asking what should we call this, why do users keep confusing these two things, what do our status icons actually mean to people, how do I document a rule that has exceptions, how should this reference page be ordered, which rows need a warning, why does support keep answering the same question, how do I write an error explanation that fixes the user's model, or what happened to our term after another team started using it. Covers notation redesign, motivated form, false friends, overloaded primitives, symbol ambiguity, labelled defaults, selective marking, and minimal contrasts.

Version

2.0.0

License

MIT