update readme

FOR DISCUSSION ONLY. DO NOT MERGE.

@zdne @pksunkara @smizell I have edited the README and one example file. I am holding of on other example files pending chatting with @zdne. ITMT, I have added a few comments in-line that need clarification per an email I sent @zdne and questions I have.

Also, I have switched the order of presentation here from JSON first to MSON first in the examples. The point of this document is to introduce MSON and the JSON makes more sense once you read the MSON vs. the opposite (my experience reading this the first time). In the context of MSON being used to replace JSON in api-blueprint, maybe the logic is opposite, but if we are going to share this generally with people, then I think the order I have it is correct.
@zdne I am going to a wildcard _Type Name_ to the spec in an immediately forth coming PR. 

However, this example here does highlight and issue with Markdown formatting and escaping a reserved word like here. This is the correct syntax in that the * indicate a variable value and the ` indicate a literal of the reserved word. But it does not render how you would desire in Markdown.