Editorial: self-referential changes

These changes are an editorial suggestion, I encourage the editor(s) to implement whichever ones they feel are appropriate.

Author: gesa

index.bs

@@ -1,5 +1,5 @@
 <pre class='metadata'>
-Title: Minimum Common Web Platform API
+Title: Minimum common web API
 Shortname: minimum-common-api
 Group: wintertc
 Status: DRAFT
@@ -17,25 +17,75 @@ spec:fetch; type:method; text:fetch()
 
 <h2 class="no-num" id="intro">Introduction</h2>
 
-There is a wide base of JavaScript runtime environments being used beyond web browsers, specifically in web server and edge platforms. An important part of the reason for this is the fact that JavaScript can be used both in the server and in the client side, which reduces the specialization needed to work in different parts of a single codebase, and allows reusing code across the server and client side.
+There is a wide base of ECMAScript runtime environments being used beyond web browsers, specifically in web server and edge platforms. An major benefit to this approach is the ability to use a single programming language across multiple contexts, reducing specialization and allowing for reuse of code across the server and client side.
 
-But since code running in web browsers makes up the vast majority of JavaScript code, this is helped along if such runtimes support the same APIs as web browsers. So, unsurprisingly, more and more runtime environments have started supporting web platform APIs. However, the increase in such environments, as well as the different choices of web platform APIs, resulted in poor interoperability across such environments.
+Since code running in web browsers makes up the vast majority of ECMAScript code, runtimes are incentivised to support the same APIs as web browsers. However without a specification of which web platform APIs to be implemented, the resulting landscape provides poor interoperability across such environments.
 
