Merge pull request OAI#1023 from timburks/OpenAPI.next

Minor edits: add headers for consistency, fix misspelling, add missing tag.

Author: Ron

versions/3.0.md

@@ -384,7 +384,9 @@ This object can be extended with [Specification Extensions](#specificationExtens
 
 #### <a name="serverVariableObject"></a>Server Variable Object
 
-An object representing a Server Variable for server URL template substituion.
+An object representing a Server Variable for server URL template substitution.
+
+##### Fixed Fields
 
 Field Name | Type | Description
 ---|:---:|---
@@ -409,7 +411,7 @@ Field Name | Type | Description
 <a name="componentsParameters"></a> parameters | Map[`string`, [Parameter Object](#parameterObject)] | An object to hold reusable [Parameter Objects](#parameterObject).
 <a name="componentsExamples"></a> examples | Map[`string`, [Example Object](#exampleObject)] | An object to hold reusable [Example Objects](#exampleObject).
 <a name="componentsRequestBodies"></a> requestBodies | Map[`string`, [Request Body Object](#requestBodyObject)] | An object to hold reusable [Request Body Objects](#requestBodyObject).
-<a name="componentsHeaders"></a> headers | Map[`string`, [Header object](#headerObject)] | An object to hold reusable [Header objects](#headerObject).
+<a name="componentsHeaders"></a> headers | Map[`string`, [Header Object](#headerObject)] | An object to hold reusable [Header Objects](#headerObject).
 <a name="componentsSecuritySchemes"></a> securitySchemes| Map[`string`, [Security Scheme Object](#securitySchemeObject)] | An object to hold reusable [Security Scheme Objects](#securitySchemeObject).
 <a name="componentsLinks"></a> links | Map[`string`, [Link Object](#linkObject)] | An object to hold reusable [Link Objects](#linkObject).
 <a name="componentsCallbacks"></a> callbacks | Map[`string`, [Callback Object](#callbackObject)] | An object to hold reusable [Callback Objects](#callbackObject).
@@ -911,6 +913,7 @@ Describes a single operation parameter.
 
 A unique parameter is defined by a combination of a [name](#parameterName) and [___location](#parameterIn).
 
+##### Parameter Locations
 There are four possible parameter locations (as specified with the `in` field):
 * path - Used together with [Path Templating](#pathTemplating), where the parameter value is actually part of the operation's URL. This does not include the host or base path of the API. For example, in `/items/{itemId}`, the path parameter is `itemId`.
 * query - Parameters that are appended to the URL. For example, in `/items?id=###`, the query parameter is `id`.
@@ -926,7 +929,7 @@ Field Name | Type | Description
 <a name="parameterDescription"></a>description | `string` | A brief description of the parameter. This could contain examples of use.  [CommonMark syntax](http://spec.commonmark.org/) can be used for rich text representation.
 <a name="parameterRequired"></a>required | `boolean` | Determines whether this parameter is mandatory. If the [parameter ___location](#parameterIn) is "path", this property is **required** and its value MUST be `true`. Otherwise, the property MAY be included and its default value is `false`. 
 <a name="parameterDeprecated"></a> deprecated | `boolean` | Specifies that a parameter is deprecated and SHOULD be transitioned out of usage.
-<a name="parameterAllowEmptyValue"/>allowEmptyValue | `boolean` | Sets the ability to pass empty-valued parameters. This is valid only for `query` parameters and allows sending a parameter with an empty value. Default value is `false`. If [`style`](#parameterStyle) is used, if behavior is `n/a`, the value of `allowEmptyValue` SHALL be ignored.
+<a name="parameterAllowEmptyValue"></a> allowEmptyValue | `boolean` | Sets the ability to pass empty-valued parameters. This is valid only for `query` parameters and allows sending a parameter with an empty value. Default value is `false`. If [`style`](#parameterStyle) is used, if behavior is `n/a`, the value of `allowEmptyValue` SHALL be ignored.
 
 The rules for serialization of the parameter are specified in one of two ways.
 For simpler scenarios, a [`style`](#parameterStyle) and [`schema`](#parameterSchema) can be used to describe the structure and syntax of the parameter.
@@ -950,6 +953,8 @@ Field Name | Type | Description
 ---|:---:|---
 <a name="parameterContent"></a>content | [Content Object](#contentObject) | The content of the parameter.
 
+##### Style Values
+
 In order to support common ways of serializing simple parameters, a set of `style` values are defined.
 
 `style` | [`type`](#dataTypeType) |  `in` | Comments
@@ -1998,6 +2003,8 @@ Field Pattern | Type | Description
 #### <a name="linkObject"></a>Link Object
 The `Link Object` is responsible for defining a possible operation based on a single response.
 
+##### Fixed Fields
+
 Field Name  |  Type  | Description
 ---|:---:|---
 operationRef | `string` | a relative or absolute reference to an OAS operation. This field is mutually exclusive with the `operationId` field, and must point to the fragment of a valid OAS definition
@@ -2604,6 +2611,8 @@ This object is an extended subset of the [JSON Schema Specification Wright Draft
 Further information about the properties can be found in [JSON Schema Core](https://tools.ietf.org/html/draft-wright-json-schema-00) and [JSON Schema Validation](https://tools.ietf.org/html/draft-wright-json-schema-validation-00).
 Unless stated otherwise, the property definitions follow the JSON Schema specification as referenced here.
 
+##### Properties 
+
 The following properties are taken directly from the JSON Schema definition and follow the same specifications:
 
 - title