Feature/revise spec

DO NOT MERGE. FOR DISCUSSION ONLY. @zdne @honzajavorek Please comment.

This PR updates the SPEC based on @zdne and my multiple discussions and refinements.

It also pulls in the current README with some typo fixes. 

@zdne I basically forked and update your branch for this PR into master. Would you prefer I just fork off of master and just create a branch the only adds the spec? Let me know.
The point here is that a `body` section or a `attributes` section in resource blueprint that has an MSON list like this are actually the implied object. Not sure I want to put that phrase in right now or tie in other external concepts to the MSON spec. @zdne do you think we need to clarify this better now?