Merge pull request OAI#950 from OAI/general-fixes

misc fixes

Author: webron

versions/3.0.md

@@ -48,7 +48,7 @@ Additional utilities can also take advantage of the resulting files, such as tes
 		- [Responses Object](#responsesObject)
 		- [Response Object](#responseObject)
 		- [Headers Object](#headersObject)
-		- [Examples Object](#examplesObject)
+		- [Example Object](#exampleObject)
 		- [Links Object](#linksObject)
 		- [Link Object](#linkObject)
 		- [Link Parameters Object](#linkParametersObject)
@@ -397,7 +397,7 @@ All objects defined within the components object will have no effect on the API
 
 ##### Fixed Fields
 
-Field Pattern | Type | Description
+Field Name | Type | Description
 ---|:---|---
 <a name="componentsSchemas"></a> schemas | Map[`string`, [Schema Object](#schemaObject)] | An object to hold reusable [Schema Objects](#schemaObject).
 <a name="componentsResponses"></a> responses | Map[`string`, [Response Object](#responseObject)] | An object to hold reusable [Response Objects](#responseObject).
@@ -1109,12 +1109,7 @@ Field Name | Type | Description
 <a name="requestBodyRequired"></a>required | `boolean` | Determines if the request body is required in the request. Defaults to `true`.
 
 
-##### Patterned Fields
-Field Pattern | Type | Description
----|:---:|---
-<a name="requestBodyRepresentation"></a>`*` | [Schema Object](#schemaObject) <span>&#124;</span> [Reference Object](#referenceObject)] | The schema defining the request body.
-<a name="parameterExtensions"></a>^x- | Any | Allows extensions to the OpenAPI Schema. The field name MUST begin with `x-`, for example, `x-internal-id`. The value can be `null`, a primitive, an array or an object. See [Specification Extensions](#specificationExtensions) for further details.
-
+This object can be extended with [Specification Extensions](#specificationExtensions). 
 
 ##### Request Body Examples
 
@@ -1560,16 +1555,6 @@ Field Name | Type | Description
 <a name="responseContentObject"></a>content | [Content Object](#contentObject) | An object containing descriptions of potential response payloads.
 <a name="responseLinks"></a>links | [Links Object](#linksObject) | An object representing operations related to the response payload.
 
-
-##### Patterned Objects 
-
-Field Pattern | Type | Description
----|:---:|---
-<a name="responseContentType"></a>`*` | [Schema Object](#schemaObject)<span>&#124;</span> [Reference Object](#referenceObject) | A schema describing the response value for a specific `Content-Type`
-
-Representations MAY take the form of a wildcard (`*`) to designate any `Content-Type`, 
-or a regular expression for matching a specific type
-
 This object can be extended with [Specification Extensions](#specificationExtensions). 
 
 ##### Response Object Examples
@@ -2381,7 +2366,7 @@ schemas:
         $ref: http://foo.bar#/examples/name-example
 
 # in a request body, note the plural `examples` as the Content-Type is set to `*`:
-	requestBody:
+  requestBody:
     content:
       'application/json':
         schema:
@@ -2420,7 +2405,7 @@ schemas:
 
 #### <a name="referenceObject"></a>Reference Object
 
-A simple object to allow referencing other definitions in the specification, internally and externally.
+A simple object to allow referencing other components in the specification, internally and externally.
 
 The Reference Object is defined by [JSON Reference](https://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03) and follows the same structure, behavior and rules. 
 
@@ -2539,8 +2524,8 @@ To support polymorphism, OpenAPI Specification adds the support of the `discrimi
 When used, the `discriminator` will be the name of the property used to decide which schema definition is used to validate the structure of the model.
 As such, the `discriminator` field MUST be a required field.
 There are are two ways to define the value of a discriminator for an inheriting instance.
-- Use the definition's name.
-- Override the definition's name by overriding the property with a new value. If exists, this takes precedence over the definition's name.
+- Use the schema's name.
+- Override the schema's name by overriding the property with a new value. If exists, this takes precedence over the schema's name.
 As such, inline schema definitions, which do not have a given id, *cannot* be used in polymorphism.
 
 ###### XML Modeling
@@ -3458,7 +3443,7 @@ read:pets: read your pets
 #### <a name="securityRequirementObject"></a>Security Requirement Object
 
 Lists the required security schemes to execute this operation.
-The name used for each property MUST correspond to a security scheme declared in the [Security Definitions](#componentsSecuritySchemes) under the [Components Object](#componentsObject).
+The name used for each property MUST correspond to a security scheme declared in the [Security Schemes](#componentsSecuritySchemes) under the [Components Object](#componentsObject).
 
 Security Requirement Objects that contain multiple schemes require that all schemes MUST be satisfied for a request to be authorized.
 This enables support for scenarios where there multiple query parameters or HTTP headers are required to convey security information.
@@ -3469,7 +3454,7 @@ When a list of Security Requirement Objects is defined on the [Open API object](
 
 Field Pattern | Type | Description
 ---|:---:|---
-<a name="securityRequirementsName"></a>{name} | [`string`] | Each name MUST correspond to a security scheme which is declared in the [Security Definitions](#securityDefinitions). If the security scheme is of type `"oauth2"` or `"openIdConnect"`, then the value is a list of scope names required for the execution. For other security scheme types, the array MUST be empty.
+<a name="securityRequirementsName"></a>{name} | [`string`] | Each name MUST correspond to a security scheme which is declared in the [Security Schemes](#componentsSecuritySchemes) under the [Components Object](#componentsObject). If the security scheme is of type `"oauth2"` or `"openIdConnect"`, then the value is a list of scope names required for the execution. For other security scheme types, the array MUST be empty.
 
 ##### Security Requirement Object Examples