I've experienced confusion reading corporate documents which contained poor grammar or orthography. As an example of the latter, based loosely on a real exampl

I've experienced confusion reading corporate documents which contained poor grammar or orthography. As an example of the latter, based loosely on a real example: It is preferred to take the server to run-level 1 then to reboot. So, I telinit 1 followed by shutdown -r now ...? In operational-readiness documents there really must not be any leeway for confusion or ambiguity, yet I've encountered many such examples. The usual retort of 'language evolves!' doesn't hold true in circumstances where a common, unequivocal meaning is required. You'd think programmers would be aware of that, writing strictly-defined grammar all day long!