Editorial: clean up references to ecma262

Rename all references to es202x to ECMA-262 with a dfn that could be
updated more conveninently and get rid of redundant editorial note.

Furthermore, it simplifies every remaining reference to ECMA-262 in the
spec to be better and easier to maintain in the future.

Co-authored-by: Richard Gibson <[email protected]>

Author: ryzokuken

spec/collator.html

@@ -223,7 +223,7 @@ <h1>
           <dd>
             The returned Number represents the result of an implementation-defined locale-sensitive String comparison of _x_ with _y_.
             The result is intended to correspond with a sort order of String values according to the effective locale and collation options of _collator_, and will be negative when _x_ is ordered before _y_, positive when _x_ is ordered after _y_, and zero in all other cases (representing no relative ordering between _x_ and _y_).
-            String values must be interpreted as UTF-16 code unit sequences as described in es2026, <emu-xref href="#sec-ecmascript-language-types-string-type"></emu-xref>, and a surrogate pair (a code unit in the range 0xD800 to 0xDBFF followed by a code unit in the range 0xDC00 to 0xDFFF) within a string must be interpreted as the corresponding code point.
+            String values must be interpreted as UTF-16 code unit sequences as described in ECMA-262, <emu-xref href="#sec-ecmascript-language-types-string-type"></emu-xref>, and a surrogate pair (a code unit in the range 0xD800 to 0xDBFF followed by a code unit in the range 0xDC00 to 0xDFFF) within a string must be interpreted as the corresponding code point.
           </dd>
         </dl>
 

spec/conformance.html

@@ -1,6 +1,6 @@
 <emu-clause id="conformance">
   <h1>Conformance</h1>
-  <p>A conforming implementation of this specification must conform to the ECMAScript 2026 Language Specification (ECMA-262 17<sup>th</sup> Edition, or successor), and must provide and support all the objects, properties, functions, and program semantics described in this specification. Nothing in this specification is intended to allow behaviour that is otherwise prohibited by ECMA-262, and any such conflict should be considered an editorial error rather than an override of constraints from ECMA-262.</p>
+  <p>A conforming implementation of this specification must conform to ECMA-262, and must provide and support all the objects, properties, functions, and program semantics described in this specification. Nothing in this specification is intended to allow behaviour that is otherwise prohibited by ECMA-262, and any such conflict should be considered an editorial error rather than an override of constraints from ECMA-262.</p>
   <p>A conforming implementation is permitted to provide additional objects, properties, and functions beyond those described in this specification. In particular, a conforming implementation is permitted to provide properties not described in this specification, and values for those properties, for objects that are described herein. A conforming implementation is not permitted to add optional arguments to the functions defined in this specification.</p>
   <p>A conforming implementation is permitted to accept additional values, and then have implementation-defined behaviour instead of throwing a *RangeError*, for the following properties of _options_ arguments:</p>
   <ul>

spec/conventions.html

@@ -1,17 +1,17 @@
 <emu-clause id="conventions">
   <h1>Notational Conventions</h1>
 
-  <p>This standard uses a subset of the notational conventions of the ECMAScript 2026 Language Specification (ECMA-262 17<sup>th</sup> Edition), as es2026:</p>
+  <p>This standard uses a subset of the notational conventions of ECMA-262:</p>
 
   <ul>
-    <li>Object Internal Methods and Internal Slots, as described in es2026, <emu-xref href="#sec-object-internal-methods-and-internal-slots"></emu-xref>.</li>
-    <li>Algorithm conventions, as described in es2026, <emu-xref href="#sec-algorithm-conventions"></emu-xref>, and the use of abstract operations, as described in es2026, <emu-xref href="#sec-type-conversion"></emu-xref>, <emu-xref href="#sec-testing-and-comparison-operations"></emu-xref>, <emu-xref href="#sec-operations-on-objects"></emu-xref>, <emu-xref href="#sec-operations-on-iterator-objects"></emu-xref>.</li>
-    <li>Internal Slots, as described in es2026, <emu-xref href="#sec-ordinary-object-internal-methods-and-internal-slots"></emu-xref>.</li>
-    <li>The List and Record Specification Type, as described in es2026, <emu-xref href="#sec-list-and-record-specification-type"></emu-xref>.</li>
+    <li>Object Internal Methods and Internal Slots, as described in <emu-xref href="#sec-object-internal-methods-and-internal-slots" title></emu-xref>.</li>
+    <li>Algorithm conventions, as described in <emu-xref href="#sec-algorithm-conventions" title></emu-xref>, and the use of abstract operations as described in <emu-xref href="#sec-type-conversion" title></emu-xref>, <emu-xref href="#sec-testing-and-comparison-operations" title></emu-xref>, <emu-xref href="#sec-operations-on-objects" title></emu-xref>, and <emu-xref href="#sec-operations-on-iterator-objects" title></emu-xref>.</li>
+    <li>Internal Slots, as described in <emu-xref href="#sec-ordinary-object-internal-methods-and-internal-slots" title></emu-xref>.</li>
+    <li>The List and Record Specification Type, as described in <emu-xref href="#sec-list-and-record-specification-type" title></emu-xref>.</li>
   </ul>
 
   <emu-note>
