I don't think that linux is worried about taking over the Desktop market, as long as they have the server market cornered. Also they're making a big impact on cell phones & tablets.

Linux has been doing well in marketing, by getting the free advertising, because it's willing to give.

Also a lot of the documentation provided isn't really paid for so, how much should someone put out for free.
That's why some of the big guys provide subscriptions for support. If you pay for the support then you can get all the technical info that you need.

Linux man pages and much of the official documentation put out by distributions is written in a technical manner and with the assumption that the reader understands the items and processes referred to. So they are properly written for the people they are written for. What you are referring to is layman's documentation that explains basic principles with as little technical language as possible. Although layman's documentation is useful, I do not like the idea of too much of it being written. The biggest hurdle new users have is lacking the necessary background knowledge to understand and use documentation. Once that knowledge is gained, the documentation becomes a very good resource. Layman's documentation should be written with the goal of providing the basic knowledge to use "real" documentation.

There is one of the problems with Linux today. Linux users are no longer considered users, but customers.

True. And since Linux is no company it's not possible to change the attitude of the developers. And that's a problem because that way Linux will stay just a niche product (or vanish alltogether) while it can do so much more.
Ten years ago, Microsoft was worried about Linux taking over the Desktop, by the way. I would have loved to either see that happen or at least Microsoft remaining worried.

Check out the mplayer manpage as an example for good documentation. If you do, you'll realise that I'm NOT asking for a manpage to explain everything starting from the flow of electrons (what you call layman's documentation). I'm expecting manpages to be helpful as a starting point for somewhat experienced users, and NOT to be merely a cheatsheet for people who have done it all before and just forgot some of the options. The mplayer manpage is helpful in that sense as it gives at least some examples. (And for more information, for example on how to group differnent options for video, audio, in- and output you'd obviously refer to the online documentation.)