Git Protocol

I think the description should be pretty free form and doesn't necessarily need to be there at all. If we were using [RFC vocabulary](http://tools.ietf.org/html/rfc2119)’, I'd maybe say something to the effect of "The commit may contain a description that can take any form. The developer should include a description if the commit needs context that can be provided in no other way (ie. surrounding commits, code comments)"

I used to think that document that I linked to was really stupid, but after reading a ton of spec and RFCs, I've grown to think it's awesome to have should, may, must, etc explicitly defined.