This is the first of many PRs to migrate the spec to use RFC2119 keywords to tighten up the language so its clear when things are required vs just optional/guidance.
This is the first of many PRs to migrate the spec to use RFC2119 keywords
to tighten up the language so its clear when things are required vs just
optional/guidance.

In this pass:
- add a title header
- added a "Notational Conventions"  section - to bring in RFC2119
- move "Changes" section down one section since I think "API Overview"
  is more important. We should really add an "Abstract" section at some
  point too.
- for each RFC2119 keyword already in the spec I either made it all CAPS or
  replaced it with a more appropate word. Note that sometimes we were
  using the word w/o meaning for it to be normative, like in examples.
  Sometimes I did swap things like "should" for "MUST" when it seemed
  like that was the real intent. But please do look over each one to make
  sure I didn't go too far.
- Related to the previous one, I tried to avoid tighening the language
  in the spec in most cases because I was hoping to limit this to more of
  a syntax change PR and we can leave PRs that might impact semantics for
  follow-on PRs.

Signed-off-by: Doug Davis <ff3bde741799c0eff815b83a54eda3fc494df54f@us.ibm.com>

servicebroker/servicebroker,servicebroker/servicebroker,openservicebrokerapi/servicebroker,servicebroker/servicebroker,duglin/servicebroker