I am sorry to have annoyed you.
I also regret distracting from the major issue, by mentioning the minor issues that you focused on.
The real problem:
In different contexts DocType names are sometimes concatenated and sometimes not.
So:
- To use a multiple name DocType for code examples, and make it clear when and when not to concatenate, would be ideal.
- To use a single name DocType for code examples would be ok, but not great.
- To use a two name DocType that also happens to be the only concatenated two word name is horrible.
Worse still, it’s used in a code example that shows NO error messages of any kind if you get it wrong. Getting it right is like a combination padlock: when everything is correct you get something; anything else, you get nothing.
I have been told off before for being sarcastic and typically I’m told, “if you don’t like it, fix it!” Well, guess what … I do … over and over again, filling in the gaping blanks in the documentation, but getting very little thanks or recognition…
… here: How to fully submit a DocType from Python?
and here: How to create an "Absolute Minimum Script Report"?
and here: [solved] cURL example of an attachment upload RPC call?
and here: How to set a "Naming Series" sequence start number through the RPC API?
and here: How to remove the "Publications" card from the landing page?
and here: How to get 'site_config.json' settings in Python code?
and here: How to call "Chart of Accounts Importer" through RPC API? - #7 by MartinHBramwell
and here: Can't use port 8000 except as NGinx upstream. What am I missing? - #5 by MartinHBramwell
and here: [Solved] What's the right way to version control my customizations? - #2 by MartinHBramwell
and here: How to create an "Absolute Minimum Script Report"?
All of those represent cases where I found the docs to be like product brochure feature lists, “Hey, here’s another cool thing ERPNext can do!”. They’re not written to fully armed the developer to go in and solve any problem. They’re more like, “When you figure out how, you will be able to …”
Very often, the examples only show the trivial case, like here: REST API – RPC, where the typical case is a call with parameters, but the example only shows how it’s done without parameters. Once again, I made the effort to fill in the hole: [Solved] cURL example of a whitelist method RPC call with parameters?