It is precisely this reason, I've put
our project documentation into a wiki, so users can help us figure out what needs to be in it, what needs correction, what needs to get tossed, etc. Our
FAQ is there also. If there's something they want in there, they add it. If something is out of place, they fix it. Of course, I'll go over everything in the end, but it encourages the community to help each other by providing high-quality documentation.
Once the docs are feature-complete, I'll roll them back up into a .pdb, PDF, and so on, and ship it with the next release.
I'm always looking for ideas on how to improve, and as anyone knows I'm no
stranger to
writing and
maintaining lots and lots and lots of documentation in dozens of formats.