Add specification references for securitySchemes

Usage of description and definition to refer to an OAS document was mixed. This makes it more co...

[Implementations] Added editing tools section with known OpenAPI 3.0 Editors

Make callback example link relative

Update intro wording, OAS definition [file] fixup

Fixed a typo: embeded -> embedded

Fixed JSON request example in "Key Expression"

Fixed an invalid example (Encoding Object Example)

Updated Link Object to ensure OperationRef or OperationId

Removed bonus character from requestBody description

Prep for next version

The runtime expression [must be quoted](http://www.yaml.org/spec/1.2/spec.html#id2788859) as it ...

3.0.0-RC2 Release Preparation

Callback example link

Fixed ambiguity with link parameters and added requestBody support

Grammar fixes copied from Kris' PRs

Clarified multi media types - for encoding object only

Also added support for passing requestbody

multipart clarifications

Semantic Versioning

[Contributors] Add contributors with >25 PRs

Addresses #1156

Fixed table headers

added example

Update apiKey name field description

OperationRef changes and more

fixed example

clarified wording

Allow apiKey in cookie

Update link to RFC7235 section in Security Scheme `scheme` field description

no more red

Added callback examples

Clarified path matching

refs #15

edit Discriminator Object

edit Tab Object

edit Parameter Locations and its Fixed Fields

edit Special Considerations for multipart Content

edit Patterned Fields in Responses Object

The specification itself is versioned using semver, so a new top level section
describes specifi...

edit Reponses Object Example

edit Schema Object

edit Schema Object Properties and Fixed Fields

edit all security sections

edit XML Arrays

edit Composition and Inheritance

edit Reference Object