Release Notes: Unlrelated fixes

Author: jdesrosiers

draft/2019-09/release-notes.md

@@ -3,8 +3,6 @@ title: JSON Schema 2019-09 Release Notes
 layout: page
 ---
 
-_NOTE: This page is still being written, and is currently a fairly minimal listing of changes._
-
 For the vast majority of schema authors, we hope that these changes are minimally disruptive.
 
 The most likely to be frustrating is that `format` is no longer treated as a validation assertion _by default_ (although it is still possible for an application or user to configure a validator to treat it as one).  We decided this was acceptable because many schema authors are already extremely frustrated by its inconsistent behavior.

specification-links.md

@@ -307,12 +307,10 @@ For links to the somewhat more readably formatted versions on this web site, and
 - Output examples
     - [JSON Schema verbose output example](draft/2020-12/output/verbose-example)
 
-### 2019-09 (formerly known as Draft 8)
+### Draft 2019-09 (formerly known as Draft 8)
 
 _**NOTE:** All meta-schema URIs now use `https://`.  While currently also available over plain HTTP due to the limitations of GitHub pages and the need to keep prior drafts available over HTTP, only the HTTPS URIs should be used._
 
-### Draft 2019-09
-
 - Specifications
     - Core: [draft-handrews-json-schema-02](https://tools.ietf.org/html/draft-handrews-json-schema-02) ([changes](https://tools.ietf.org/html/draft-handrews-json-schema-02#appendix-G))
     - Validation: [draft-handrews-json-schema-validation-02](https://tools.ietf.org/html/draft-handrews-json-schema-validation-02) ([changes](https://tools.ietf.org/html/draft-handrews-json-schema-validation-02#appendix-C))