http://en.wikipedia.org/wiki/Muphry%27s_lawI should perhaps, at the risk of being more correct but harder to understand, have written "s/here/heir/g"
The original has now been changed, although not in the way it is stated, but an error remains, as is so often the case, and no doubt will be in this comment.
My point was serious. Sometimes I have real difficulty in understanding things that have such grammatical oddities, so much so that I spend more time decoding what must have been intended than I spend understanding the point being made. I'm getting to the point where if I don't understand something because the grammar or spelling is "odd" then I move on. The author has lost a reader, for better of for worse.
There is too much to read, and a reader's attention is difficult to get. Don't discard it lightly. Yes, many people have English as a second, third or even fourth language, and all credit to them. But there is a trade-off to be made. Written once, read many times (you would hope). Make sure it's easy to read.
This equates nicely with writing code. Take more time to write it more clearly so that later readers (which may include you!) will be able to understand it. This is a principle we all know, and we all know we should apply. It applies equally to the written word as to the program.