has been

Author: mikehoffms

microsoft-edge/dev-videos/index.md

@@ -625,7 +625,7 @@ December 9, 2021
 
 [![Thumbnail image for video "Debug memory leaks with the Microsoft Edge Detached Elements tool"](./index-images/detached-elements.png)](https://www.youtube.com/watch?v=v2iy17ptmBk)
 
-March 7, 2025: The **Detached Elements** tool is about to be removed.  To debug DOM memory leaks, use the **Detached elements** profiling type in the **Memory** tool.
+March 2025 update: The **Detached Elements** tool has been removed.  To debug DOM memory leaks, use the **Detached elements** profiling type in the **Memory** tool.
 
 Memory leaks occur when the JavaScript code of an application retains more and more objects in memory instead of releasing them for the browser to garbage-collect.  We built the **Detached Elements** tool with the Microsoft Teams developers, and it has already helped us find and fix memory leaks across many of our own websites and apps.
 

microsoft-edge/devtools-guide-chromium/whats-new/2021/07/devtools.md

@@ -55,7 +55,7 @@ Dark themes:
 <!-- Title: Introducing the Detached Elements tool -->
 <!-- Subtitle: Use the Detached Elements tool to find and fix DOM node memory leaks. -->
 
-March 2025 update: The **Detached Elements** tool is being removed.  To debug DOM memory leaks, use the **Detached elements** profiling type in the **Memory** tool.
+March 2025 update: The **Detached Elements** tool has been removed.  To debug DOM memory leaks, use the **Detached elements** profiling type in the **Memory** tool.
 
 A DOM node is considered "detached" when it is no longer attached to any element of the DOM but is still being retained in memory by Microsoft Edge. The browser cannot garbage-collect the element, because some JavaScript is still referencing the element even though it's no longer on the page or a part of the DOM.
 

microsoft-edge/devtools-guide-chromium/whats-new/2022/01/devtools.md

@@ -25,7 +25,7 @@ These are the latest features in the Stable release of Microsoft Edge DevTools.
 <!-- Title: Check out the new Detached Elements tool -->
 <!-- Subtitle: The new Detached Elements tool is now available by default in Microsoft Edge 97. -->
 
-March 2025 update: The **Detached Elements** tool is being removed.  To debug DOM memory leaks, use the **Detached elements** profiling type in the **Memory** tool.
+March 2025 update: The **Detached Elements** tool has been removed.  To debug DOM memory leaks, use the **Detached elements** profiling type in the **Memory** tool.
 
 A DOM node is considered _detached_ when it's no longer attached to any element of the DOM, but is still being retained in memory by Microsoft Edge.  The browser cannot garbage-collect the detached element, because some JavaScript object is still referencing the element, even though the element is no longer on the page or is no longer a part of the DOM.
 

microsoft-edge/devtools-guide-chromium/whats-new/2022/08/devtools-104.md

@@ -64,7 +64,7 @@ See also:
 <!-- Title: The Detached Elements tool now works better with assistive technology -->
 <!-- Subtitle: In Microsoft Edge 104, Screen readers announce the name of the table of detached elements in the tool. -->
 
-March 2025 update: The **Detached Elements** tool is being removed.  To debug DOM memory leaks, use the **Detached elements** profiling type in the **Memory** tool.
+March 2025 update: The **Detached Elements** tool has been removed.  To debug DOM memory leaks, use the **Detached elements** profiling type in the **Memory** tool.
 
 In previous versions of Microsoft Edge, when selecting the table of detached elements in the **Detached Elements** feature, assistive technology only announced "Table" and the number of rows and columns.  In Microsoft Edge version 104, this issue has been fixed.  When selecting the table of detached elements in the **Detached Elements** feature, assistive technology now announces "Detached Elements List, Table" and the number of rows and columns.