I've only made a few contributions to various open source projects but I think that I'm an effective advocate for open source in general amongst my friends and

I've only made a few contributions to various open source projects but I think that I'm an effective advocate for open source in general amongst my friends and colleagues. One task that is often neglected, by myself as well as others, is documentation review. I'd like to suggest that anyone wanting to make contributions to open source software, and has the time and knowledge to do so, please expand and correct the documentation for any favourite projects that seem like they need it. I have a feeling that good documentation is more important than good implementation when it comes to product adoption. I'm going to try to follow my own advice here. There are a few projects I use that could really do with better docs, and I think that teaching people to use software correctly is easily as valid as fixing bugs or adding features.