Merge pull request #1038 from karenetheridge/ether/rc0-typos

improve some wording in draft 2020-xx rc0

Author: Relequestual

jsonschema-core.xml

@@ -286,7 +286,7 @@
                         where an instance may be outside any of the six JSON data types.
                     </t>
                     <t>
-                        In this case, annotations still apply; but validation keywords will not be useful,
+                        In this case, annotations still apply; but most validation keywords will not be useful,
                         as they will always pass or always fail.
                     </t>
                     <t>
@@ -344,7 +344,7 @@
                         of their subschemas.
                     </t>
                     <t>
-                        Keywords within the same schema object are referred to as adjacent keywords.
+                        Keywords which are properties within the same schema object are referred to as adjacent keywords.
                     </t>
                     <t>
                         Extension keywords, meaning those defined outside of this document
@@ -363,7 +363,7 @@
                 <section title="Boolean JSON Schemas">
                     <t>
                         The boolean schema values "true" and "false" are trivial schemas that
-                        always produce themselves as assertions results, regardless of the
+                        always produce themselves as assertion results, regardless of the
                         instance value.  They never produce annotation results.
                     </t>
                     <t>
@@ -546,7 +546,7 @@
                     dialect described in <xref target="ecma262">ECMA-262, section 21.2.1</xref>.
                 </t>
                 <t>
-                    Regular expressions SHOULD be built with the "u" flag (or equivilent) to provide
+                    Regular expressions SHOULD be built with the "u" flag (or equivalent) to provide
                     Unicode support, or processed in such a way which provides Unicode as defined
                     by ECMA-262.
                 </t>

schema.json

@@ -7,7 +7,7 @@
         "https://json-schema.org/draft/2019-09/vocab/unevaluated": true,
         "https://json-schema.org/draft/2019-09/vocab/validation": true,
         "https://json-schema.org/draft/2019-09/vocab/meta-data": true,
-        "https://json-schema.org/draft/2019-09/meta/format-annotation": true,
+        "https://json-schema.org/draft/2019-09/vocab/format-annotation": true,
         "https://json-schema.org/draft/2019-09/vocab/content": true
     },
     "$dynamicAnchor": "meta",