I wish each language, framework and library had a manual on HOW to read their docs.
I have a very hard time with reading the official PHP docs. Very hard time.
The official JavaScript docs are not bad, but they throw too much information about each operation. I don't want to know every single possible way to use an operation. I want a Pareto Principle-based categorization of most common use-cases so that I can prioritize what to look at.
This reminds me a lot of my experience reading man-pages. Usually I end up at Stackoverflow to help me solve the problem at hand, because there's just too much to read through for some docs.
there is also "tldr" https://github.com/tldr-pages/tldr