I would add something that is counterintuitive but unsurprising to people who have children: learning long/complicated words is actually not a problem at all. Kids love learning and saying long words with interesting sounds in them. Sometimes it’s even easier to learn long/complicated words because they are easier to distinguish from shorter words.
Ask any 4 year old whether they would rather say “Tyrannosaurus Rex” or “dino”.
I've read that book and several other works on the subject and I still can't remember which one is system I and which is system II. I get why they use those labels (because they don't want to pre-suppose the characteristics of what they're investigating). But I do find them frustratingly undescriptive.
System 2 is always second cause it's slower. (Because it's more methodical, etc. etc.)
As a concrete example, if you say "I'm thinking slowly right now", someone might assume you have brain fog or some sort of trouble concentrating unless they've read a particular book. If you say you are using System II-thinking, they either get it because they've read that book, or they understand that they don't and can save themselves a lot of time and confusion and ask what you mean.
Using a simpler word for endianness does not spare you from having to understand endianness, but it might mislead you into thinking you do when you don't.
Re-using simple words can be confusing, and understanding that you do not not understand a word can actually be a feature, especially in technical writing.
As a good counter example, the word 'service' is used way too much in too many different ways. If someone says 'the service isn't working', they could mean the entire web application is down, the kubernetes Service-abstraction is misconfgiured, what it's running is broken, or some piece of code ending in "Service" doesn't compile.