@9V1MI : Thanks for the feedback. I'm not sure what you mean however : the doc says to go back to Eeschema ("how to load the new library in Eeschema"), then to go to the menu "Preferences" -> "Component libraries"; Under "Component library files" (which is the first bloc at the top), click the "Add", select the library file (*.lib) you just created, and it's done. I don't see any mention to "Path type" or "relative path". After @davidsrsb 's comment I checked on Windows too (otherwise I'm on Linux) but it looks identical. For the seek of simplicity I volontarily don't mention the other ways of adding a library using the "search paths", because a beginner usually want to be told one method that works and this method only, so they don't get confused over unimportant details (to be honest, I'm not really sure I know exactly what the other blocks do myself).
My point (and therefore the point of this document) is that beginners that are considering learning KiCad to see if it would be better than their old software, or even more so, those that are trying to get into EE in the first place, hate reading documentations. As you said yourself, "it seems that the documentation was written by those familiar with the program instead of a newbie", and I'd add that it was written by and for users who already know the program. Documentations (unless maybe the most well-written ones) are "flat", they describe everything without highlighting what is important for a daily use. "It's not a bug, it's a feature" (meaning "design choice"). In my opinion, this is the gap a cheatsheet or any other kind of "getting started" document should fill. At the glance of an eye (that is hopefully attracted here using pretty shapes, fonts and colors) you have an idea of the workflow the program invites you to follow, with the most important steps and the details of what-button-to-click and what-key-to-press. And when you start to get familiar with the program, you can ponctually look at the documentation for this detail or that.