Fixing Documentation Bugs

[Ben Cotton]

Looks good to me, though I wonder if instead of having people make
their edits on master, we should suggest branching first. This will
ease the transition from "patch writer" to "docs committer" and might
avoid pull problems the next time they go to fix something in the same
guide. So the steps would change to:

4. git checkout -b bugfix
5. [edit the file appropriately]
6. git add <file>
7. git commit <file>
8. git format-patch master
9. Submit the patch to the bugzilla ticket and state that the ticket
is ready for QA. Change the status to MODIFIED.
10. git branch -d bugfix

Thoughts?


-- 
Ben Cotton