-    As described in the ECMAScript Language Specification, algorithms are used to precisely specify the required semantics of ECMAScript constructs, but are not intended to imply the use of any specific implementation technique. Internal slots are used to define the semantics of object values, but are not part of the API. They are defined purely for expository purposes. An implementation of the API must behave as if it produced and operated upon internal slots in the manner described here.
+    As described in ECMA-262, algorithms are used to precisely specify the required semantics of ECMAScript constructs, but are not intended to imply the use of any specific implementation technique. Internal slots are used to define the semantics of object values, but are not part of the API. They are defined purely for expository purposes. An implementation of the API must behave as if it produced and operated upon internal slots in the manner described here.
   </emu-note>
 
   <p>As an extension to the Record Specification Type, the notation “[[&lt;_name_>]]” denotes a field whose name is given by the variable _name_, which must have a String value. For example, if a variable _s_ has the value *"a"*, then [[&lt;_s_>]] denotes the field [[a]].</p>
@@ -21,7 +21,7 @@ <h1>Notational Conventions</h1>
   <emu-clause id="sec-402-well-known-intrinsic-objects">
     <h1>Well-Known Intrinsic Objects</h1>
 
-    <p>The following table extends the Well-Known Intrinsic Objects table defined in es2026, <emu-xref href="#sec-well-known-intrinsic-objects"></emu-xref>.</p>
+    <p>The following table extends the Well-Known Intrinsic Objects table defined in <emu-xref href="#sec-well-known-intrinsic-objects" title></emu-xref>.</p>
 
     <emu-table id="table-402-well-known-intrinsic-objects">
       <emu-caption>Well-known Intrinsic Objects (Extensions)</emu-caption>

spec/datetimeformat.html

@@ -1439,7 +1439,7 @@ <h1>
       </h1>
       <dl class="header">
         <dt>description</dt>
-        <dd>It interprets _x_ as a time value as specified in es2026, <emu-xref href="#sec-time-values-and-time-range"></emu-xref>, and creates the corresponding parts according to the effective locale and the formatting options of _dateTimeFormat_.</dd>
+        <dd>It interprets _x_ as a time value as specified in ECMA-262, <emu-xref href="#sec-time-values-and-time-range"></emu-xref>, and creates the corresponding parts according to the effective locale and the formatting options of _dateTimeFormat_.</dd>
       </dl>
       <emu-alg>
         1. Let _x_ be TimeClip(_x_).
@@ -1506,7 +1506,7 @@ <h1>
       </h1>
       <dl class="header">
         <dt>description</dt>
-        <dd>It interprets _x_ and _y_ as time values as specified in es2026, <emu-xref href="#sec-time-values-and-time-range"></emu-xref>, and creates the corresponding parts according to the effective locale and the formatting options of _dateTimeFormat_.</dd>
+        <dd>It interprets _x_ and _y_ as time values as specified in ECMA-262, <emu-xref href="#sec-time-values-and-time-range"></emu-xref>, and creates the corresponding parts according to the effective locale and the formatting options of _dateTimeFormat_.</dd>
       </dl>
       <emu-alg>
         1. Set _x_ to TimeClip(_x_).

spec/introduction.html

@@ -1,7 +1,7 @@
 <emu-intro id="introduction">
   <h1>Introduction</h1>
   <p>This specification's source can be found at <a href="https://github.com/tc39/ecma402">https://github.com/tc39/ecma402</a>.</p>
-  <p>The ECMAScript 2026 Internationalization API Specification (ECMA-402 13<sup>th</sup> Edition), provides key language sensitive functionality as a complement to the ECMAScript 2026 Language Specification (ECMA-262 17<sup>th</sup> Edition or successor). Its functionality has been selected from that of well-established internationalization APIs such as those of the <dfn id="icu">Internationalization Components for Unicode (ICU) library</dfn> (<a href="https://unicode-org.github.io/icu-docs/">https://unicode-org.github.io/icu-docs/</a>), of the .NET framework, or of the Java platform.</p>
+  <p>The ECMAScript 2026 Internationalization API Specification (ECMA-402 13<sup>th</sup> Edition), provides key language sensitive functionality as a complement to ECMA-262. Its functionality has been selected from that of well-established internationalization APIs such as those of the <dfn id="icu">Internationalization Components for Unicode (ICU) library</dfn> (<a href="https://unicode-org.github.io/icu-docs/">https://unicode-org.github.io/icu-docs/</a>), of the .NET framework, or of the Java platform.</p>
   <p>The 1<sup>st</sup> Edition API was developed by an ad-hoc group established by Ecma TC39 in September 2010 based on a proposal by Nebojša Ćirić and Jungshik Shin.</p>
   <p>The 2<sup>nd</sup> Edition API was adopted by the General Assembly of June 2015, as a complement to the ECMAScript 6<sup>th</sup> Edition.</p>
   <p>The 3<sup>rd</sup> Edition API was the first edition released under Ecma TC39's new yearly release cadence and open development process. A plain-text source document was built from the ECMA-402 source document to serve as the base for further development entirely on GitHub. Over the year of this standard's development, dozens of pull requests and issues were filed representing several of bug fixes, editorial fixes and other improvements. Additionally, numerous software tools were developed to aid in this effort including Ecmarkup, Ecmarkdown, and Grammarkdown.</p>