diff --git a/microsoft-edge/toc.yml b/microsoft-edge/toc.yml
index 4e0f0d3f7a..4902a59d08 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 144
+          href: ./web-platform/release-notes/144.md
+          displayName: Microsoft Edge 144 web platform release notes (Jan. 2026)  # page title
+
         - name: Microsoft Edge 143
           href: ./web-platform/release-notes/143.md
           displayName: Microsoft Edge 143 web platform release notes (Dec. 2025)  # page title
@@ -66,13 +70,13 @@
           href: ./web-platform/release-notes/135.md
           displayName: Microsoft Edge 135 web platform release notes (Apr. 2025)  # page title
 
-        - name: Microsoft Edge 134
-          href: ./web-platform/release-notes/134.md
-          displayName: Microsoft Edge 134 web platform release notes (Mar. 2025)  # page title
-
         # keep 10 items above
         - name: Archive
           items:
+            - name: Microsoft Edge 134
+              href: ./web-platform/release-notes/134.md
+              displayName: Microsoft Edge 134 web platform release notes (Mar. 2025)  # page title
+
             - name: Microsoft Edge 133
               href: ./web-platform/release-notes/133.md
               displayName: Microsoft Edge 133 web platform release notes (Feb. 2025)  # page title
diff --git a/microsoft-edge/web-platform/release-notes/133.md b/microsoft-edge/web-platform/release-notes/133.md
index e13bbb28be..78ff280a99 100644
--- a/microsoft-edge/web-platform/release-notes/133.md
+++ b/microsoft-edge/web-platform/release-notes/133.md
@@ -307,7 +307,9 @@ This fixes a bug with speculation rules prefetch, where non-2xx responses were c
 <!-- ====================================================================== -->
 ## Origin trials
 
-The following are new experimental APIs which you can try 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/).
+The following are new experimental APIs which you can try 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).
+
+For the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
 
 
 <!-- ------------------------------ -->
diff --git a/microsoft-edge/web-platform/release-notes/134.md b/microsoft-edge/web-platform/release-notes/134.md
index b8f22f9a89..f47102fb86 100644
--- a/microsoft-edge/web-platform/release-notes/134.md
+++ b/microsoft-edge/web-platform/release-notes/134.md
@@ -204,7 +204,9 @@ This feature makes concurrent execution of shared storage worklets more reliable
 <!-- ====================================================================== -->
 ## Origin trials
 
-The following are new experimental APIs which you can try 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/).
+The following are new experimental APIs which you can try 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).
+
+For the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
 
 
 <!-- ------------------------------ -->
diff --git a/microsoft-edge/web-platform/release-notes/135.md b/microsoft-edge/web-platform/release-notes/135.md
index a8f44fdb3e..7898d72bcb 100644
--- a/microsoft-edge/web-platform/release-notes/135.md
+++ b/microsoft-edge/web-platform/release-notes/135.md
@@ -348,7 +348,7 @@ The following are new experimental APIs which you can try on your own live websi
 
 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 the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
 
 
 <!-- ------------------------------ -->
diff --git a/microsoft-edge/web-platform/release-notes/136.md b/microsoft-edge/web-platform/release-notes/136.md
index 0f39d7a804..186f90d2dd 100644
--- a/microsoft-edge/web-platform/release-notes/136.md
+++ b/microsoft-edge/web-platform/release-notes/136.md
@@ -330,7 +330,7 @@ The following are new experimental APIs that you can try on your own live websit
 
 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 the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
 
 
 <!-- ------------------------------ -->
diff --git a/microsoft-edge/web-platform/release-notes/137.md b/microsoft-edge/web-platform/release-notes/137.md
index 65a4c69e9d..2605d2979f 100644
--- a/microsoft-edge/web-platform/release-notes/137.md
+++ b/microsoft-edge/web-platform/release-notes/137.md
@@ -377,7 +377,7 @@ The following are new experimental APIs which you can try on your own live websi
 
 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 the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
 
 
 <!-- ------------------------------ -->
diff --git a/microsoft-edge/web-platform/release-notes/138.md b/microsoft-edge/web-platform/release-notes/138.md
index 5e8550d012..a39d558fb5 100644
--- a/microsoft-edge/web-platform/release-notes/138.md
+++ b/microsoft-edge/web-platform/release-notes/138.md
@@ -350,7 +350,7 @@ The following are new experimental APIs which you can try on your own live websi
 
 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 the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
 
 
 <!-- ------------------------------ -->
