Update power-apps-mobile-canvas-app-restarts.md

Author: sericks007

powerapps-docs/mobile/power-apps-mobile-canvas-app-restarts.md

@@ -52,7 +52,7 @@ The greatest memory improvements to decrease app restarts can be made by app mak
 
 | Problem | Root Cause | Mitigation |
 |---------|---------|---------|
-| App restarts when loading a specific screen. | If a specific screen is running too many formulas at one time, the app can have too much processing and be restarted by the operating system. | Limit the number of controls on a screen and the number of formulas being run when the screen is loaded, which might require splitting up screens. <br><br> Avoid control dependency between screens. <br><br> Prevent the user from taking action during high-processing moments (e.g. when a large gallery with multiple filters/lookups is loading). <br><br> Consider using named formulas. <br><br> Consider using the **Delayed Load** app setting. |
+| App restarts when loading a specific screen. | If a specific screen is running too many formulas at one time, the app can have too much processing and be restarted by the operating system. | Limit the number of controls on a screen and the number of formulas being run when the screen is loaded, which might require splitting up screens. <br><br> Avoid control dependency between screens. <br><br> Prevent the user from taking action during high-processing moments. For example, when a large gallery with multiple filters and lookups is loading. <br><br> Consider using named formulas. <br><br> Consider using the **Delayed Load** app setting. |
 | App restarts after multiple screen navigations. | There are memory leaks happening on the screens, resulting in memory usage building up as the user navigates around the app. | Turn on the **Keep recently visited screens in memory** app setting. While this increases total memory usage in the short term as the screen is preserved in memory, across multiple screen navigations, it will prevent memory leaks. |
 | App restarts when doing **SaveData**/**LoadData** or using data connections. | **SaveData** and data connections both increase the total memory being used by the app. **SaveData** is also a processing-heavy operation. Bringing in large amounts of data into the app and saving that data for offline usage (especially media content and files) can cause the app to go above its allotted memory, causing the operating system to restart the app. | Optimize the amount of data brought into the app via data connections and saved via **SaveData**. <br><br> Reduce the number of **SaveData** calls where possible. <br><br> Turning on the **Explicit column selection** app setting and turning off the **Record scope one-to-many and many-to-many relationships** app setting can also help reduce the data being brought into the app. |
 | App restarts when using the camera control. | The camera control saves the captured image to memory. This can increase the memory usage of the app, especially if the captured image is saved into variables or **SaveData** using the **OnStream** property. | Do not save any images beyond the most recently captured one. <br><br> Use **Photo** instead of **Stream** to only capture images when the user taps on the camera. <br><br> If you need to use **Stream**, set the **StreamRate** property as high as possible to reduce the number of updates. |