Many parts of the guidelines are in all caps

[microsoft]

Many parts of the guidelines are in all caps

[johnnliu]

I read the guideline again after seeing this issue and I'm inclined to agree.

• The table of contents itself is inconsistent with casing.
• All caps has actual meanings in the actual guideline both as technical words: e.g. REST, RESTful, HTTPS, OPTIONS
• And as part of the requirements language https://github.com/Microsoft/api-guidelines/blob/master/Guidelines.md#43-requirements-language "MUST, SHOULD, SHOULD NOT"

So the liberal use of all capital case in headings distracts from the use in the rest of the text. In fact, it is much hard to see "SHOULD, SHOULD NOT" with all the headings capitalized and that's when I feel the issue has crossed the line from trivial to important.

Please consider dropping all caps in the headings.

[RobDolinMS]

Thanks for the suggestions @lumaxis and @johnnliu.
I believe this is just a remnant from when we converted the guidelines into Markdown.
Anyone wanting to submit a pull request to fix these from ALL CAPS would be appreciated.

[cleemullins]

@BasThomas PR, found here, addresses most of this.

As soon as I get get another set of eyes on it, I'll merge it in. #26