Fix how ECMA-262 is used and referenced

Author: Relequestual

jsonschema-core.xml

@@ -545,12 +545,12 @@
                     Keywords MAY use regular expressions to express constraints, or constrain
                     the instance value to be a regular expression.
                     These regular expressions SHOULD be valid according to the regular expression
-                    dialect described in <xref target="ecma262">ECMA 262, section 21.2.1</xref>.
+                    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
-                    Unicode support, or processed in such a way which provides Unicode support,
-                    as defined by ECMA 262.
+                    Unicode support, or processed in such a way which provides which provides Unicode
+                    as defined by ECMA-262.
                 </t>
                 <t>
                     Furthermore, given the high disparity in regular expression constructs support,
@@ -2485,7 +2485,7 @@
                         <t>
                             The value of "patternProperties" MUST be an object. Each property name
                             of this object SHOULD be a valid regular expression, according to the
-                            ECMA 262 regular expression dialect. Each property value of this object
+                            ECMA-262 regular expression dialect. Each property value of this object
                             MUST be a valid JSON Schema.
                         </t>
                         <t>
@@ -3298,9 +3298,9 @@ https://example.com/schemas/common#/$defs/count/minimum
             <reference anchor="ecma262"
             target="https://www.ecma-international.org/ecma-262/11.0">
                 <front>
-                    <title>ECMA-262 11.0 edition specification</title>
+                    <title>ECMA-262, 11th edition specification</title>
                     <author/>
-                    <date year="2020" />
+                    <date month="June" year="2020" />
                 </front>
             </reference>
         </references>
@@ -3931,7 +3931,7 @@ https://example.com/schemas/common#/$defs/count/minimum
                             <t>$dynamic* (previously $recursive) no longer use runtime base URI determination</t>
                             <t>Reference ecma262 11th edition for regular expression support</t>
                             <t>Define Compound Schema Documents (bundle) and processing</t>
-                            <t>Reference ecma262 11th edition for regular expression support</t>
+                            <t>Reference ECMA-262, 11th edition for regular expression support</t>
                             <t></t>
                             <t></t>
                             <t></t>

jsonschema-validation.xml

@@ -352,7 +352,7 @@
                 <section title="pattern" anchor="pattern">
                     <t>
                         The value of this keyword MUST be a string. This string SHOULD be a
-                        valid regular expression, according to the ECMA 262 regular expression
+                        valid regular expression, according to the ECMA-262 regular expression
                         dialect.
                     </t>
                     <t>
@@ -898,12 +898,12 @@
                     </t>
                     <t>
                         A regular expression, which SHOULD be valid according to the
-                        <xref target="ecma262">ECMA 262</xref> regular expression dialect.
+                        <xref target="ecma262">ECMA-262</xref> regular expression dialect.
                     </t>
                     <t>
                         Implementations that validate formats MUST accept at least the subset of
-                        ECMA 262 defined in the <xref target="regexInterop">Regular Expressions</xref>
-                        section of this specification, and SHOULD accept all valid ECMA 262 expressions.
+                        ECMA-262 defined in the <xref target="regexInterop">Regular Expressions</xref>
+                        section of this specification, and SHOULD accept all valid ECMA-262 expressions.
                     </t>
                 </section>
             </section>
@@ -1318,9 +1318,9 @@
             <reference anchor="ecma262"
             target="https://www.ecma-international.org/ecma-262/11.0">
                 <front>
-                    <title>ECMA-262 11.0 edition specification</title>
+                    <title>ECMA-262, 11th edition specification</title>
                     <author/>
-                    <date year="2020" />
+                    <date month="June" year="2020" />
                 </front>
             </reference>
             <reference anchor="relative-json-pointer">
@@ -1434,7 +1434,7 @@
                         <list style="symbols">
                             <t>Correct email format RFC reference to 5321 instead of 5322</t>
                             <t>Clarified the set and meaning of "contentEncoding" values</t>
-                            <t>Reference ecma262 11th edition for regular expression support</t>
+                            <t>Reference ECMA-262, 11th edition for regular expression support</t>
                             <t></t>
                             <t></t>
                             <t></t>