Reading through the main linked document - I think that you're just reading too much into it. That is a sample test plan, showing a generally acceptable format and structure. It isn't a real flight test plan and report, that's been flown through, modified as issues were hit and resolved.
The format is representative of most real-world best practices, the detail has in my opinion been shoved in to give an idea of what it should look like. I don't think anybody ever intended for it to be forensically picked apart and cross-checked. That will, and should, happen to real plans as they are resolved into compliance reports - but this is just a simplified example.
G