Use an Engineer
I've seen technical requirement specifications with similar problems to those described in this article. They were usually cobbled together by managers and had a quick polish from marketing types. I shudder to think what can happen to a document after a lawyer gets hold of it.
In all cases, any important documentation should be reviewed by someone who is not involved in the project and maybe doesn't even work for the companies concerned. Let's face it, if millions of pounds/dollars will be generated/spent as a result of this, you might as well put a couple more thousand in up front to get it right. What happens is that people who more or less understand the situation apply an internal mental filter to anything that isn't clear, turning it into something that fits their own internal mental model. Hence, to them, the document makes sense.
If you gave to an independent and experienced person (especially an engineer) you'd soon be asked questions like 'what does that mean?', 'what happens if X then Y, because that situation doesn't seem to be covered?' These and more embarrassing questions would flow like water.
It wont happen though because it's terrifying and embarrassing to have your work looked at and then criticised by someone who isn't afraid of you screwing up their career progress :)