Ask not what your open source project can do for you...
I sympathize with Sharon's plight about Drupal documentation and Clancy's concerns. As with many open source projects, the documentation could be much improved. That's a given that most open source projects recognize.
Unfortunately, I've seen similar observations about the need for better documentation posted to the Drupal forums many, many times. The solution to the problem is clear--many long term Drupal contributors respond to those that note the documentation problems with the best solution--but those who could provide the solution almost never do.
Many of you reading this who are open source software users probably think I'm talking about the software developers, that they should be the ones to improve the documentation. I'll admit it is a help when they are involved, and sometimes their assistance is needed for clarifying how the software works, but they aren't the ones that should be taking action. To paraphrase JFK, ask not what your open source project can do for you, ask what you can do for your open source project.
Most larger open source projects are a lot like not-for-profit style organizations, and in fact, often form non-profit foundations to handle monetary donations. Like Wikipedia and every other commons based peer production project, development of the product depends on the users. One has to escape beyond thinking of open source software as just a product and see open source as about communities where volunteers provide coding, bug testing, documentation, and support. All too often, there are volunteers to do the coding and the bug testing, but not nearly enough to offer support, and documentation comes dead last in the area of willing contributors. This despite the fact that creating and maintaining documentation is a massive task, much more difficult than people who have not been involved can imagine.
Open source software is often free, and free is good here because we have the opportunity in open source to shape the product in a way that we cannot with the proprietary software imposed upon us by our institutions. Writing teachers who use open source software may not be good coders, but they can be excellent contributors of documentation. In my years of working with Drupal and with other writing teachers who use Drupal, I haven't seen many contributions from other writing teachers to drupal.org's documentation. My advice is don't just expect that the soup kitchen with free meals should provide you with better food. Go find better food donations for the soup kitchen or get in there and help prepare the meals so that they taste better.
Consider this a challenge. Give some of your time to an open source project in the same way that you do other types of community service. If you find the documentation wanting for what you are trying to accomplish, take notes as you figure it out. Then afterwards, revise the existing documentation or provide new text as needed and negotiate with the project to have your changes included. Your help will be much appreciated, and it's an opportunity to learn to collaborate in the creation of text on commons based peer production projects. At the same time, you'll be helping to build the public commons and make things easier for those that come behind you.