I don’t agree much with this sentence. I will report something happened to me.
We needed to use unix extensions on SMB to make some sort of roaming profiles for the clients (Firefox will not work if home directory is on a SMB share without unix extensions, to be explicit). Unix extensions are disabled on the smb.conf file template and are highly discouraged, but we were brave 
and changed just one line in one template file. Starting from that point, our smb.conf file is pretty and regenerated every time with unix extensions enabled.
How much time took me to figure out how to fix it forever within templates? Not more than 10 minutes, including read up where template files were placed and find the right one. How much time did I lose to find that missing unix extensions were the culprit (it may be matched to troubleshoot misbehaviors in a production environment)? Days.
We are discussing of reading some pages once in a lifetime and profiting for the rest of it… Are we really asking ourselves if it is worth or not?
Also, I read somewhere that documentation was written from developers, and usually they are terse. Yes, they are. At the beginning I also found out documentation to be a little sparse, but it changed as soon as I read it through, although quite quickly paced. Once I grasped the gists of the documentation, all the information needed flowed quite instantly.
Just my 2 cents, of course.