3.0.2 - Security Scheme Object description missing cookie location for apiKey

Update Open API object to OpenAPI Object in 3.0.2

It is understood that most examples showcased in the OAS spec are snippets, not entire OAS documents. However some of those snippets would not be valid even if included in entire OAS documents. This PR is an attempt to fix some of those examples.

**List of changes**:
- added a `GeneralError` schema inside the `Components Object Example`
- split the `Example Object Example` into multiple examples

Fixed some invalid examples

Fix nvm install on travis

… Invalid' to 'Method Not Allowed'

Revise 405 Response Object description to follow the RFC7231 Specification 's definition

Updated text relating to wildcard status code responses to clarify intent

So many people were considering dateTime, etc to be an OpenAPI type that tool vendors were implementing functionality to normalize this.

mikunn/openapi-schema-to-json-schema#4

I too in the past have thought I was meant to use dateTime in the format, not date-time. Let's just get rid of this column, it serves no real purpose as far as I can tell.

Removing type confusion

Added wording to clarify case sensitivity rules.

Address #715 - State (explicitly) whether Open API schema object definitions are open or closed for extension.

Address #715 - State (explicitly) whether Open API schema object definitions are open or closed for extension. Add 'an' for readability.

Updated suggested text to simplify

State explicitly: `additionalProperties : true` is the default

…by the consumer

Fix callback key expression example.

…cated

Add missing description of default value

fix wording on who supplies the default value for a server variable

Remove colons from example headings

discriminator is now an object, not an attribute

Do not rely on auto-detection of fenced code block languages

Simple change to indicate that it is likely to be removed in a later revision.

Make allowEmptyValue NOT RECOMMENDED

* Pet Schema in the MediaTypes Examples and Schema Object Examples uses the camelCase notation(petType),
* While Pets from the Discriminator Object use snake_case (pet_type).
It's inconsistent.

I chose the camelCase notation because it's used for propertyNames by the OpenAPI specification itself.

This reverts commit 4c79d31.

This reverts commit 3e7d0a8.

Re-target two commits from 3.0.1.md to 3.0.2.md

Consistent use of property name in schema examples: `petType` vs `pet_type`

3.0.2 Release Prep

Update release date