Also, a lot of users don't give a shit about how something happens (all the gritty details). They just want to understand what is happening. Most of the time t

Also, a lot of users don't give a shit about how something happens (all the gritty details). They just want to understand what is happening. Most of the time this is because they have better things to do. When it comes to documentation: if the implementation details are not important to the user, you should skip them. Words on a page that a user reads but doesn't care about is wasting their time and they could be reading about other important details. If you have a broad user base who largely don't care about implementation details you're better hiding them from everyone rather than showing them to everyone.