diff --git a/microsoft-edge/toc.yml b/microsoft-edge/toc.yml
index 4d7a43dc9c..c4cd1cadb0 100644
--- a/microsoft-edge/toc.yml
+++ b/microsoft-edge/toc.yml
@@ -30,6 +30,10 @@
           href: ./web-platform/release-notes/index.md
           displayName: what's new, announcements
 
+        - name: Microsoft Edge 142
+          href: ./web-platform/release-notes/142.md
+          displayName: Microsoft Edge 142 web platform release notes (Oct. 2025)  # page title
+
         - name: Microsoft Edge 141
           href: ./web-platform/release-notes/141.md
           displayName: Microsoft Edge 141 web platform release notes (Oct. 2025)  # page title
diff --git a/microsoft-edge/web-platform/release-notes/135.md b/microsoft-edge/web-platform/release-notes/135.md
index 8f6f36551f..f447bb0c25 100644
--- a/microsoft-edge/web-platform/release-notes/135.md
+++ b/microsoft-edge/web-platform/release-notes/135.md
@@ -39,7 +39,6 @@ To stay up-to-date and get the latest web platform features, download a preview
     * [Create service worker client and inherit service worker controller for iframe with `srcdoc`](#create-service-worker-client-and-inherit-service-worker-controller-for-iframe-with-srcdoc)
     * [Dispatching click events to captured pointer](#dispatching-click-events-to-captured-pointer)
     * [Float16Array](#float16array)
-    * [HSTS tracking prevention](#hsts-tracking-prevention)
     * [`sourceElement` property for `NavigateEvent`](#sourceelement-property-for-navigateevent)
     * [PerformanceNavigationTiming API NotRestoredReasons name change](#performancenavigationtiming-api-notrestoredreasons-name-change)
     * [Observable API](#observable-api)
@@ -244,14 +243,6 @@ If a pointer is captured while the `pointerup` event is being dispatched, the `c
 The `Float16Array` typed array is now supported.  Number values are rounded to half-precision float-point format (IEEE FP16) when writing into a `Float16Array` instance.
 
 
-<!-- ---------- -->
-###### HSTS tracking prevention
-
-Mitigates user tracking by third-parties via the HTTP Strict Transport Security (HSTS) cache.
-
-This feature only allows HSTS upgrades for top-level navigations, and blocks HSTS upgrades for sub-resource requests.  Blocking such an HSTS upgrade makes it infeasible for third-party sites to use the HSTS cache in order to track a user across the web.
-
-
 <!-- ---------- -->
 ###### `sourceElement` property for `NavigateEvent`
 
diff --git a/microsoft-edge/web-platform/release-notes/139.md b/microsoft-edge/web-platform/release-notes/139.md
index 85fccd4929..9670544921 100644
--- a/microsoft-edge/web-platform/release-notes/139.md
+++ b/microsoft-edge/web-platform/release-notes/139.md
@@ -37,7 +37,6 @@ To stay up-to-date and get the latest web platform features, download a preview
     * [WebGPU: 3D texture support for BC and ASTC compressed formats](#webgpu-3d-texture-support-for-bc-and-astc-compressed-formats)
     * [WebXR depth sensing performance improvements](#webxr-depth-sensing-performance-improvements)
   * [PWA features](#pwa-features)
-    * [New PWA manifest update algorithm](#new-pwa-manifest-update-algorithm)
     * [Web app scope extensions](#web-app-scope-extensions)
   * [Removed features](#removed-features)
     * [Remove auto-detection of ISO-2022-JP charset in HTML](#remove-auto-detection-of-iso-2022-jp-charset-in-html)
@@ -285,23 +284,6 @@ See also:
 #### PWA features
 
 
-<!-- ---------- -->
-###### New PWA manifest update algorithm
-
-The updating of installed PWAs uses a new algorithm.  The new update algorithm makes the update process more deterministic and predictable, and gives you more control over whether, and when, updates should apply to existing installations of your app.
-
-The new update algorithm has the following benefits:
-
-* **Consistency:** The algorithm provides a consistent way to detect when a manifest update should happen.
-* **Reduced user interruptions:** App users won't see the update dialog, except when it's strictly necessary, such as to confirm security-sensitive changes.
-* **Browser flexibility:** Microsoft Edge can now allow known, trusted apps to update without displaying a notification, and can block updates for known bad apps.
-* **Developer control:** You have more control over when the update dialog is shown to users.
-* **Reduce network traffic:** Unnecessary network traffic is minimized.
-
-See also:
-* [Predictable Web App Updating - Explainer](https://github.com/WICG/manifest-incubations/blob/gh-pages/predictable-app-updating.md)
-
-
 <!-- ---------- -->
 ###### Web app scope extensions
 
diff --git a/microsoft-edge/web-platform/release-notes/140.md b/microsoft-edge/web-platform/release-notes/140.md
index 858b1c74e1..6bb8ec1be0 100644
--- a/microsoft-edge/web-platform/release-notes/140.md
+++ b/microsoft-edge/web-platform/release-notes/140.md
@@ -27,9 +27,6 @@ To stay up-to-date and get the latest web platform features, download a preview
     * [View transitions: more animation properties are inherited](#view-transitions-more-animation-properties-are-inherited)
     * [Nested view transitions](#nested-view-transitions)
     * [`font-variation-settings` descriptor in `@font-face` rules](#font-variation-settings-descriptor-in-font-face-rules)
-  * [SVG features](#svg-features)
-    * [CSS `width` and `height` support for SVG `<use>` element](#css-width-and-height-support-for-svg-use-element)
-    * [Support `download` attribute in SVG `<a>` element](#support-download-attribute-in-svg-a-element)
   * [Web APIs](#web-apis)
     * [`__Http-` and `__HostHttp-` cookie name prefixes](#__http--and-__hosthttp--cookie-name-prefixes)
     * [`overscroll-behavior` propagation from `<html>` to the viewport](#overscroll-behavior-propagation-from-html-to-the-viewport)
@@ -214,56 +211,6 @@ See also:
 * [@font-face](https://developer.mozilla.org/docs/Web/CSS/@font-face) at MDN.
 
 
-<!-- ------------------------------ -->
-#### SVG features
-
-
-<!-- ---------- -->
-###### CSS width and height support for SVG `<use>` element
-
-The SVG `<use>` element now supports the `width` and `height` CSS properties.
-
-This allows you to control the sizing of SVG elements through CSS, such as to improve their responsiveness.
-
-With this feature, the following two HTML snippets now produce the same output:
-
-```html
-<svg width="100px" height="100px">
- <defs>
-    <symbol id="sym" width="80" height="80">
-      <rect width="100" height="100" fill="green" />
-    </symbol>
-  </defs>
-  <use href="#sym" style="width:40px; height:40px" />
-</svg>
-```
-
-```html
-<svg width="100px" height="100px">
- <defs>
-    <symbol id="sym" width="80" height="80">
-      <rect width="100" height="100" fill="green" />
-    </symbol>
-  </defs>
-  <use href="#sym" width="40" height="40" />
-</svg>
-```
-
-See also:
-* [`<svg>`](https://developer.mozilla.org/docs/Web/SVG/Reference/Element/svg) at MDN.
-
-
-<!-- ---------- -->
-###### Support `download` attribute in SVG `<a>` element 
-
-The `download` attribute is now supported by SVG `<a>` elements.
-
-The `download` attribute enables you to specify that the target of an SVG hyperlink should be downloaded rather than navigated to.
-
-See also:
-* [`<a>`](https://developer.mozilla.org/docs/Web/SVG/Reference/Element/a) at MDN.
-
-
 <!-- ------------------------------ -->
 #### Web APIs
 
diff --git a/microsoft-edge/web-platform/release-notes/141.md b/microsoft-edge/web-platform/release-notes/141.md
index dade0a1d84..f2b641bb4d 100644
--- a/microsoft-edge/web-platform/release-notes/141.md
+++ b/microsoft-edge/web-platform/release-notes/141.md
@@ -5,10 +5,9 @@ author: MSEdgeTeam
 ms.author: msedgedevrel
 ms.topic: conceptual
 ms.service: microsoft-edge
-ms.date: 09/04/2025
+ms.date: 10/02/2025
 ---
 # Microsoft Edge 141 web platform release notes (Oct. 2025)
-<!-- todo: check date field above -->
 
 The following are the new web platform features and updates in Microsoft Edge 141, which releases on October 2, 2025.
 
@@ -21,11 +20,9 @@ To stay up-to-date and get the latest web platform features, download a preview
 * [Web platform features](#web-platform-features)
   * [CSS features](#css-features)
     * [CSS `::search-text` pseudo-element](#css-search-text-pseudo-element)
-    * [`document.activeViewTransition` property](#documentactiveviewtransition-property)
     * [Support `width` and `height` presentational attributes on nested `<svg>` elements](#support-width-and-height-presentational-attributes-on-nested-svg-elements)
   * [Web APIs](#web-apis)
     * [`ariaNotify()` API](#arianotify-api)
-    * [`dataTransfer` property for `insertFromPaste`, `insertFromDrop`, and `insertReplacementText` input events](#datatransfer-property-for-insertfrompaste-insertfromdrop-and-insertreplacementtext-input-events)
     * [IndexedDB `getAllRecords()` method and `direction` option for `getAll()` and `getAllKeys()`](#indexeddb-getallrecords-method-and-direction-option-for-getall-and-getallkeys)
     * [Navigation API `precommitHandler`](#navigation-api-precommithandler)
     * [`windowAudio` option for `getDisplayMedia()`](#windowaudio-option-for-getdisplaymedia)
@@ -81,24 +78,6 @@ See also:
 * [::search-text](https://drafts.csswg.org/css-pseudo-4/#selectordef-search-text) in _CSS Pseudo-Elements Module Level 4_.
 
 
-<!-- ---------- -->
-###### `document.activeViewTransition` property
-
-The `document.activeViewTransition` property provides access to the currently running view transition, whether this transition is on a single web page, or between two web pages.
-
-The View Transition API allows you to create visual transitions between different states of a single page, or between multiple pages.
-
-For transitions within single pages, the `document.startViewTransition()` method returns a transition object.  The `document.activeViewTransition` property now provides access to this transition object, which means you no longer need to store the `document.startViewTransition()` return value.
-
-For transitions between multiple pages, the `document.activeViewTransition` property now gives you access to the currently running transition object, for the duration of the transition. This is in addition to the `pageswap` and `pagereveal` events.
-
-See also:
-* [View Transition API](https://developer.mozilla.org/docs/Web/API/View_Transition_API) at MDN.
-* [Document: startViewTransition() method](https://developer.mozilla.org/docs/Web/API/Document/startViewTransition) at MDN.
-* [Window: pageswap event](https://developer.mozilla.org/docs/Web/API/Window/pageswap_event) at MDN.
-* [Window: pagereveal event](https://developer.mozilla.org/docs/Web/API/Window/pagereveal_event) at MDN.
-
-
 <!-- ---------- -->
 ###### Support `width` and `height` presentational attributes on nested `<svg>` elements
 
@@ -130,45 +109,6 @@ See also:
 * [`<svg>`](https://developer.mozilla.org/docs/Web/SVG/Reference/Element/svg) at MDN.
 
 
-<!-- ---------- 
-todo: this is planned to ship with 142 after all. Keeping here until we need it for the 142 release notes.
-###### Range syntax for style container queries and `if()` functions
-
-The CSS `@container style()` queries and `if()` functions now support the range syntax.
-
-The range syntax makes it possible to compare custom properties and values by using the `<` and `>` operators.
-
-For a comparison to be valid, both sides of the comparison must resolve to the same data type.  The range syntax is limited to the following numeric types: `<length>`, `<number>`, `<percentage>`, `<angle>`, `<time>`, `<frequency>`, and `<resolution>`.
-
-Example comparing a custom property with a literal length:
-
-```css
-@container style(--inner-padding > 1em) {
-  .card { border: 2px solid; }
-}
-```
-
-Example comparing two literal values:
-
-```css
-@container style(1em < 20px) {
-  ...
-}
-```
-
-Example comparing a value from the `attr()` substitution function with a literal value:
-
-```css
-.item-grid {
-  background-color: if(style(attr(data-columns, type<number>) > 2): lightblue; else: white);
-}
-```
-
-See also:
-* []()
--->
-
-
 <!-- ------------------------------ -->
 #### Web APIs
 
@@ -182,22 +122,6 @@ See also:
 * [Creating a more accessible web with Aria Notify](https://blogs.windows.com/msedgedev/2025/05/05/creating-a-more-accessible-web-with-aria-notify/).
 
 
-<!-- ---------- -->
-###### `dataTransfer` property for `insertFromPaste`, `insertFromDrop`, and `insertReplacementText` input events
-
-The input event objects of type `insertFromPaste`, `insertFromDrop`, and `insertReplacementText` now have a `dataTransfer` property, for better interoperability with other browsers.
-
-The `dataTransfer` property provides access to the clipboard or drag-drop data when the user edits text within a `contenteditable` element.  The same data is also available on the `dataTransfer` property of `beforeinput` events.
-
-This feature only applies to `contenteditable` elements.
-
-See also:
-* [DataTransfer](https://developer.mozilla.org/docs/Web/API/DataTransfer) at MDN.
-* [InputEvent: inputType property](https://developer.mozilla.org/docs/Web/API/InputEvent/inputType) at MDN.
-* [HTML contenteditable global attribute](https://developer.mozilla.org/docs/Web/HTML/Reference/Global_attributes/contenteditable) at MDN.
-* [Element: beforeinput event](https://developer.mozilla.org/docs/Web/API/Element/beforeinput_event) at MDN.
-
-
 <!-- ---------- -->
 ###### IndexedDB `getAllRecords()` method and `direction` option for `getAll()` and `getAllKeys()`
 
diff --git a/microsoft-edge/web-platform/release-notes/142.md b/microsoft-edge/web-platform/release-notes/142.md
new file mode 100644
index 0000000000..c65853d178
--- /dev/null
+++ b/microsoft-edge/web-platform/release-notes/142.md
@@ -0,0 +1,479 @@
+---
+title: Microsoft Edge 142 web platform release notes (Oct. 2025)
+description: Microsoft Edge 142 web platform release notes (Oct. 2025)
+author: MSEdgeTeam
+ms.author: msedgedevrel
+ms.topic: conceptual
+ms.service: microsoft-edge
+ms.date: 10/19/2025
+---
+# Microsoft Edge 142 web platform release notes (Oct. 2025)
+<!-- todo: after Sep. 30, 2025, change date: yaml field to:
+ms.date: 10/30/2025
+-->
+
+The following are the new web platform features and updates in Microsoft Edge 142, which releases on October 30, 2025.
+
+To stay up-to-date and get the latest web platform features, download a preview channel of Microsoft Edge (Beta, Dev, or Canary); go to [Become a Microsoft Edge Insider](https://www.microsoft.com/edge/download/insider).
+
+**Detailed contents:**
+
+* [Edge DevTools](#edge-devtools)
+* [WebView2](#webview2)
+* [CSS features](#css-features)
+   * [AccentColor and AccentColorText system colors](#accentcolor-and-accentcolortext-system-colors)
+   * [CSS font-language-override property](#css-font-language-override-property)
+   * [document.activeViewTransition property](#documentactiveviewtransition-property)
+   * [Range syntax for style container queries and if() functions](#range-syntax-for-style-container-queries-and-if-functions)
+* [SVG features](#svg-features)
+   * [Support download attribute in SVG \<a\> element](#support-download-attribute-in-svg-a-element)
+   * [CSS width and height support for SVG \<use\> element](#css-width-and-height-support-for-svg-use-element)
+* [Web APIs](#web-apis)
+   * [Clear the window.name value for cross-site navigations that switch browsing context group](#clear-the-windowname-value-for-cross-site-navigations-that-switch-browsing-context-group)
+   * [clipboardchange event](#clipboardchange-event)
+   * [dataTransfer property for insertFromPaste, insertFromDrop, and insertReplacementText input events](#datatransfer-property-for-insertfrompaste-insertfromdrop-and-insertreplacementtext-input-events)
+   * [Show third-party iframe origins in the FedCM UI](#show-third-party-iframe-origins-in-the-fedcm-ui)
+   * [HSTS tracking prevention](#hsts-tracking-prevention)
+   * [Only fire pointerrawupdate events in secure contexts](#only-fire-pointerrawupdate-events-in-secure-contexts)
+   * [Enable sticky user activation across same-origin navigations](#enable-sticky-user-activation-across-same-origin-navigations)
+   * [New PWA manifest update algorithm](#new-pwa-manifest-update-algorithm)
+   * [Web Speech API contextual biasing](#web-speech-api-contextual-biasing)
+* [Origin trials in Microsoft Edge](#origin-trials-in-microsoft-edge)
+   * [AriaNotify API](#arianotify-api)
+   * [Ad Selection API](#ad-selection-api)
+   * [Acquisition Info API](#acquisition-info-api)
+* [Chromium origin trials](#chromium-origin-trials)
+   * [WebAssembly Custom Descriptors](#webassembly-custom-descriptors)
+   * [WebGPU Compatibility Mode](#webgpu-compatibility-mode)
+   * [Fetch retry](#fetch-retry)
+   * [Prompt API](#prompt-api)
+   * [Incoming Call Notifications](#incoming-call-notifications)
+   * [Full frame rate render blocking attribute](#full-frame-rate-render-blocking-attribute)
+
+
+<!-- ====================================================================== -->
+## Edge DevTools
+
+See [What's New in Microsoft Edge DevTools](../../devtools/whats-new/whats-new.md).
+<!-- todo: when it exists in Oct 2025, use instead:
+See [What's New in DevTools (Microsoft Edge 142)](../../devtools/whats-new/2025/10/devtools-142.md).
+-->
+
+
+<!-- ====================================================================== -->
+## WebView2
+
+See [Release Notes for the WebView2 SDK](../../webview2/release-notes/index.md).
+<!-- todo: when exists in Oct 2025, use instead:
+For WebView2, see [1.0.n.n](../../webview2/release-notes/index.md#10nnnnnn) in _Release Notes for the WebView2 SDK_ (Oct 2025).
+-->
+
+
+<!-- ====================================================================== -->
+## CSS features
+
+Below are the new Cascading Style Sheets (CSS) features in Microsoft Edge.
+
+
+<!-- ------------------------------ -->
+#### `AccentColor` and `AccentColorText` system colors
+
+The `AccentColor` and `AccentColorText` system colors can now be used as CSS color values to access the system accent color that's specified on the user's device.
+
+See also:
+* [\<system-color\>](https://developer.mozilla.org/docs/Web/CSS/system-color) at MDN.
+* [system Colors](https://drafts.csswg.org/css-color/#css-system-colors) in _CSS Color Module Level 4_.
+
+
+<!-- ------------------------------ -->
+#### CSS `font-language-override` property
+
+The `font-language-override` CSS property allows you to override the system language used for OpenType glyph substitution, by specifying a four-character language tag directly in CSS.
+
+This enables finer-grained typographic control for multilingual content, or for fonts with language-specific glyph variants.
+
+See also:
+* [font-language-override](https://developer.mozilla.org/docs/Web/CSS/font-language-override) at MDN.
+
+
+<!-- ------------------------------ -->
+#### `document.activeViewTransition` property
+
+The `document.activeViewTransition` property provides access to the currently running view transition, regardless of whether this transition is on a single webpage, or between two webpages.
+
+The View Transition API allows you to create visual transitions between different states of a single webpage, or between multiple webpages.
+
+* For transitions within single webpages, the `document.startViewTransition()` method returns a transition object.  The `document.activeViewTransition` property now provides access to this transition object, which means you no longer need to store the `document.startViewTransition()` return value.
+
+* For transitions between multiple webpages, the `document.activeViewTransition` property now gives you access to the currently running transition object, for the duration of the transition.  This is in addition to the `pageswap` and `pagereveal` events.
+
+See also:
+* [View Transition API](https://developer.mozilla.org/docs/Web/API/View_Transition_API) at MDN.
+* [Document: startViewTransition() method](https://developer.mozilla.org/docs/Web/API/Document/startViewTransition) at MDN.
+* [Window: pageswap event](https://developer.mozilla.org/docs/Web/API/Window/pageswap_event) at MDN.
+* [Window: pagereveal event](https://developer.mozilla.org/docs/Web/API/Window/pagereveal_event) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Range syntax for style container queries and `if()` functions
+
+The CSS `@container style()` queries and `if()` functions now support the range syntax.  The range syntax makes it possible to compare custom properties and values by using the `<` and `>` operators.
+
+For a comparison to be valid, both sides of the comparison must resolve to the same data type.  The range syntax is limited to the following numeric types:
+* `<length>`
+* `<number>`
+* `<percentage>`
+* `<angle>`
+* `<time>`
+* `<frequency>`
+* `<resolution>`
+
+Example comparing a custom property with a literal length:
+
+```css
+@container style(--inner-padding > 1em) {
+   .card { border: 2px solid; }
+}
+```
+
+Example comparing two literal values:
+
+```css
+@container style(1em < 20px) {
+   ...
+}
+```
+
+Example comparing a value from the `attr()` substitution function with a literal value:
+
+```css
+.item-grid {
+   background-color: if(style(attr(data-columns, type<number>) > 2): lightblue; else: white);
+}
+```
+
+See also:
+* [Using container size and style queries](https://developer.mozilla.org/docs/Web/CSS/CSS_containment/Container_size_and_style_queries) at MDN.
+* [if()](https://developer.mozilla.org/docs/Web/CSS/if) at MDN.
+
+
+<!-- ====================================================================== -->
+## SVG features
+<!-- https://developer.mozilla.org/docs/Web/SVG -->
+
+Below are the new Scalable Vector Graphics (SVG) features in Microsoft Edge.
+
+
+<!-- ------------------------------ -->
+#### Support `download` attribute in SVG `<a>` element
+
+The `download` attribute is now supported by SVG `<a>` elements.
+
+The `download` attribute enables you to specify that the target of an SVG hyperlink should be downloaded rather than navigated to.
+
+See also:
+* [`<a>`](https://developer.mozilla.org/docs/Web/HTML/Reference/Elements/a#download) at MDN.
+
+
+<!-- ------------------------------ -->
+#### CSS width and height support for SVG `<use>` element
+
+The SVG `<use>` element now supports the `width` and `height` CSS properties.
+
+This allows you to control the sizing of SVG elements through CSS, such as to improve their responsiveness.
+
+With this feature, the following two HTML snippets now produce the same output:
+
+```html
+<svg width="100px" height="100px">
+   <defs>
+      <symbol id="sym" width="80" height="80">
+         <rect width="100" height="100" fill="green" />
+      </symbol>
+   </defs>
+   <use href="#sym" style="width:40px; height:40px" />
+</svg>
+```
+
+```html
+<svg width="100px" height="100px">
+   <defs>
+      <symbol id="sym" width="80" height="80">
+         <rect width="100" height="100" fill="green" />
+      </symbol>
+   </defs>
+   <use href="#sym" width="40" height="40" />
+</svg>
+```
+
+See also:
+* [`<use>`](https://developer.mozilla.org/docs/Web/SVG/Reference/Element/use) at MDN.
+
+
+<!-- ====================================================================== -->
+## Web APIs
+<!-- https://developer.mozilla.org/docs/Web/API/ -->
+
+Below are the new Web API features in Microsoft Edge.
+
+
+<!-- ------------------------------ -->
+#### Clear the `window.name` value for cross-site navigations that switch browsing context group
+
+Previously, the value of the `window.name` property was preserved throughout the lifetime of a browser tab, even when a cross-site navigation switched browsing context groups.
+
+The `window.name` property is now cleared when a cross-site navigation switches browsing context groups.
+
+See also:
+* [Window: name property](https://developer.mozilla.org/docs/Web/API/Window/name) at MDN.
+* [Browsing context](https://developer.mozilla.org/docs/Glossary/Browsing_context) at MDN.
+
+
+<!-- ------------------------------ -->
+#### `clipboardchange` event
+
+The Clipboard API now fires a `clipboardchange` event whenever the content of the system clipboard changes.
+
+The `clipboardchange` event provides an efficient alternative to polling techniques, such as using JavaScript to read the clipboard content at regular intervals of time.
+
+See also:
+* [Clipboard API](https://developer.mozilla.org/docs/Web/API/Clipboard_API) at MDN.
+
+
+<!-- ------------------------------ -->
+#### `dataTransfer` property for `insertFromPaste`, `insertFromDrop`, and `insertReplacementText` input events
+
+The input event objects of type `insertFromPaste`, `insertFromDrop`, and `insertReplacementText` now have a `dataTransfer` property, for better interoperability with other browsers.
+
+The `dataTransfer` property provides access to the clipboard or drag-and-drop data when the user edits text within a `contenteditable` element.  The same data is also available on the `dataTransfer` property of `beforeinput` events.
+
+This feature only applies to `contenteditable` elements.
+
+See also:
+* [DataTransfer](https://developer.mozilla.org/docs/Web/API/DataTransfer) at MDN.
+* [InputEvent: inputType property](https://developer.mozilla.org/docs/Web/API/InputEvent/inputType) at MDN.
+* [HTML contenteditable global attribute](https://developer.mozilla.org/docs/Web/HTML/Reference/Global_attributes/contenteditable) at MDN.
+* [Element: beforeinput event](https://developer.mozilla.org/docs/Web/API/Element/beforeinput_event) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Show third-party iframe origins in the FedCM UI
+
+Third-party iframe origins are now shown in the FedCM UI.  Showing the third-party iframe's origin to the user is important, to help users make an informed decision about sharing their credentials with the third-party origin.  The `client_is_third_party_to_top_frame_origin` Relying Party (RP) metadata property allows you to show the third-party origin in the FedCM iframe.
+
+Previously, when using iframes with FedCM, the FedCM UI always displayed the origin from the top-level site, even if it differed from the iframe's origin.  That works well when the iframe is conceptually part of the top-level site, even if its origin is different; for example, a top-level site at `example.com` might use a FedCM iframe at `example-static.com`, which it owns, but which is not meaningful to show to the user.  In other cases, FedCM iframes might belong to third-party sites.
+
+See also:
+* [Federated Credential Management (FedCM) API](https://developer.mozilla.org/docs/Web/API/FedCM_API) at MDN.
+
+
+<!-- ------------------------------ -->
+#### HSTS tracking prevention
+
+HSTS tracking prevention mitigates user tracking by third-parties via the HTTP Strict Transport Security (HSTS) cache.
+
+This feature only allows HSTS upgrades for top-level navigations, and blocks HSTS upgrades for sub-resource requests.  Blocking such an HSTS upgrade prevents third-party sites from using the HSTS cache to track a user across the web.
+
+See also:
+* [Strict-Transport-Security header](https://developer.mozilla.org/docs/Web/HTTP/Reference/Headers/Strict-Transport-Security) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Only fire `pointerrawupdate` events in secure contexts
+
+Microsoft Edge now matches the specification and other browsers by only firing `pointerrawupdate` in secure contexts.
+
+Previously, the `pointerrawupdate` event fired in both secure and insecure contexts, which didn't match the Pointer Events specification and other browsers.
+
+See also:
+* [Element: pointerrawupdate event](https://developer.mozilla.org/docs/Web/API/Element/pointerrawupdate_event) at MDN.
+* [The pointerrawupdate event](https://w3c.github.io/pointerevents/#the-pointerrawupdate-event) in _Pointer Events Level 4_.
+
+
+<!-- ------------------------------ -->
+#### Enable sticky user activation across same-origin navigations
+
+The sticky user activation state is now preserved after a the user navigates to a webpage that's on the same origin.
+
+This allows you to directly make use of web features that normally require user activation, such as those listed at [Features gated by user activation](https://developer.mozilla.org/docs/Web/Security/User_activation), even after the user has navigated to another webpage of your website.
+
+See also:
+* [Sticky activation](https://developer.mozilla.org/docs/Glossary/Sticky_activation) at MDN.
+
+
+<!-- ------------------------------ -->
+#### New PWA manifest update algorithm
+
+The updating of installed PWAs uses a new algorithm.  The new update algorithm makes the update process more deterministic and predictable, and gives you more control over whether, and when, updates should apply to existing installations of your app.
+
+The new update algorithm has the following benefits:
+
+* **Consistency:** The algorithm provides a consistent way to detect when a manifest update should happen.
+
+* **Reduced user interruptions:** App users won't see the update dialog, except when it's strictly necessary, such as to confirm security-sensitive changes.
+
+* **Browser flexibility:** Microsoft Edge can now allow known, trusted apps to update without displaying a notification, and can block updates for known bad apps.
+
+* **Developer control:** You have more control over when the update dialog is shown to users.
+
+* **Reduce network traffic:** Unnecessary network traffic is minimized.
+
+See also:
+* [Predictable Web App Updating - Explainer](https://github.com/WICG/manifest-incubations/blob/gh-pages/predictable-app-updating.md)
+
+
+<!-- ------------------------------ -->
+#### Web Speech API contextual biasing
+
+You can now provide a list of phrases to the Web Speech API for contextual biasing in speech recognition.  Listing recognition phrases provides the Web Speech API with an explicit mechanism to support contextual biasing.
+
+Previously, the Web Speech API used generalized speech recognition models, and couldn't prioritize certain words or phrases, or adapt to user-specific or domain-specific vocabularies.
+
+See also:
+* [phrases attribute](https://webaudio.github.io/web-speech-api/#dom-speechrecognition-phrases) in _Web Speech API_.
+* [Web Speech API](https://developer.mozilla.org/docs/Web/API/Web_Speech_API) at MDN.
+
+
+<!-- ====================================================================== -->
+## Origin trials in Microsoft Edge
+
+The following are origin trials for new experimental APIs that are available in Microsoft Edge.
+
+Origin trials let you try experimental APIs on your own live website for a limited time.
+
+To learn more about origin trials, see [Use origin trials in Microsoft Edge](../../origin-trials/index.md).
+
+To see the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
+
+
+<!-- ---------- -->
+#### AriaNotify API
+
+Expires on October 14, 2025.
+
+The AriaNotify API enables your app to directly tell a screen reader what to say when there's a non-user-initiated change in the content of a webpage.  In the simplest scenario, you call `ariaNotify("foo")` on the document or on an element.
+
+See [Creating a more accessible web with Aria Notify](https://blogs.windows.com/msedgedev/2025/05/05/creating-a-more-accessible-web-with-aria-notify/).
+
+* [Explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Accessibility/AriaNotify/explainer.md)
+* [Feedback](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?labels=AriaNotify,OriginTrialFeedback&title=%5BAriaNotify%5D+Feedback)
+* [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/a05622fb-4cd9-42f4-ac8d-1a2f62de139b)
+
+
+<!-- ---------- -->
+#### Ad Selection API
+
+Expires on November 30, 2025.
+
+The Ad Selection API provides user-relevant ads on your site without using third-party cookies.
+
+* [Explainer](https://github.com/WICG/privacy-preserving-ads/blob/main/Ad%20Selection%20Overview.md)
+* [Feedback](https://github.com/WICG/privacy-preserving-ads/issues/new?labels=Ad+Selection%20API,OriginTrialFeedback&amp;title=%5BAd%20Selection%20API%5D+Feedback)
+* [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/ffe94e9d-436d-46e6-9144-43abd7bf8c75)
+
+
+<!-- ---------- -->
+#### Acquisition Info API
+
+Expires on December 18, 2025.
+
+The Acquisition Info API supports third-party acquisition attribution for PWAs that were acquired through an app store or directly from the browser.
+
+* [Explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/AcquisitionInfo/explainer.md)
+* [Feedback](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?labels=Acquisition+Info,OriginTrialFeedback&amp;title=%5BAcquisition%20Info%5D+Feedback)
+* [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/4013a45f-3f48-4341-81ea-1bc13bf90c83)
+
+
+<!-- ====================================================================== -->
+## Chromium origin trials
+
+Below are active Chromium origin trials which you can try in Microsoft Edge.
+
+To see the full list of Chromium origin trials that are available in Microsoft Edge, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
+
+
+<!-- ---------- -->
+#### WebAssembly Custom Descriptors
+
+Expires on June 16, 2026.
+
+WebAssembly Custom Descriptors allows WebAssembly to store data associated with source-level types more efficiently in new custom descriptor objects.
+
+* [Explainer](https://github.com/WebAssembly/custom-descriptors/blob/main/proposals/custom-descriptors/Overview.md)
+* [Feedback](https://github.com/WebAssembly/custom-descriptors/issues)
+* [Register](https://developer.chrome.com/origintrials/#/register_trial/619807898716864513)
+
+
+<!-- ---------- -->
+#### WebGPU Compatibility Mode
+
+Expires on April 21, 2026
+
+WebGPU Compatibility Mode is an opt-in, lightly restricted subset of WebGPU capable of running older graphics APIs such as OpenGL and Direct3D11.  The goal is to expand the reach of WebGPU applications to older devices that don't have the modern, explicit graphics APIs that core WebGPU requires.
+
+* [Explainer](https://github.com/explainers-by-googlers/webgpu-compatibility-mode/blob/main/README.md)
+* [Feedback](https://github.com/gpuweb/gpuweb/issues)
+* [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/0b40bea0-e36c-4be0-8983-254a8004a4e3)
+
+
+<!-- ---------- -->
+#### Fetch retry
+
+Expires on March 24, 2026.
+
+Fetch retry allows web developers to indicate that a `fetch()` request should be retried, to have a greater guarantee on it being reliably sent, even if the network connection is erratic.  This is especially important for keep-alive fetches, where the request might outlive the document, which can no longer watch for its failure and do a manual retry.
+
+* [Explainer](https://github.com/explainers-by-googlers/fetch-retry/tree/main)
+* [Feedback](https://github.com/whatwg/fetch/issues/1838)
+* [Register](https://developer.chrome.com/origintrials/#/register_trial/2119506574631239681)
+
+
+<!-- ---------- -->
+#### Prompt API
+
+Expires on March 24, 2026
+
+The Prompt API is an experimental web API that allows you to prompt a small language model (SLM) that is built into Microsoft Edge, from your website's or browser extension's JavaScript code.  Use the Prompt API to generate and analyze text, or to create application logic based on user input, and discover innovative ways to integrate prompt engineering capabilities into your web application.
+
+* [Explainer](https://github.com/webmachinelearning/prompt-api/blob/main/README.md)
+* [Feedback](https://github.com/webmachinelearning/prompt-api/issues)
+* [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/b7d35247-b855-4b08-b237-89e7a5056117)
+
+See also:
+* [Prompt a built-in language model with the Prompt API](../prompt-api.md)
+
+
+<!-- ---------- -->
+#### Incoming Call Notifications
+
+Expires on May 19, 2026.
+
+Extend the Notifications API to allow installed PWAs to send incoming call notifications -- that is, notifications that have call-styled buttons and a ringtone.  This extension helps VoIP web apps create more engaging experiences by making it easier for users to easily recognize a calling notification and answer it.  This feature also helps bridge the gap between native and web implementations of apps that have them both.
+
+* [Explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/Notifications/notifications_actions_customization.md)
+* [Feedback](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues)
+* [Register](https://developer.chrome.com/origintrials/#/register_trial/2876111312029483009)
+
+See also:
+* [Request for feedback: Incoming call notifications API for web apps](https://blogs.windows.com/msedgedev/2025/02/04/request-for-feedback-incoming-call-notifications-api/)
+
+
+<!-- ---------- -->
+#### Full frame rate render blocking attribute
+
+Expires on March 24, 2026
+
+The new `full-frame-rate` render blocking attribute instructs the browser to render the page at a lower frame rate to reserve resources while parsing critical content.  After the critical content has been parsed, the browser restores its normal frame rate.
+
+For example `<link rel="expect" href="#critical-content" blocking="full-frame-rate">` lowers the frame rate of the browser until the `#critical-content` element is parsed.
+
+The `full-frame-rate` render blocking attribute is informational only.  The browser may decide to lower the frame rate before parsing a blocking element, such as at the very beginning of the loading phase.  The browser may also decide to restore the frame rate before the blocking element list becomes empty, such as after a timeout, or after certain user interactions.
+
+* [Explainer](https://github.com/whatwg/html/issues/11070)
+* [Feedback](https://github.com/whatwg/html/issues/11070)
+* [Register](https://developer.microsoft.com/microsoft-edge/origin-trials/trials/e43c41e4-b9d3-4128-a89f-a2e4d0de80f4)
+
+
+<!-- ====================================================================== -->
+> [!NOTE]
+> Portions of this page are modifications based on work created and shared by Chromium.org and used according to terms described in the [Creative Commons Attribution 4.0 International License](https://creativecommons.org/licenses/by/4.0).
diff --git a/scripts/beta-release-notes-template.njk b/scripts/beta-release-notes-template.njk
index cfc9f960fe..7d60d15f5c 100644
--- a/scripts/beta-release-notes-template.njk
+++ b/scripts/beta-release-notes-template.njk
@@ -18,27 +18,25 @@ To stay up-to-date and get the latest web platform features, download a preview
 
 * [Edge DevTools](#edge-devtools)
 * [WebView2](#webview2)
-* [Web platform features](#web-platform-features)
-  * [Enabled features](#enabled-features)
-    {% for feature in data.csFeatures["Enabled by default"] %}
-    * [{{ feature.name }}](#{{ feature.name | slugify }})
-    {% endfor %}
-  * [Deprecated and removed features](#deprecated-and-removed-features)
-    {% for feature in data.csFeatures["Deprecated"] %}
-    * [{{ feature.name }}](#{{ feature.name | slugify }})
-    {% endfor %}
-    {% for feature in data.csFeatures["Removed"] %}
-    * [{{ feature.name }}](#{{ feature.name | slugify }})
-    {% endfor %}
-* [Origin trials](#origin-trials)
-  * [New Chromium origin trials](#new-chromium-origin-trials)
-    {% for trial in data.chromeOTs %}
-    * [{{ trial.title }}](#{{ trial.title | slugify }})
-    {% endfor %}
-  * [Microsoft Edge-only origin trials](#microsoft-edge-only-origin-trials)
-    {% for trial in data.edgeOTs %}
-    * [{{ trial.title }}](#{{ trial.title | slugify }})
-    {% endfor %}
+* [CSS/SVG/Web API features](#csssvgweb-api-features)
+  {% for feature in data.csFeatures["Enabled by default"] %}
+  * [{{ feature.name }}](#{{ feature.name | slugify }})
+  {% endfor %}
+* [Deprecated or removed features](#deprecated-or-removed-features)
+  {% for feature in data.csFeatures["Deprecated"] %}
+  * [{{ feature.name }}](#{{ feature.name | slugify }})
+  {% endfor %}
+  {% for feature in data.csFeatures["Removed"] %}
+  * [{{ feature.name }}](#{{ feature.name | slugify }})
+  {% endfor %}
+* [Origin trials in Microsoft Edge](#origin-trials-in-microsoft-edge)
+  {% for trial in data.edgeOTs %}
+  * [{{ trial.title }}](#{{ trial.title | slugify }})
+  {% endfor %}
+* [Chromium origin trials](#chromium-origin-trials)
+  {% for trial in data.chromeOTs %}
+  * [{{ trial.title }}](#{{ trial.title | slugify }})
+  {% endfor %}
 
 
 <!-- ====================================================================== -->
@@ -60,15 +58,12 @@ For WebView2, see [1.0.n.n](../../webview2/release-notes/index.md#10nnnnnn) in _
 
 
 <!-- ====================================================================== -->
-## Web platform features
+## CSS/SVG/Web API features
 
-
-<!-- ------------------------------ -->
-#### Enabled features
 {% for feature in data.csFeatures["Enabled by default"] %}
 
-<!-- ---------- -->
-###### {{ feature.name }}
+<!-- ------------------------------ -->
+#### {{ feature.name }}
 
 {{ feature.summary | safe }}
 
@@ -77,42 +72,41 @@ See also:
 {% endfor %}
 
 <!-- ------------------------------ -->
-#### Deprecated and removed features
+#### Deprecated or removed features
 
 **TODO: CHECK THE FEATURES LISTED BELOW AND ADD THEM TO THE SITE-COMPAT-IMPACTING-CHANGES ARTICLE.**
 
 {% for feature in data.csFeatures["Deprecated"] %}
 
-<!-- ---------- -->
-###### {{ feature.name }}
+<!-- ------------------------------ -->
+#### {{ feature.name }}
 
 {{ feature.summary | safe }}
 {% endfor %}
 {% for feature in data.csFeatures["Removed"] %}
 
-<!-- ---------- -->
-###### {{ feature.name }}
+<!-- ------------------------------ -->
+#### {{ feature.name }}
 
 {{ feature.summary | safe }}
 {% endfor %}
 
 
 <!-- ====================================================================== -->
-## Origin trials
+## Origin trials in Microsoft Edge
 
-The following are new experimental APIs which you can try on your own live website for a limited time.
+The following are origin trials for new experimental APIs that are available in Microsoft Edge.
+
+Origin trials let you try experimental APIs on your own live website for a limited time.
 
 To learn more about origin trials, see [Use origin trials in Microsoft Edge](../../origin-trials/index.md).
 
 To see the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
 
+{% for trial in data.edgeOTs %}
 
 <!-- ------------------------------ -->
-#### New Chromium origin trials
-{% for trial in data.chromeOTs %}
-
-<!-- ---------- -->
-###### {{ trial.title }}
+#### {{ trial.title }}
 
 Expires on {{ trial.expiration }}.
 
@@ -121,15 +115,20 @@ Expires on {{ trial.expiration }}.
 * [Explainer]({{ trial.explainer }})
 * [Feedback]({{ trial.feedback }})
 * [Register]({{ trial.registration }})
+
 {% endfor %}
 
+<!-- ====================================================================== -->
+## Chromium origin trials
 
-<!-- ------------------------------ -->
-#### Microsoft Edge-only origin trials
-{% for trial in data.edgeOTs %}
+Below are active Chromium origin trials which you can try in Microsoft Edge.
 
-<!-- ---------- -->
-###### {{ trial.title }}
+To see the full list of Chromium origin trials that are available in Microsoft Edge, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
+
+{% for trial in data.chromeOTs %}
+
+<!-- ------------------------------ -->
+#### {{ trial.title }}
 
 Expires on {{ trial.expiration }}.
 
@@ -138,7 +137,6 @@ Expires on {{ trial.expiration }}.
 * [Explainer]({{ trial.explainer }})
 * [Feedback]({{ trial.feedback }})
 * [Register]({{ trial.registration }})
-
 {% endfor %}
 
 
diff --git a/scripts/web-platform-release-notes.js b/scripts/web-platform-release-notes.js
index af1a6f5eea..14d74ee0da 100644
--- a/scripts/web-platform-release-notes.js
+++ b/scripts/web-platform-release-notes.js
@@ -197,7 +197,11 @@ async function main() {
   const chromeOTs = chromeOTsData.origin_trials
     .filter((ot) => {
       // Only active origin trials that start in the next beta version.
-      return ot.status === "ACTIVE" && ot.start_milestone === nextBetaVersion;
+      return ot.status === "ACTIVE"
+        // Should start no later than the next beta version, otherwise it's not active.
+        && parseInt(ot.start_milestone, 10) <= parseInt(nextBetaVersion, 10)
+        // Should end at least one milestone after the next beta version, so that people have time to try it.
+        && parseInt(ot.end_milestone, 10) >= parseInt(nextBetaVersion, 10) + 1;
     })
     .map((ot) => {
       return {