> or we could just use the longer words? we could but don't expect anyone with dyslexia noticing that a text says authorization when they subconsciously expect

> or we could just use the longer words? we could but don't expect anyone with dyslexia noticing that a text says authorization when they subconsciously expect authentication (and don't explicitly double check) Through also if we use AuthN and AuthZ (with capitalization) it's quite clearly readable and hard to mistype and no longer the kind of words dyslexia makes it easy to misread (it never was in the category of things dyslexia makes easy to accidentally mix up when writing I think). Using authorization and authentication also can have issues if you use a text editor with auto completion, for AuthN/AuthZ you simply could not use autocompletion. > My guess is they ran into something like installing a package that didn't cover their desired needs, or got into problems because they used the wrong term in technical documentation, maybe in context of a security review or a requirements document which has been legally binding singed of > The confusion is not going to be solved with trying to relabel the concepts. Especially given that login likely implies both AuthN and AuthZ so it's not even "just" relabeling.