Just have pity for the reviewers
I can't imagine going through any kind of volume of documentation with that degree of picky wordplay.
developer documentation is generally relatively volatile and will be under near permanent review (and now probably never pass a review) - for consumer (i.e. the great unwashed public) consumption it
may be more reasonable to stick to a house style.
IMHO as long as it is not open to interpretation where its important to the solution - JFDI and stop wasting everyone's time. Developers rarely want anything other than expected results and defined inputs in a manual anyway and therefore don't care even as a consumer about the fancy wordplay...The rest of the words are simply there to make it look big and expensive.