With respect, WebAssist is one of the few software businesses that doesn't seem able to grasp the idea of version control linked to documentation.
If you have WAProduct_1.0.0, then that would be issued with documentation clearly marked WAProduct_1.0.0_gsg.pdf (or whatever). That document would exist as a download or linked PDF in the support documentation for WAProduct_1.0.0.
If a dot release was issued that included any enhanced or altered (or fixed) functionality, then WAProduct_1.0.1_gsg.pdf (or whatever) would be added to that product's documentation page with an updated PDF that reflected the changes made - in addition to any previous material. The engineers creating the software would then presumably test its implementation following a literal interpretation of the guide to confirm that the instructions are correct.
Similarly with WAProduct_2.0.0. The documentation for this - tested and proved - would co-exist with the previous versions' documentation.
As an example, If I wanted to implement my copy of PowerCMS_101 or any other of my solutions purchased prior to 17th March 2010 (as the previous EULA allows me to use them on as many sites as I like) - I should be able to find required documentation for that specific release.
Too many people seeing guides with missing or innacurate information which refer only to some non-specific generic outline of what the customer should be seeing, often wrongly.
One version number, one accessible, related set of documentation. As it is, you have your customers paying to do all your beta-testing pending the innevitable imminent dot release on each new version.
Regards to Eric & Jimmy, wherever they are. Please can we have them back?