Language and Communication
The comments about who wrote this editorial are interesting in light of the subject matter. It seems clear that the real reason the authorship of this editorial is vague is that the poster's name has been placed where the byline should go.
Native speakers (and readers) of a language have certain expectations built into their wetware. These are the parsing rules for the grammar. Miscommunication results when these rules are violated. Hairy Larry is correct when he says you must learn to communicate in order to succeed. If you misuse language, others will be confused about what you mean, and you miss an opportunity to persuade or inform them.
It has been a source of puzzlement to me that no programmer would expect a compiler to 'understand' his meaning when he writes 'foreash' rather than 'foreach', yet if he writes documentation that uses 'enstans' in place of 'instance' he expects this to be understandable. Or, more pointedly, if the byline reflects the poster rather than the author, misunderstanding is bound to occur.
I believe the first step in better documentation is to learn how to write prose correctly (is it written 'function()' or '(function)'?). Proper spelling would also be a good thing (is it 'open FILE, filename' or 'open FILE filename'?). You learned C and Perl and Lisp; surely you can learn your own language as well. It's just one more hack.