resolve the warnings

Author: lucciz01

support/dynamics-365/field-service/mobile-app/webview-reset.md

@@ -4,10 +4,9 @@ description: Helps resolve WebView reset issues in the Dynamics 365 Field Servic
 author: JonBaker007
 ms.author: jobaker
 ms.reviewer: mhart
-ms.date: 12/12/2024
+ms.date: 07/04/2025
 ms.custom: sap:Mobile Application\Application is throwing errors
 ---
-
 # WebView Reset Overview
 
 This article helps you troubleshoot and resolve issues in the [Dynamics 365 Field Service mobile app](/dynamics365/field-service/mobile/overview), where the home page is unexpectedly displayed, and a WebView reset occurs.
@@ -23,17 +22,20 @@ It's important to be aware of the impact that poor memory management practices c
 
 There are two common causes of memory pressure buildup to be aware of.
 
-**Memory Spike** – A memory spike is when a large object is allocated into the WebView process and causes an immediate spike in memory usage. Examples can include storing Base64 representations of images and videos in variables within Power Apps Component Framework controls and Web Resources or utilizing JavaScript libraries that import large resource files like font libraries. If you can reliably reproduce a WebView reset through an action like opening a specific form or interacting with a specific control, you're likely encountering a memory spike. <br/>
+**Memory Spike** – A memory spike is when a large object is allocated into the WebView process and causes an immediate spike in memory usage. Examples can include storing Base64 representations of images and videos in variables within Power Apps Component Framework controls and Web Resources or utilizing JavaScript libraries that import large resource files like font libraries. If you can reliably reproduce a WebView reset through an action like opening a specific form or interacting with a specific control, you're likely encountering a memory spike.
+
 **Memory Leaks** – A memory leak is when memory is allocated within the WebView process but isn't cleaned up when no longer needed due to dangling pointers and references preventing garbage collection from reclaiming the allocated memory. This causes memory pressure buildup over time that can lead to a WebView reset. Examples include adding event listeners to the window object in Javascript but not removing them when navigating away. If you can't reliably reproduce a WebView reset and seem to experience them at random while doing different activities within the application, you're likely encountering a memory leak in the previous activities that you were performing before the reset.
 
 ## Debugging Memory Pressure
 
-The WebView reset error itself is specific to iOS applications running WebViews and can only be reproduced within that context, however any code causing memory pressure on mobile causes memory pressure buildup on desktop browsers as well. This enables investigation of the root cause of a WebView reset using browser debug tools, like those provided by Microsoft Edge for tracking memory usage: [Fix memory problems - Microsoft Edge Developer documentation](https://learn.microsoft.com/microsoft-edge/devtools-guide-chromium/memory-problems/) <br/>
-These debugging tools are also available on mobile devices if needed: [Debugging JavaScript Code in Model-Driven Apps](https://learn.microsoft.com/power-apps/developer/model-driven-apps/clientapi/debug-javascript-code) <br/>
+The WebView reset error itself is specific to iOS applications running WebViews and can only be reproduced within that context, however any code causing memory pressure on mobile causes memory pressure buildup on desktop browsers as well. This enables investigation of the root cause of a WebView reset using browser debug tools, like those provided by Microsoft Edge for tracking memory usage: [Fix memory problems - Microsoft Edge Developer documentation](/microsoft-edge/devtools-guide-chromium/memory-problems/)
+
+These debugging tools are also available on mobile devices if needed: [Debugging JavaScript Code in Model-Driven Apps](/power-apps/developer/model-driven-apps/clientapi/debug-javascript-code)
+
 When debugging memory issues on iOS directly, Safari memory analysis tools enable you to identify the memory performance of the app module: [Timelines Tab](https://webkit.org/web-inspector/timelines-tab/)
 
 ## Related content
 
-- [Debugging JavaScript Code in Model-Driven Apps](https://learn.microsoft.com/power-apps/developer/model-driven-apps/clientapi/debug-javascript-code)
-- [Fix memory problems - Microsoft Edge Developer documentation](https://learn.microsoft.com/microsoft-edge/devtools-guide-chromium/memory-problems/)
+- [Debugging JavaScript Code in Model-Driven Apps](/power-apps/developer/model-driven-apps/clientapi/debug-javascript-code)
+- [Fix memory problems - Microsoft Edge Developer documentation](/microsoft-edge/devtools-guide-chromium/memory-problems/)
 - [Performance considerations when customizing the mobile app](/dynamics365/field-service/mobile/improve-mobile-performance)