[merb]

well not treating them as critical, but there are many projects that do so. One scala Project for example: https://github.com/playframework/playframework/labels/docume...

Unfortunatly once they are there not many PRs will address, these, only if their are actually critical. (Well the problem with play is actually that you need to read the README.md of the documentation carefully to make documentation and to understand a little bit of sbt and scala.)

Also it's actually not easy to write understandable documentation for many users. Some people are just too different, so that some actually need a way more detailed view, while for others this would be disturbing and useless noise, the golden middle is hard, especially if you contribute documentation to a framework which includes different libraries, it's really hard to keep the documentation simple.

P.S.: gitlab also treats documentation very seriously. (just to have at least two examples)