-As such, this Ecma Standard defines the Minimum Common Web API specification, which lists a curated minimum subset of web platform APIs for server-side and edge runtimes to implement if they aim to be web-interoperable. This is the first edition of the standard, corresponding to the 2025 snapshot, and an additional snapshot will be published every year.
+As such, this Ecma Standard defines the Minimum common web API specification, which lists a curated minimum subset of web platform APIs for server-side and edge runtimes to implement if they aim to be web-interoperable. This is the first edition of the standard, corresponding to the 2025 snapshot. As the web platform (and non-web runtimes) grow and evolve, the committee will aim to publish with an annual cadence.
+
+This Ecma Standard was developed by Technical Committee 55 and was adopted by the General Assembly of December 2025.
+
+## Contributing to this specification>
+
+This version
+: [https://min-common-api.proposal.wintertc.org/](https://min-common-api.proposal.wintertc.org/)
+
+Issue Tracking
+: [GitHub](https://github.com/WinterTC55/proposal-minimum-common-api/issues/)
+
+Editor
+: [James M Snell](mailto:jsnell@cloudflare.com), [Cloudflare](https://cloudflare.com)
+
+***
+
+*ALTERNATIVE COPYRIGHT NOTICE AND COPYRIGHT LICENSE*
+
+*© 2025 Ecma International*
+
+*By obtaining and/or copying this work, you (the licensee) agree that you have read, understood, and will comply with the following terms and conditions.*
+
+*Permission under Ecma’s copyright to copy, modify, prepare derivative works of, and distribute this work, with or without modification, for any purpose and without fee or royalty is hereby granted, provided that you include the following on ALL copies of the work or portions thereof, including modifications:*
+
+*(i) The full text of this COPYRIGHT NOTICE AND COPYRIGHT LICENSE in a location viewable to users of the redistributed or derivative work.*
+
+*(ii) Any pre-existing intellectual property disclaimers, notices, or terms and conditions. If none exist, the Ecma alternative copyright notice should be included.*
+
+*(iii) Notice of any changes or modifications, through a copyright statement on the document such as “This document includes material copied from or derived from Minimum common web API specification.<br> Copyright © 2025 Ecma International.*
+
+**Disclaimers**
+
+THIS WORK IS PROVIDED “AS IS,” AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR THAT THE USE OF THE DOCUMENT WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
+
+COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT.
+
+The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to the work without specific, written prior permission. Title to copyright in this work will at all times remain with copyright holders.
+
+<!-- insert title here -->
 
 Scope {#scope}
-==============
+==========================
 
-This Standard defines the 2025 snapshot of the Minimum Common Web Platform API, a curated subset of APIs defined by web platform standards from W3C and WHATWG, which is intended to define a minimum set of capabilities common to Browser and Non-Browser JavaScript-based runtime environments.
+This Standard defines the 2025 snapshot of the Minimum common web API, a curated subset of APIs defined by web platform standards from W3C and WHATWG, which is intended to define a minimum set of capabilities common to browser and non-browser ECMAScript-based runtime environments.
 
 Conformance {#conformance}
 ==========================
 
-A conforming implementation of the Minimum Common Web Platform API shall conform to ECMA-262, and additionally shall provide the interfaces and properties listed in this specification, according to their definition in the corresponding W3C or WHATWG standard.
+A conforming implementation of the Minimum common web API shall conform to ECMA-262, and additionally shall provide the interfaces and properties listed in this Standard, according to their definition in the corresponding W3C or WHATWG standard.
+
+Runtime-specific extensions to any Web Platform API may be implemented by conforming runtimes. Such extensions shall be defined so that their use neither contradicts, nor causes the non-conformance of, normative functionality of any Web Platform API. It is important to carefully consider use of such extensions, as it reduces interoperability and portability of code across runtimes.
+
+This Standard does not prohibit implementing additional Web Platform APIs beyond those listed here.
+
+Note: For example, the {{Performance}} API could be extended with additional methods or properties beyond those defined in the [HR-TIME] specifications, such as those defined in the [PERFORMANCE-TIMELINE] or [USER-TIMING] specifications.
+
+Terminology {#terminology}
+==========================
+
+A conforming implementation of the Minimum Common Web Platform API shall conform to ECMA-262, and additionally shall provide the interfaces and properties listed in this Standard, according to their definition in the corresponding W3C or WHATWG standard.
 
 Runtime-specific extensions to any Web Platform API may be implemented by conforming runtimes. Such extensions shall be defined so that their use neither contradicts, nor causes the non-conformance of, normative functionality of any Web Platform API. It is important to carefully consider use of such extensions, as it reduces interoperability and portability of code across runtimes.
 
-This specification does not prohibit implementing additional Web Platform APIs beyond those listed here.
+This Standard does not prohibit implementing additional Web Platform APIs beyond those listed here.
 
 Note: For example, the {{Performance}} API could be extended with additional methods or properties beyond those defined in the [[HR-TIME]] specifications, such as those defined in the [[PERFORMANCE-TIMELINE]] or [[USER-TIMING]] specifications.
 
@@ -57,16 +107,16 @@ The Web Platform is the combination of technology standards defined by organizat
 <dfn>Web-interoperable Runtime</dfn> {#term-web-interoperable-runtime}
 ----------------------------------------------------------------------
 
-Any ECMAScript-based application runtime environment that implements the subset of Web Platform APIs outlined in this specification.
+Any ECMAScript-based application runtime environment that implements the subset of Web Platform APIs outlined in this Standard.
 
 While this term is intentionally broad to also encompass Web Browsers, the primary focus here is on outlining expectations for non-browser runtimes.
 
 Common API Index {#api-index}
 =========================
 
-All <a>Web-interoperable Runtimes</a> conforming to this specification shall implement each of the following Web Platform APIs. These should be implemented in accordance with their normative requirements except where modified here. Where any conforming runtime environment chooses (either by necessity or otherwise) to diverge from a normative requirement of the specification, clear explanations of such divergence shall be made clearly and readily available in the documentation.
+All <a>Web-interoperable Runtimes</a> conforming to this Standard shall implement each of the following <a>Web Platform</a> APIs. These should be implemented in accordance with their normative requirements except where modified here. Where any conforming runtime environment chooses (either by necessity or otherwise) to diverge from a normative requirement of the specification, clear explanations of such divergence shall be made clearly and readily available in the documentation.
 
-All of the following interfaces shall be exposed on the global object accessible through `globalThis`, unless otherwise specified in this specification:
+All of the following interfaces shall be exposed on the global object accessible through `globalThis`, unless otherwise specified in this Standard:
 
 * {{AbortController}} [[!DOM]]
 * {{AbortSignal}} [[!DOM]]
@@ -122,7 +172,7 @@ All of the following interfaces shall be exposed on the global object accessible
 * {{WritableStreamDefaultController}} [[!STREAMS]]
 * {{WritableStreamDefaultWriter}} [[!STREAMS]]
 
-All of the following methods and properties shall be exposed on the global object accessible through `globalThis`, unless otherwise specified in this specification:
+All of the following methods and properties shall be exposed on the global object accessible through `globalThis`, unless otherwise specified in this Standard:
 
 * {{globalThis}} [[!ECMASCRIPT]]
 * `globalThis.`{{atob()}} [[!HTML]]
@@ -153,14 +203,14 @@ All of the following methods and properties shall be exposed on the global objec
 Web-interoperable runtimes that support workers shall also expose {{WorkerGlobalScope/onerror}},
 {{WorkerGlobalScope/onunhandledrejection}}, {{WorkerGlobalScope/onrejectionhandled}} and
 {{WorkerGlobalScope/self}} on the worker's `globalThis`,
-unless otherwise specified in this specification. [[!HTML]]
+unless otherwise specified in this Standard. [[!HTML]]
 
 The Global Scope {#global-scope}
 ================================
 
-The exact type of the global scope (`globalThis`) can vary across runtimes. Most Web Platform APIs are defined in terms that assume Web Browser environments that specifically expose types like {{Window}}, {{WorkerGlobalScope}}, and so forth. To simplify conformance, all interfaces, methods, and properties defined by this specification shall be exposed on the runtime's relevant global scope (e.g., `globalThis.crypto`, `globalThis.ReadableStream`, etc).
+The exact type of the global scope (`globalThis`) can vary across runtimes. Most Web Platform APIs are defined in terms that assume Web Browser environments that specifically expose types like {{Window}}, {{WorkerGlobalScope}}, and so forth. To simplify conformance, all interfaces, methods, and properties defined by this Standard shall be exposed on the runtime's relevant global scope (e.g., `globalThis.crypto`, `globalThis.ReadableStream`, etc).
 
-With many runtimes, adding a new global-scoped property can introduce breaking changes when the new global conflicts with existing application code. Many Web Platform APIs define global properties using [=read only|the `readonly` attribute=]. [[!WEBIDL]] To avoid introducing breaking changes, runtimes conforming to this specification may choose to ignore the `readonly` attribute for properties being added to the global scope. This allows users of these runtimes to delete or overwrite these properties if they conflict with existing application code.
+With many runtimes, adding a new global-scoped property can introduce breaking changes when the new global conflicts with existing application code. Many Web Platform APIs define global properties using [=read only|the `readonly` attribute=]. [[!WEBIDL]] To avoid introducing breaking changes, runtimes conforming to this Standard may choose to ignore the `readonly` attribute for properties being added to the global scope. This allows users of these runtimes to delete or overwrite these properties if they conflict with existing application code.
 
 The global object on {{Window}}-like and worker environments should always be an instance of {{EventTarget}}. Web-interoperable runtimes should follow the <a>report an exception</a> algorithm, and the JavaScript <a href="https://tc39.es/ecma262/#sec-host-promise-rejection-tracker">HostPromiseRejectionTracker</a> host hook, as defined in [[!HTML]]. This includes firing the {{Window/error}}, {{Window/unhandledrejection}} and {{Window/rejectionhandled}} events on the global object.