diff --git a/microsoft-edge/web-platform/release-notes/139.md b/microsoft-edge/web-platform/release-notes/139.md
index 2626098ed8..d960285eba 100644
--- a/microsoft-edge/web-platform/release-notes/139.md
+++ b/microsoft-edge/web-platform/release-notes/139.md
@@ -29,7 +29,6 @@ To stay up-to-date and get the latest web platform features, download a preview
     * [Specify a crash-reporting endpoint to receive only crash reports](#specify-a-crash-reporting-endpoint-to-receive-only-crash-reports)
     * [Fire error event instead of throwing for CSP blocked worker](#fire-error-event-instead-of-throwing-for-csp-blocked-worker)
     * [Reduce fingerprinting in `Accept-Language`](#reduce-fingerprinting-in-accept-language)
-    * [Browser Bound Keys in the Secure Payment Confirmation API](#browser-bound-keys-in-the-secure-payment-confirmation-api)
     * [Better JSON MIME type detection](#better-json-mime-type-detection)
     * [Support the async attribute for SVG `<script>` elements](#support-the-async-attribute-for-svg-script-elements)
     * [WebGPU `core-features-and-limits`](#webgpu-core-features-and-limits)
@@ -186,18 +185,6 @@ See also:
 * [Accept-Language header](https://developer.mozilla.org/docs/Web/HTTP/Reference/Headers/Accept-Language) at MDN.
 
 
-<!-- ---------- -->
-###### Browser Bound Keys in the Secure Payment Confirmation API
-
-The Secure Payment Confirmation API can now keep up with syncing passkeys and device requirements for online payments.  The Browser Bound Keys feature adds device binding in the browser, to enable payment scenarios in which device binding is required.
-
-This feature helps meet requirements for device binding for payment transactions.
-
-See also:
-* [Using Secure Payment Confirmation](https://developer.mozilla.org/docs/Web/API/Payment_Request_API/Using_secure_payment_confirmation) at MDN.
-* [Browser Bound Key Store](https://w3c.github.io/secure-payment-confirmation/#sctn-browser-bound-key-store) in _Secure Payment Confirmation_.
-
-
 <!-- ---------- -->
 ###### Better JSON MIME type detection
 
@@ -327,7 +314,7 @@ The following are new experimental APIs that you can try on your own live websit
 
 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 the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
 
 
 <!-- ------------------------------ -->
diff --git a/microsoft-edge/web-platform/release-notes/140.md b/microsoft-edge/web-platform/release-notes/140.md
index 6706d07366..263c8f2670 100644
--- a/microsoft-edge/web-platform/release-notes/140.md
+++ b/microsoft-edge/web-platform/release-notes/140.md
@@ -355,7 +355,7 @@ The following are new experimental APIs which you can try on your own live websi
 
 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 the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
 
 
 <!-- ------------------------------ -->
diff --git a/microsoft-edge/web-platform/release-notes/142.md b/microsoft-edge/web-platform/release-notes/142.md
index 60cdeacdb2..f723d15702 100644
--- a/microsoft-edge/web-platform/release-notes/142.md
+++ b/microsoft-edge/web-platform/release-notes/142.md
@@ -47,19 +47,13 @@ To stay up-to-date and get the latest web platform features, download a preview
 <!-- ====================================================================== -->
 ## Edge DevTools
 
-See [What's New in Microsoft Edge DevTools](../../devtools/whats-new/whats-new.md).
-<!-- todo: when it exists in Oct/Nov 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/Nov 2025, use instead:
-For WebView2, see [1.0.n.n](../../webview2/release-notes/index.md#10nnnnnn) (Oct./Nov. 2025) in _Release Notes for the WebView2 SDK_.
--->
+See [1.0.3595.46](../../webview2/release-notes/index.md#10359546) (Nov. 3, 2025) in _Release Notes for the WebView2 SDK_.
 
 
 <!-- ====================================================================== -->
@@ -273,11 +267,9 @@ See also:
 
 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.
+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 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 the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
 
 
 <!-- ---------- -->
@@ -323,7 +315,7 @@ The Acquisition Info API supports third-party acquisition attribution for PWAs t
 
 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/).
+For 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/).
 
 
 <!-- ---------- -->
diff --git a/microsoft-edge/web-platform/release-notes/143.md b/microsoft-edge/web-platform/release-notes/143.md
index cb06cf3943..bd97dc5151 100644
--- a/microsoft-edge/web-platform/release-notes/143.md
+++ b/microsoft-edge/web-platform/release-notes/143.md
@@ -56,7 +56,7 @@ To stay up-to-date and get the latest web platform features, download a preview
 ## Edge DevTools
 
 See [What's New in Microsoft Edge DevTools](../../devtools/whats-new/whats-new.md).
-<!-- todo: when it exists in Dec 2025, use instead:
+<!-- todo: when exists, change to:
 See [What's New in DevTools (Microsoft Edge 143)](../../devtools/whats-new/2025/12/devtools-143.md).
 -->
 
@@ -65,8 +65,8 @@ See [What's New in DevTools (Microsoft Edge 143)](../../devtools/whats-new/2025/
 ## WebView2
 
 See [Release Notes for the WebView2 SDK](../../webview2/release-notes/index.md).
-<!-- todo: when exists in Dec 2025, use instead:
-For WebView2, see [1.0.n.n](../../webview2/release-notes/index.md#10nnnnnn) in _Release Notes for the WebView2 SDK_ (Dec 2025).
+<!-- todo: when wv2 relnotes for runtime 143 exists, change to:
+See [1.0.n.n](../../webview2/release-notes/index.md#10nnnnnn) (Dec. nn, 2025) in _Release Notes for the WebView2 SDK_.
 -->
 
 
@@ -312,11 +312,9 @@ See also:
 
 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.
+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 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 the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
 
 <!-- headings below match ot name per register link -->
 
@@ -350,7 +348,7 @@ The Acquisition Info API supports third-party acquisition attribution for PWAs t
 
 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/).
+For 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/).
 
 
 <!-- ------------------------------ -->
diff --git a/microsoft-edge/web-platform/release-notes/144.md b/microsoft-edge/web-platform/release-notes/144.md
new file mode 100644
index 0000000000..2367bc28d8
--- /dev/null
+++ b/microsoft-edge/web-platform/release-notes/144.md
@@ -0,0 +1,539 @@
+---
+title: Microsoft Edge 144 web platform release notes (Jan. 2026)
+description: Microsoft Edge 144 web platform release notes (Jan. 2026)
+author: MSEdgeTeam
+ms.author: msedgedevrel
+ms.topic: conceptual
+ms.service: microsoft-edge
+ms.date: 11/24/2025
+---
+# Microsoft Edge 144 web platform release notes (Jan. 2026)
+
+The following are the new web platform features and updates in Microsoft Edge 144, which releases on January 15, 2026.
+
+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)
+  * [The `scrolled` feature for scroll-state container queries](#the-scrolled-feature-for-scroll-state-container-queries)
+  * [CSS transform support in anchor positioning](#css-transform-support-in-anchor-positioning)
+  * [Support for overscroll-behavior on keyboard scrolling and on non-scrollable containers](#support-for-overscroll-behavior-on-keyboard-scrolling-and-on-non-scrollable-containers)
+  * [Scroll-triggered animations](#scroll-triggered-animations)
+  * [Styling SVG elements instantiated via `<use>`](#styling-svg-elements-instantiated-via-use)
+  * [View Transitions waitUntil() method](#view-transitions-waituntil-method)
+* [Web APIs](#web-apis)
+  * [The Temporal API](#the-temporal-api)
+  * [The clipboardchange event](#the-clipboardchange-event)
+  * [IDNA ContextJ rules](#idna-contextj-rules)
+  * [The variants accessor property of Intl.Locale](#the-variants-accessor-property-of-intllocale)
+  * [Mirroring of MathML operators in right-to-left mode](#mirroring-of-mathml-operators-in-right-to-left-mode)
+  * [Performance API interactionCount property](#performance-api-interactioncount-property)
+  * [The `maintain-framerate-and-resolution` value for the `RTCDegradationPreference` enum](#the-maintain-framerate-and-resolution-value-for-the-rtcdegradationpreference-enum)
+  * [LayoutShift API reports rect elements in CSS pixels](#layoutshift-api-reports-rect-elements-in-css-pixels)
+  * [Browser Bound Keys in the Secure Payment Confirmation API](#browser-bound-keys-in-the-secure-payment-confirmation-api)
+  * [Support for `ping`, `hreflang`, `type`, and `referrerPolicy` for SVG `<a>` elements](#support-for-ping-hreflang-type-and-referrerpolicy-for-svg-a-elements)
+  * [Exception on History API pushState and replaceState throttling](#exception-on-history-api-pushstate-and-replacestate-throttling)
+  * [User-Agent Client Hints ch-ua-high-entropy-values permissions policy](#user-agent-client-hints-ch-ua-high-entropy-values-permissions-policy)
+  * [WebGPU: Uniform buffer standard layout](#webgpu-uniform-buffer-standard-layout)
+  * [WebGPU: subgroup_id feature](#webgpu-subgroup_id-feature)
+  * [WebXR XRVisibilityMaskChange event](#webxr-xrvisibilitymaskchange-event)
+* [Deprecated or removed features](#deprecated-or-removed-features)
+  * [Externally loaded entities in XML parsing](#externally-loaded-entities-in-xml-parsing)
+* [Origin trials in Microsoft Edge](#origin-trials-in-microsoft-edge)
+  * [Web Install API](#web-install-api)
+  * [Acquisition Info API](#acquisition-info-api)
+* [Chromium origin trials](#chromium-origin-trials)
+  * [Incoming call notifications](#incoming-call-notifications)
+  * [Writer API](#writer-api)
+  * [Rewriter API](#rewriter-api)
+  * [WebAssembly Custom Descriptors](#webassembly-custom-descriptors)
+  * [CrashReportingStorageAPI](#crashreportingstorageapi)
+  * [WebGPU Compatibility Mode](#webgpu-compatibility-mode)
+  * [Extended lifetime shared workers](#extended-lifetime-shared-workers)
+  * [Local Network Access from Non-Secure Contexts](#local-network-access-from-non-secure-contexts)
+
+
+<!-- ====================================================================== -->
+## Edge DevTools
+
+See [What's New in Microsoft Edge DevTools](../../devtools/whats-new/whats-new.md).
+<!-- todo: when it exists in Jan 2026, use instead:
+See [What's New in DevTools (Microsoft Edge 144)](../../devtools/whats-new/2026/01/devtools-144.md).
+-->
+
+
+<!-- ====================================================================== -->
+## WebView2
+
+See [Release Notes for the WebView2 SDK](../../webview2/release-notes/index.md).
+<!-- todo: when exists in Jan 2026, use instead:
+For WebView2, see [1.0.n.n](../../webview2/release-notes/index.md#10nnnnnn) in _Release Notes for the WebView2 SDK_ (Jan 2026).
+-->
+
+
+<!-- ====================================================================== -->
+## CSS features
+
+
+<!-- ------------------------------ -->
+#### The `scrolled` feature for scroll-state container queries
+
+The `scrolled` feature for a `@container sroll-state()` query makes it possible to style elements within a scrollable containers based on the container's most recent scrolling direction.
+
+For example:
+
+```css
+.scrolling-up {
+  translate: 80px 0;
+  transition: 0.4s translate;
+}
+
+html {
+  container-type: scroll-state;
+}
+
+@container scroll-state(scrolled: top) {
+  .scrolling-up {
+    translate: 0 0;
+  }
+}
+```
+
+The `scrolled` feature can be used to implement UI patterns such as a header that automatically hides as the user scrolls down the page and reappears as they scroll up.  The `scrolled` feature provides a CSS-only solution for these common UI patterns.
+
+See also:
+* [CSS scroll state container queries](./133.md#css-scroll-state-container-queries) in _Microsoft Edge 133 web platform release notes (Feb. 2025)_.
+* [Scrolled: the scrolled feature](https://drafts.csswg.org/css-conditional-5/#scrolled) in _CSS Conditional Rules Module Level 5_.
+
+
+<!-- ------------------------------ -->
+#### CSS `transform` support in anchor positioning
+
+When an anchor-positioned element is tethered to an element that's transformed, such as by using the CSS `transform` property, the anchor-positioned element is now correctly positioned relative to the bounding box of the transformed anchor.
+
+This makes it possible to create UI effects where elements remain logically connected, even if one of the elements is being transformed.
+
+See also:
+* [CSS anchor positioning](https://developer.mozilla.org/docs/Web/CSS/Guides/Anchor_positioning) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Support for `overscroll-behavior` on keyboard scrolling and on non-scrollable containers
+
+When you set the CSS `overscroll-behavior` property to a value other than `auto`, scroll chaining is prevented by the browser.  This means that when a user scrolls to the end of a scroll container, the scroll doesn't propagate to ancestor scroll containers.
+
+In earlier versions of Microsoft Edge, this only worked for mouse or touch scrolling.  This change makes keyboard scrolling respect `overscroll-behavior` as well.
+
+Additionally, `overscroll-behavior` now applies to all scroll container elements, regardless of whether those elements currently have overflowing content or are user-scrollable.  For example, you can now use `overscroll-behavior` to prevent scroll propagation on an `overflow: hidden` backdrop, or on an `overflow: auto` element, without needing to consider whether the element itself is overflowing.
+
+See also:
+* [overscroll-behavior](https://developer.mozilla.org/docs/Web/CSS/Reference/Properties/overscroll-behavior) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Scroll-triggered animations
+
+The `timeline-trigger` property can now trigger CSS animations based on a scroll position, and can control the playback of those animations as the user scrolls.
+
+This feature is useful to implement common patterns where animations only start when a scroll position on the page has been reached.  Previously, developers often did this by using JavaScript to detect that an element is within its scroll container's viewport.  Using the CSS `timeline-trigger` property to trigger animations based on a scroll position instead can improve performance and reliability.
+
+See also:
+* [Timeline Triggers](https://drafts.csswg.org/css-animations-2/#timeline-triggers) in _CSS Animations Module Level 2_.
+* [Scroll-triggered animation demos](https://davmila.github.io/sta-demos/explore/).
+
+
+<!-- ------------------------------ -->
+#### Styling SVG elements instantiated via `<use>`
+
+CSS rules that match SVG elements that are embedded into a document via the `<use>` SVG element now correctly match against the embedded elements.
+
+Previously, the CSS rules matched the originating SVG elements instead of the elements instantiated via `<use>`.
+
+See also:
+* [`<use>`](https://developer.mozilla.org/docs/Web/SVG/Reference/Element/use) at MDN.
+
+
+<!-- ------------------------------ -->
+#### View Transitions `waitUntil()` method
+
+The `ViewTransition.waitUntil()` function enables more advanced uses of the View Transitions API.  The function accepts a Promise, which is used to delay the destruction of the pseudo-tree that's used to render and animate the view transition.
+
+The View Transitions API automatically constructs this pseudo-element subtree to display and animate the elements that participate in a transition.
+
+Normally:
+* This subtree is constructed when the view transition starts animating.
+* This subtree is destroyed when the animations that are associated with all view transition pseudo-elements are in the finished state.
+
+That normal behavior works for the vast majority of cases.  In some cases, however, you might want the view transition pseudo-tree to persist beyond the animation finish state.  For example, if you tie a view transition with a scroll-driven animation, we don't want the subtree to be destroyed when the animations finish, because scrolling back should animate the pseudo-elements again.
+
+See also:
+* [View Transition API](https://developer.mozilla.org/docs/Web/API/View_Transition_API) at MDN.
+* [CSS scroll-driven animations](https://developer.mozilla.org/docs/Web/CSS/Guides/Scroll-driven_animations) at MDN.
+
+
+<!-- ====================================================================== -->
+## Web APIs
+
+
+<!-- ------------------------------ -->
+#### The Temporal API
+
+The Temporal API allows you to work with dates, times, time zones, and durations, and is more powerful than the Date API.
+
+See also:
+* [Temporal](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Temporal) at MDN.
+
+
+<!-- ------------------------------ -->
+#### The `clipboardchange` event
+
+The `clipboardchange` event of the `navigator.clipboard` API fires when the user modifies the contents of the clipboard from a web app, or from any other system application.
+
+The `clipboardchange` event allows you to react to clipboard changes, without having to read the clipboard contents at regular intervals of time (sometimes called _clipboard polling_).
+
+See also:
+* [Test the clipboardchange event—a more efficient way to monitor the clipboard](https://developer.chrome.com/blog/clipboardchange).
+
+
+<!-- ------------------------------ -->
+#### IDNA ContextJ rules
+
+To improve interoperability with other browsers, Microsoft Edge now implements the IDNA ContextJ rules, by disallowing ZWNJ (U+200C ZERO WIDTH NON-JOINER) and ZWJ (U+200D ZERO WIDTH JOINER) characters in most places within URLs.
+
+IDNA is the mechanism by which non-ASCII characters can occur in domain names.  For example, the URL `http://네이버.한국/` is encoded as `http://xn--950bt9s8xi.xn--3e0b707e/`.
+
+See also:
+* [Better Unicode support](./143.md#better-unicode-support) in _Microsoft Edge 143 web platform release notes (Dec. 2025)_.
+
+
+<!-- ------------------------------ -->
+#### The `variants` accessor property of `Intl.Locale`
+
+The `variants` accessor property of a `Intl.Locale` instance returns the language tag variants that are associated with this locale, as a string of identifiers separated by dash (hyphen) characters (`-`).
+
+For example, the 1901 German orthography variant is represented by the `de-1901` language tag, and can be accessed as follows:
+
+```js
+const locale = new Intl.Locale('de-1901');
+console.log(locale.variants); // "1901"
+```
+
+See also:
+* [Intl.Locale.prototype.variants](https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/variants) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Mirroring of MathML operators in right-to-left mode
+
+When rendering MathML operators in right-to-left mode, characters and glyphs can now be mirrored by changing them to another code point.
+
+For characters, the mirroring is defined by the Unicode's `Bidi_Mirrored` property.  For example, a right (closing) parenthesis becomes a left (opening) parenthesis.
+
+Some operators have no appropriate mirrored character.  In this situation, glyph-level mirroring applies instead.  By using the `rtlm` font feature, a glyph can be replaced by another glyph.
+
+See also:
+* [MathML](https://developer.mozilla.org/docs/Web/MathML) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Performance API `interactionCount` property
+
+The new `performance.interactionCount` property returns the total number of interactions that have occurred on the page.
+
+This feature is useful for computing the **Interaction to Next Paint (INP)** metric value, which requires knowing the total number of interactions, in order to compute a high percentile score.
+
+The `performance.interactionCount` property complements the Event Timing API, which is used to measure the performance of user interactions.  Some events that are returned by the Event Timing API have an `interactionId` value assigned to them, which is useful for grouping related interactions based on common physical user inputs or gestures.
+
+See also:
+* [Extensions to the Performance interface](https://www.w3.org/TR/event-timing/#sec-extensions).
+* [Performance](https://developer.mozilla.org/docs/Web/API/Performance) at MDN.
+
+
+<!-- ------------------------------ -->
+#### The `maintain-framerate-and-resolution` value for the `RTCDegradationPreference` enum
+
+The `maintain-framerate-and-resolution` value for the `RTCDegradationPreference` enum allows an application to disable WebRTC's internal video adaptation mechanism, for cases where the application implements its own external video adaptation logic.
+
+WebRTC has an internal video adaptation mechanism that optimizes video quality and performance by adjusting encoding settings.  This mechanism relies on hardcoded logic and thresholds, which might not yield optimal results across diverse use-cases.
+
+The `maintain-framerate-and-resolution` value for the `RTCDegradationPreference` enum disables WebRTC's internal video adaptation.
+
+See also:
+* [WebRTC API](https://developer.mozilla.org/docs/Web/API/WebRTC_API) at MDN.
+
+
+<!-- ------------------------------ -->
+#### LayoutShift API reports rect elements in CSS pixels
+
+The LayoutShift API now reports information about the elements which have shifted, such as `previousRect` and `currentRect`, in CSS pixels rather than physical pixels.
+
+This makes the API consistent with other layout-related web APIs, which all use CSS pixels.
+
+See also:
+* [LayoutShift](https://developer.mozilla.org/docs/Web/API/LayoutShift) at MDN.
+* [LayoutShiftAttribution](https://developer.mozilla.org/docs/Web/API/LayoutShiftAttribution) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Browser Bound Keys in the Secure Payment Confirmation API
+
+The Secure Payment Confirmation API can now keep up with syncing passkeys and device requirements for online payments.  The Browser Bound Keys feature adds device binding in the browser, to enable payment scenarios in which device binding is required.
+
+This feature helps meet requirements for device binding for payment transactions.
+
+See also:
+* [Using Secure Payment Confirmation](https://developer.mozilla.org/docs/Web/API/Payment_Request_API/Using_secure_payment_confirmation) at MDN.
+* [Browser Bound Key Store](https://w3c.github.io/secure-payment-confirmation/#sctn-browser-bound-key-store) in _Secure Payment Confirmation_.
+
+
+<!-- ------------------------------ -->
+#### Support for `ping`, `hreflang`, `type`, and `referrerPolicy` for SVG `<a>` elements
+
+The `ping`, `hreflang`, `type`, and `referrerPolicy` attributes are now supported on SVG `<a>` elements.
+
+This makes the SVG `<a>` element more consistent with the HTML `<a>` element.
+
+See also:
+* [Support `download` attribute in SVG `<a>` element](./142.md#support-download-attribute-in-svg-a-element) in _Microsoft Edge 142 web platform release notes (Oct. 2025)_.
+* [`<a>`](https://developer.mozilla.org/docs/Web/HTML/Reference/Elements/a#download) at MDN.
+
+
+<!-- ------------------------------ -->
+#### Exception on History API `pushState` and `replaceState` throttling
+
+A `SecurityError` exception is now thrown when excessive use of the History API's `pushState` and `replaceState` methods is detected, such as when these methods are called hundreds of times per second.
+
+Previously, the calls were ignored, and no errors were thrown.
+
+See also:
+* [History](https://developer.mozilla.org/docs/Web/API/History) at MDN.
+
+
+<!-- ------------------------------ -->
+#### User-Agent Client Hints `ch-ua-high-entropy-values` permissions policy
+
+The `ch-ua-high-entropy-values` permissions policy allows a first-party site to have more control over which third-parties are allowed to request high-entropy User-Agent Client Hints via the `navigator.userAgentData.getHighEntropyValues()` API.
+
+Previously, it was only possible to restrict third-party collection of high-entropy User-Agent Client Hints when they're requested over HTTP.
+
+See also:
+* [User-Agent Client Hints API](https://developer.mozilla.org/docs/Web/API/User-Agent_Client_Hints_API) at MDN.
+* [NavigatorUAData: getHighEntropyValues() method](https://developer.mozilla.org/docs/Web/API/NavigatorUAData/getHighEntropyValues) at MDN.
+
+
+<!-- ------------------------------ -->
+#### WebGPU: Uniform buffer standard layout
+
+Uniform buffers that are declared in WGSL shaders are no longer required to have 16-byte alignment on array elements, or to pad nested structure offsets to a multiple of 16 bytes.
+
+See also:
+* [WebGPU API](https://developer.mozilla.org/docs/Web/API/WebGPU_API) at MDN.
+
+
+<!-- ------------------------------ -->
+#### WebGPU: `subgroup_id` feature
+
+The `subgroup_id` and `num_subgroups` built-in values are now available when the subgroups extension is enabled.
+
+See also:
+* [WebGPU Subgroups](./134.md#webgpu-subgroups) in _Microsoft Edge 134 web platform release notes (Mar. 2025)_.
+* [WebGPU API](https://developer.mozilla.org/docs/Web/API/WebGPU_API) at MDN.
+
+
+<!-- ------------------------------ -->
+#### WebXR `XRVisibilityMaskChange` event
+
+The `XRVisibilityMaskChange` event provides a list of vertices and a list of indices to represent the mesh of the visible portion of the user's viewport.
+
+This data can be used to confidently limit how much of the viewport is drawn, to improve performance.
+
+See also:
+* [WebXR Device API](https://developer.mozilla.org/docs/Web/API/WebXR_Device_API) at MDN.
+
+
+<!-- ====================================================================== -->
+## Deprecated or removed features
+
+
+<!-- ------------------------------ -->
+#### Externally loaded entities in XML parsing
+
+Synchronous fetching of external XML entities/DTDs, which are then used when parsing under specific circumstances, has been removed.
+
+This improves the security of XML parsing in Microsoft Edge.  Usage of this feature was very low, and other browsers don't support this feature.
+
+
+<!-- ====================================================================== -->
+## 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).
+
+For the full list of available origin trials, see [Microsoft Edge Origin Trials](https://developer.microsoft.com/microsoft-edge/origin-trials/).
+
+
+<!-- ------------------------------ -->
+#### Web Install API
+
+Expires on July 14, 2026.
+
+The Web Install API allows websites to install other websites as web apps on the user's device, by using `navigator.install()`.
+
+* [Explainer](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/WebInstall/explainer.md)
+* [Feedback](https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/new?template=web-install-api.md)
+* [Register](https://developer.microsoft.com/en-us/microsoft-edge/origin-trials/trials/bcf7d28f-6bdf-45d8-9207-63c97a042407)
+
+
+<!-- ------------------------------ -->
+#### Acquisition Info API
+
+Expires on December 18, 2025.
+
+The Acquisition Info API supports 3P acquisition attribution for PWAs that are 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/en-us/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.
+
+For 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/).
+
+
+<!-- ------------------------------ -->
+#### Incoming call notifications
+
+Expires on May 19, 2026.
+
+This feature extends the Notifications API to allow installed PWAs to send incoming call notifications.
+
+Incoming call notifications have call-styled buttons and a ringtone.
+
+This extension helps Voice over IP web apps create more engaging experiences by making it easier for users to easily recognize a call notification and answer it.
+
+* [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)
+
+
+<!-- ------------------------------ -->
+#### Writer API
+
+Expires on April 21, 2026.
+
+The Writer API can be used to write text given a writing task prompt, backed by an on-device AI language model.
+
+Use this API to:
+* Generate a textual explanation of structured data.
+* Compose a post about a product, based on reviews or a product description.
+* Generate a biography based on background information.
+* And more.
+
+See also [Summarize, write, and rewrite text with the Writing Assistance APIs](../writing-assistance-apis.md).
+
+* [Explainer](https://github.com/webmachinelearning/writing-assistance-apis/blob/main/README.md#writer-api)
+* [Feedback](https://github.com/webmachinelearning/writing-assistance-apis/issues)
+* [Register](https://developer.chrome.com/origintrials/#/register_trial/-8779204523605360639)
+
+
+<!-- ------------------------------ -->
+#### Rewriter API
+
+Expires on April 21, 2026.
+
+The Rewriter API transforms and rephrases input text in requested ways, backed by an on-device AI language model.
+
+Use this API to remove redundancies within a text, in order to:
+* Fit the text into a word limit.
+* Rephrase messages to suit the intended audience.
+* Be more constructive if a message is found to use inadequate language.
+
+See also [Summarize, write, and rewrite text with the Writing Assistance APIs](../writing-assistance-apis.md).
+
+* [Explainer](https://github.com/webmachinelearning/writing-assistance-apis/blob/main/README.md#rewriter-api)
+* [Feedback](https://github.com/webmachinelearning/writing-assistance-apis/issues)
+* [Register](https://developer.chrome.com/origintrials/#/register_trial/444167513249415169)
+
+
+<!-- ---------- -->
+#### WebAssembly Custom Descriptors
+
+Expires on June 16, 2026.
+
+WebAssembly Custom Descriptors allows WebAssembly to store data that's 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)
+
+
+<!-- ------------------------------ -->
+#### CrashReportingStorageAPI
+
+Expires on April 21, 2026.
+
+The CrashReportingStorageAPI origin trial exposes the `window.crashReport` key-value Storage API, which allows you to supply arbitrary application state with each crash report that's sent to your specified endpoints.
+
+For the general crash reporting API infrastructure, see [Crash Reporting](https://wicg.github.io/crash-reporting/).
+
+For the design and specification of the `window.crashReport` extension, see [Introduce the CrashReportStorage interface](https://github.com/WICG/crash-reporting/pull/37) (an Explainer pull request).
+
+See
+* [Explainer](https://github.com/WICG/crash-reporting/blob/gh-pages/crashReport-explainer.md)
+* [Feedback](https://github.com/WICG/crash-reporting/issues)
+* [Register](https://developer.chrome.com/origintrials/#/register_trial/1304355042077179905)
+
+
+<!-- ---------- -->
+#### WebGPU Compatibility Mode
+
+Expires on April 21, 2026
+
+WebGPU Compatibility Mode is an opt-in, lightly restricted subset of WebGPU that's capable of running older graphics APIs, such as OpenGL and Direct3D11.  WebGPU Compatibility Mode expands 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)
+
+
+<!-- ------------------------------ -->
+#### Extended lifetime shared workers
+
+Expires on April 21, 2026.
+
+Extended-lifetime shared workers introduces the `extendedLifetime` option for the `SharedWorker` constructor.
+
+This feature allows a shared worker to stay alive for a short period after all connected clients (such as pages) have been unloaded.  This is useful for performing asynchronous tasks that need to complete after a page unloads, such as saving data to IndexedDB, or sending analytics.
+
+Without this feature, those tasks require a Service Worker, which can be too heavyweight for this use-case.  This origin trial provides a lightweight alternative.
+
+* [Explainer](https://gist.github.com/domenic/c5bd38339f33b49120ae11b3b4af5b9b#file-1-explainer-md)
+* [Feedback](https://github.com/whatwg/html/issues/10997)
+* [Register](https://developer.chrome.com/origintrials/#/register_trial/3056255297124302849)
+
+
+<!-- ------------------------------ -->
+#### Local Network Access from Non-Secure Contexts
+
+Expires on May 19, 2026.
+
+Local Network Access from non-secure contexts temporarily allows for access to resources on local networks to originate from non-secure contexts.  This gives you more time to migrate Local Network Access requests so that they originate from a secure context.
+
+For restrictions on Local Network Access, see [New permission prompt for Local Network Access](https://developer.chrome.com/blog/local-network-access).  This origin trial can only be enabled through HTTP header-provided origin tokens.
+
+* [Explainer](https://developer.chrome.com/blog/local-network-access)
+* [Feedback](https://github.com/WICG/local-network-access)
+* [Register](https://developer.chrome.com/origintrials/#/register_trial/3826370833404657665)
+
+
+<!-- ====================================================================== -->
+> [!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/microsoft-edge/web-platform/site-impacting-changes.md b/microsoft-edge/web-platform/site-impacting-changes.md
index 38b8c7cb8f..ae60663468 100644
--- a/microsoft-edge/web-platform/site-impacting-changes.md
+++ b/microsoft-edge/web-platform/site-impacting-changes.md
@@ -36,7 +36,8 @@ This table lists high-impact changes which the Microsoft Edge team is tracking c
 | --- | --- | --- |
 | Insecure downloads over HTTP | Future release (TBD) | When a user tries to download potentially dangerous content from an HTTP site, the user will receive a UI warning, such as "Insecure download blocked."  The user will still have an option to proceed and download the item.  Admins can use the `InsecureContentAllowedForUrls` policy to specify HTTP sites for which the warning will be suppressed.  Admins can use the `InsecureDownloadWarnings` feature flag to test the impact of this upcoming feature. |
 | Deprecate unload event | Future release (TBD) | Introduces a new Permission-Policy to allow creating unload event listeners. The default policy is `allow`, but the default policy will gradually be migrated to `deny`, such that unload handlers stop firing on pages, unless a page explicitly opts in to re-enable them.  This change is happening in the Chromium project, on which Microsoft Edge is based.  For more information, see [Intent to Deprecate: Deprecate unload event](https://groups.google.com/a/chromium.org/g/blink-dev/c/dvusqw9-IhI/m/SBkm_u1RAQAJ). |
-| Deprecate `Intl.Locale` getters | v143 | The accessor properties of the `Intl.Locale` object are now deprecated, in favor of the corresponding functions, per specification. See [Deprecate `Intl.Locale` getters](./release-notes/143.md#deprecate-intllocale-getters), in _Microsoft Edge 143 web platform release notes (Dec 2025)_. |
+| Externally loaded entities in XML parsing | v144 | Synchronous fetching of external XML entities/DTDs, which are then used when parsing under specific circumstances, has been removed. See [Externally loaded entities in XML parsing](./release-notes/144.md#externally-loaded-entities-in-xml-parsing), in _Microsoft Edge 144 web platform release notes (Jan. 2025)_. |
+| Deprecate `Intl.Locale` getters | v143 | The accessor properties of the `Intl.Locale` object are now deprecated, in favor of the corresponding functions, per specification. See [Deprecate `Intl.Locale` getters](./release-notes/143.md#deprecate-intllocale-getters), in _Microsoft Edge 143 web platform release notes (Dec. 2025)_. |
 | Remove special font size rules for `<h1>` | v140 | The special margin and font size rules for `<h1>` elements, when nested in `<article>`, `<aside>`, `<nav>`, and `<section>` elements, are now removed, to improve accessibility. See [Removed special font size rules for `<h1>` within some elements](./release-notes/140.md#removed-special-font-size-rules-for-h1-within-some-elements) in _Microsoft Edge 140 web platform release notes (Sep. 2025)_. |
 | Asynchronous range removal for Media Source Extensions throws exceptions | v138 | The following changes have been made to the Media Source Extensions specification, to disallow ambiguously defined behavior involving asynchronous range removals:  <br/>* `SourceBuffer.abort()` no longer aborts `SourceBuffer.remove()` operations.  <br/>* Setting `MediaSource.duration` can no longer truncate currently buffered media.  <br/>While these changes were made a long time ago, and Safari and Firefox have already implemented them, Chromium had not yet done so.  Exceptions are now thrown in both cases.  See [Media Source API](https://developer.mozilla.org/docs/Web/API/Media_Source_Extensions_API) at MDN. |
 | Removal of automatic SwiftShader fallback | v138 | Previously, if a WebGL context could not be created with the available GPU, Chromium would automatically fall back to using the SwiftShader software renderer.  This automatic fallback behavior is now removed and the WebGL context creation will now fail instead of falling back to SwiftShader.  SwiftShader poses security risks and leads to a poor user experience when falling back from a high-performance GPU-backed WebGL to a CPU-backed implementation.  SwiftShader remains a useful tool for doing headless testing on a site.  This use case is still supported by opting in, which you can do by running Microsoft Edge with the `--enable-unsafe-swiftshader` command-line argument.  See [Using Chromium with SwiftShader](https://chromium.googlesource.com/chromium/src/+/main/docs/gpu/swiftshader.md). |
diff --git a/scripts/beta-release-notes-template.njk b/scripts/beta-release-notes-template.njk
index 7d60d15f5c..bb2331c9fe 100644
--- a/scripts/beta-release-notes-template.njk
+++ b/scripts/beta-release-notes-template.njk
@@ -53,7 +53,7 @@ See [What's New in DevTools (Microsoft Edge {{ data.nextBetaVersion }})](../../d
 
 See [Release Notes for the WebView2 SDK](../../webview2/release-notes/index.md).
 <!-- todo: when exists in {% monthYear data.nextBetaReleaseDate %}, use instead:
-For WebView2, see [1.0.n.n](../../webview2/release-notes/index.md#10nnnnnn) in _Release Notes for the WebView2 SDK_ ({% monthYear data.nextBetaReleaseDate %}).
+See [1.0.n.n](../../webview2/release-notes/index.md#10nnnnnn) ({% monthYear data.nextBetaReleaseDate %}) in _Release Notes for the WebView2 SDK_.
 -->
 
 
@@ -97,11 +97,9 @@ See also:
 
 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.
+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 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 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 %}
 
@@ -123,7 +121,7 @@ Expires on {{ trial.expiration }}.
 
 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/).
+For 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 %}