fix: GitHub changed markdown rendering for headings/anchors

Signed-off-by: Mike Ralphson <mike.ralphson@gmail.com>

proposals/2019-07-17-Webhooks.md

@@ -115,7 +115,7 @@ webhooks:
 **Existing Spec:**
 
 ```
-#### <a name="oasObject"></a>OpenAPI Object
+#### OpenAPI OpenAPI Object
 
 This is the root document object of the [OpenAPI document](#oasDocument).
 
@@ -146,7 +146,7 @@ This object MAY be extended with [Specification Extensions](#specificationExtens
 (new spec section)
 
 ```
-#### <a name="webhooksObject"></a>Webhooks Object
+#### Webhooks Webhooks Object
 
 A map of webhooks that may be received as incoming HTTP requests as part of the API. The key of the map is a unique short name for the webhook e.g. `messageEvent`. Each value in the map is a [Path Item Object](#pathItemObject) that describes a set of requests that may be initiated by the API provider and the expected responses.
 

proposals/2019-10-31-Clarify-Nullable.md

@@ -154,7 +154,7 @@ This is the proposed replacement for the `nullable` definition:
 
 Field Name | Type | Description
 ---|:---:|---
-<a name="schemaNullable"></a>nullable | `boolean` | A `true` value adds `"null"` to the allowed type specified by the `type` keyword, only if `type` is explicitly defined within the same Schema Object. Other Schema Object constraints retain their defined behavior, and therefore may disallow the use of `null` as a value. A `false` value leaves the specified or default `type` unmodified. The default value is `false`.
+<a id="schemaNullable"></a>nullable | `boolean` | A `true` value adds `"null"` to the allowed type specified by the `type` keyword, only if `type` is explicitly defined within the same Schema Object. Other Schema Object constraints retain their defined behavior, and therefore may disallow the use of `null` as a value. A `false` value leaves the specified or default `type` unmodified. The default value is `false`.
 <hr>
 
 ## Detailed design

proposals/2019-12-24-Overlays.md

@@ -21,51 +21,51 @@
 
 In recent months we have been discussing various use cases for overlays and various solutions.  The following proposal takes a somewhat more radical approach to the problem.  It is a more ambitious proposal than the others we have seen before but the additional complexity does allow for supporting many of the scenarios that have been discussed to date.
 
-#### <a name="overlayDocument"></a>Overlay Document
+#### Overlay Overlay Document
 
 An overlay document contains a list of [Update Objects](#overlayUpdates) that are to be applied to the target document.  Each [Update Object](#updateObject) has a `target` property and a `value` property.  The `target` property is a [JMESPath](http://jmespath.org/specification.html) query that identifies what part of the target document is to be updated and the `value` property contains an object with the properties to be overlaid.
 
 
-#### <a name="overlayObject"></a>Overlay Object
+#### Overlay Overlay Object
 
 This is the root object of the [OpenAPI Overlay document](#oasDocument).
 
 ##### Fixed Fields
 
 Field Name | Type | Description
 ---|:---:|---
-<a name="overlayVersion"></a>overlay | `string` | Version of the Overlay specification that this document conforms to. 
-<a name="overlayInfo"></a>info | [[Info Object](#overlayInfoObject)] | Identifying information about the overlay.
-<a name="overlayExtends"></a>extends | `url` | URL to an OpenAPI document this overlay applies to. 
-<a name="overlayUpdates"></a>updates | [[Update Object](#updateObject)] | A list of update objects to be applied to the target document.
+<a id="overlayVersion"></a>overlay | `string` | Version of the Overlay specification that this document conforms to. 
+<a id="overlayInfo"></a>info | [[Info Object](#overlayInfoObject)] | Identifying information about the overlay.
+<a id="overlayExtends"></a>extends | `url` | URL to an OpenAPI document this overlay applies to. 
+<a id="overlayUpdates"></a>updates | [[Update Object](#updateObject)] | A list of update objects to be applied to the target document.
 
 The list of update objects MUST be applied in sequential order to ensure a consistent outcome.  Updates are applied to the result of the previous updates. This enables objects to be deleted in one update and then re-created in a subsequent update.
 
 The `extends` property can be used to indicate that the Overlay was designed to update a specific OpenAPI description.  This is an optional property.  Where no `extends` is provided it is the responsibility of tooling to apply the Overlay documents to the appropriate OpenAPI description.
 
-#### <a name="overlayInfoObject"></a>Info Object
+#### Info Info Object
 
 This object contains identifying information about the [OpenAPI Overlay document](#oasDocument).
 
 ##### Fixed Fields
 
 Field Name | Type | Description
 ---|:---:|---
-<a name="overlayTitle"></a>title | `string` | A human readable description of the purpose of the overlay.
-<a name="overlayVersion"></a>version | `string` | A version identifier for indicating changes to an overlay document.
+<a id="overlayTitle"></a>title | `string` | A human readable description of the purpose of the overlay.
+<a id="overlayVersion"></a>version | `string` | A version identifier for indicating changes to an overlay document.
 
-#### <a name="updateObject"></a>Update Object
+#### Update Update Object
 
 This object represents one or more changes to be applied to the target document at the location defined by the target JMESPath.
 
 ##### Fixed Fields
 
 Field Name | Type | Description
 ---|:---:|---
-<a name="updateTarget"></a>target | `string` | A JMESPath expression referencing the target objects in the target document.
-<a name="updateAdd"></a>add | [Any](#addObject) | An object to be added as a child of the object(s) referenced by the target. Property has no impact if `remove` property is `true`.
-<a name="updateMerge"></a>merge | [Any](#mergeObject) | An object with the properties and values to be merged with the object(s) referenced by the target.  Property has no impact if `remove` property is `true`.
-<a name="updateRemove"></a>remove | `boolean` | A boolean value that indicates that the target object is to be removed from the the map or array it is contained in. The default value is false.  
+<a id="updateTarget"></a>target | `string` | A JMESPath expression referencing the target objects in the target document.
+<a id="updateAdd"></a>add | [Any](#addObject) | An object to be added as a child of the object(s) referenced by the target. Property has no impact if `remove` property is `true`.
+<a id="updateMerge"></a>merge | [Any](#mergeObject) | An object with the properties and values to be merged with the object(s) referenced by the target.  Property has no impact if `remove` property is `true`.
+<a id="updateRemove"></a>remove | `boolean` | A boolean value that indicates that the target object is to be removed from the the map or array it is contained in. The default value is false.  
 
 The properties of the merge object MUST be compatible with the target object referenced by the JMESPath key.  When the Overlay document is applied, the properties in the merge object replace properties in the target object with the same name and new properties are appended to the target object.