Don't you just hate it when you're reading technical documentation and the writer uses some term (like, say, carnet) but never explains what a carnet even is, as if everyone spends their day saying things like, "So how's your carnet doing? My carnet is doing pretty good. I just don't know where we'd all be without carnets."
Well, to be honest, we don't like it any better than you do. And so we did something about it: we created a glossary.
Now, by itself, the glossary is actually pretty cool: if you want to, you can go to the Glossary page and spend all day sitting there reading glossary terms. (Yes, exactly like sitting around and reading a dictionary all day.) But that's not the coolest thing about the glossary. Instead, the coolest thing about the glossary is this: Remember when we used the word carnet for the first time? Well, go back to the spot, and look carefully; you should see a double underline under the first mention of carnet:
Now, do this: hover the mouse over the double-underlined word. You should see – tah-dah! – the glossary definition of the word.
See? We weren't kidding about this being cool.
In case you're wondering, the first time we use a glossary term on any of our web pages, that term will be glossarified. (Uh, sure, that's a word.) Addressable users? Glossarified. Bearer token? Glossarified. One-time password? Reverse honeypot? We could do this all day.
But don't worry: we won't.