Editorial: Document DurationFormat in summary sections (#966)

Author: gibson042

spec/annexes.html

@@ -85,6 +85,17 @@ <h1>Implementation Dependent Behaviour</h1>
         </li>
       </ul>
     </li>
+    <li>
+      In DurationFormat:
+      <ul>
+        <li>
+          The set of supported *"nu"* key values (numbering systems) per locale (<emu-xref href="#sec-Intl.DurationFormat-internal-slots"></emu-xref>)
+        </li>
+        <li>
+          The digital formatting configuration (use of two-digit hours with style *"numeric"* and separators for numeric hours, minutes, and seconds) per locale (<emu-xref href="#sec-Intl.DurationFormat-internal-slots"></emu-xref>)
+        </li>
+      </ul>
+    </li>
     <li>
       In ListFormat:
       <ul>

spec/conventions.html

@@ -61,6 +61,11 @@ <h1>Well-Known Intrinsic Objects</h1>
           <td>`Intl.DisplayNames`</td>
           <td>The `Intl.DisplayNames` constructor (<emu-xref href="#sec-intl-displaynames-constructor"></emu-xref>)</td>
         </tr>
+        <tr>
+          <td>%Intl.DurationFormat%</td>
+          <td>`Intl.DurationFormat`</td>
+          <td>The `Intl.DurationFormat` constructor (<emu-xref href="#sec-intl-durationformat-constructor"></emu-xref>)</td>
+        </tr>
         <tr>
           <td>%Intl.ListFormat%</td>
           <td>`Intl.ListFormat`</td>

spec/durationformat.html

@@ -19,7 +19,7 @@ <h1>Intl.DurationFormat ( [ _locales_ [ , _options_ ] ] )</h1>
         1. Let _matcher_ be ? GetOption(_options_, *"localeMatcher"*, ~string~, « *"lookup"*, *"best fit"* », *"best fit"*).
         1. Let _numberingSystem_ be ? GetOption(_options_, *"numberingSystem"*, ~string~, ~empty~, *undefined*).
         1. If _numberingSystem_ is not *undefined*, then
-          1. If _numberingSystem_ does not match the Unicode Locale Identifier `type` nonterminal, throw a *RangeError* exception.
+          1. If _numberingSystem_ cannot be matched by the <code>type</code> Unicode locale nonterminal, throw a *RangeError* exception.
         1. Let _opt_ be the Record { [[localeMatcher]]: _matcher_, [[nu]]: _numberingSystem_ }.
         1. Let _r_ be ResolveLocale(%Intl.DurationFormat%.[[AvailableLocales]], _requestedLocales_, _opt_, %Intl.DurationFormat%.[[RelevantExtensionKeys]], %Intl.DurationFormat%.[[LocaleData]]).
         1. Set _durationFormat_.[[Locale]] to _r_.[[Locale]].

spec/overview.html

@@ -23,7 +23,7 @@ <h1>API Overview</h1>
       This specification is designed to complement the ECMAScript 2025 Language Specification by providing key language-sensitive functionality. The API can be added to an implementation of the ECMAScript 2025 Language Specification (ECMA-262 16<sup>th</sup> Edition, or successor) in whole or in part. This specification introduces new language values observable to ECMAScript code (such as the value of a [[FallbackSymbol]] internal slot and the set of values transitively reachable from %Intl% by <emu-xref href="#sec-property-accessors">property access</emu-xref>), and also refines the definition of some functions specified in ECMA-262 (as described below). Neither category prohibits behaviour that is otherwise permitted for values and interfaces defined in ECMA-262, in order to support adoption of this specification by any implementation of ECMA-262.
     </p>
     <p>
-      This specification provides several key pieces of language-sensitive functionality that are required in most applications: String comparison (collation), number formatting, date and time formatting, relative time formatting, display names, list formatting, locale selection and operation, pluralization rules, case conversion, and text segmentation. While the ECMAScript 2025 Language Specification provides functions for this basic functionality (on <emu-xref href="#sec-array.prototype">Array.prototype</emu-xref>: `toLocaleString`; on <emu-xref href="#sec-string.prototype">String.prototype</emu-xref>: `localeCompare`, `toLocaleLowerCase`, `toLocaleUpperCase`; on <emu-xref href="#sec-number.prototype">Number.prototype</emu-xref>: `toLocaleString`; on <emu-xref href="#sec-date.prototype">Date.prototype</emu-xref>: `toLocaleString`, `toLocaleDateString`, and `toLocaleTimeString`), their actual behaviour is left largely implemenation-defined. This specification provides additional functionality, control over the language and over details of the behaviour to be used, and a more complete specification of required functionality.
+      This specification provides several key pieces of language-sensitive functionality that are required in most applications: locale selection and inspection, string comparison (collation) and case conversion, pluralization rules, text segmentation, and formatting of numbers, absolute and relative dates and times, durations, and lists. While the ECMAScript 2025 Language Specification provides functions for this basic functionality (on <emu-xref href="#sec-array.prototype">Array.prototype</emu-xref>: `toLocaleString`; on <emu-xref href="#sec-string.prototype">String.prototype</emu-xref>: `localeCompare`, `toLocaleLowerCase`, `toLocaleUpperCase`; on <emu-xref href="#sec-number.prototype">Number.prototype</emu-xref>: `toLocaleString`; on <emu-xref href="#sec-date.prototype">Date.prototype</emu-xref>: `toLocaleString`, `toLocaleDateString`, and `toLocaleTimeString`), their actual behaviour is left largely implemenation-defined. This specification provides additional functionality, control over the language and over details of the behaviour to be used, and a more complete specification of required functionality.
     </p>
 
     <p>Applications can use the API in two ways:</p>