Many people will cite how their adoption of software was based on the quality of its documentation. At the same time, documentation can be one of the largest gaps in quality with an open source project. This talk will discuss why that is, what you (yes you) can do about it, and how the author has (so far) managed to avoid burnout by learning to (grudgingly) accept less-than-perfect grammar. Examples will include things done well and lessons learned, as well as humorous and painful failures, specifically from within the GeoServer community, where the author has lots of (perhaps too much) experience.