Merge pull request #3914 from MicrosoftDocs/edit_2110600

edit for task 2110600

Author: tapanm-MSFT

powerapps-docs/maker/monitor-advanced.md

@@ -1,5 +1,5 @@
 ---
-title: Advanced monitoring concepts related to Monitor. | Microsoft Docs
+title: Advanced Monitor concepts | Microsoft Docs
 description: Learn about advanced monitoring concepts related to Monitor.
 author: hasharaf
 ms.service: powerapps
@@ -16,44 +16,43 @@ search.app:
 
 # Advanced monitoring concepts
 
-In this article, you'll learn about how to download, upload trace files in Monitor, events supported by Monitor, and unsupported scenarios.
+In this article, you'll learn about downloading and uploading trace files in Monitor, events supported by Monitor, and scenarios that Monitor doesn't support.<!--note from editor: Suggested.-->
 
 ## Download and upload trace files
 
-You can download the events that are shown in the table for offline analysis.
-Events can be downloaded in a .json or a .csv format, and can be shared with
-others. The .csv files can only be downloaded. But if you export the events
-in .json format, you can them back into the monitor tool for analysis. You can
-also attach a trace file to support service requests helping speed-up the
-solution to your problem.
+You can download the events listed in [Supported events](#supported-events) for offline analysis.<!--note from editor: Is this what you meant by "events that are shown in the table"?-->
+Events can be downloaded in .json or .csv format, and you can share them with
+others. The .csv files can only be downloaded, not uploaded, but if you download<!--note from editor: Edit okay? Or is "export" different somehow?--> the events
+in .json format, you can upload them later into Monitor for analysis. You can
+also attach a trace file to support service requests, which can help speed up getting the solution to your problem.
 
 ![Download trace files](media/monitor/download.png "Download trace files")
 
-Select **Upload** to load a .json trace file to Monitor. The upload option will remove any events currently displayed in the Monitor table, and replace the details with the events contained in the trace file.
+Select **Upload** to load a .json trace file to Monitor. This option removes any events currently displayed in the Monitor table and replaces the details with events contained in the trace file.
 
 ![Upload trace files](media/monitor/upload.png "Upload trace files")
 
-## Supported Events
+## Supported events
 
-Monitor supports several events for canvas apps and model-driven apps. Here are some examples of the supported event categories and types:
+Monitor supports several events for canvas apps and model-driven apps. The following table includes examples of the supported event categories and types.
 
 | Canvas apps | Model-driven apps |
 | - | - |
-| <ul> <li> Data connectors </li> <li> Network events (error status codes highlighted) </li> <li> Screen load metrics </li> <li> Cross-screen dependency warning </li> <li> User actions such as *Navigate*, *Select*, *SetProperty* </li> <li> Custom Trace() </li> <li> Delegated versus non-delegated queries </li> <li> Verbose switch (internal telemetry) </li> <li> Delegation </li> <li> Function </li> <li> Network </li> <li> Parsing </li> <li> Performance </li> <li> Scenario </li> <li> ScreenLoad </li> <li> Telemetry </li> <li> UserAction </li> <li> Verbose </li> </ul> | <ul> <li>	Form events, such as load and save  </li> <li> Network </li> <li> Page navigations</li> <li> command executions </li> </ul> |
+| <ul> <li> Data connectors </li> <li> Network events (error status codes highlighted) </li> <li> Screen load metrics </li> <li> Cross-screen dependency warning </li> <li> User actions such as *Navigate*, *Select*, and *SetProperty* </li> <li> Custom Trace() </li> <li> Delegated versus non-delegated queries </li> <li> Verbose switch (internal telemetry) </li> <li> Delegation </li> <li> Function </li> <li> Network </li> <li> Parsing </li> <li> Performance </li> <li> Scenario </li> <li> ScreenLoad </li> <li> Telemetry </li> <li> UserAction </li> <li> Verbose </li> </ul> | <ul> <li>	Form events, such as load and save  </li> <li> Network </li> <li> Page navigation</li> <li>Command executions </li> </ul> |
 
 ## Unsupported scenarios for Monitor
 
-The following scenarios aren't supported when using Monitor:
+Monitor doesn't support the scenarios in the following table.
 
 |Description  |App type  |
 |---------|---------|
 |Monitor connected to apps running on a mobile device (native players).     |  Canvas    |
-|Monitor connected to canvas app embedded in a model-driven app or custom page.     |  Canvas       |
-|Monitor connected to SharePoint custom form app.     | Canvas        |
-|Monitor connected to Teams embedded app. As an alternative, play the app in a web player for diagnostics purposes.     | Canvas        |
+|Monitor connected to a canvas app embedded in a model-driven app or custom page.     |  Canvas       |
+|Monitor connected to a SharePoint custom form app.     | Canvas        |
+|Monitor connected to a Microsoft Teams embedded app.<!--note from editor: Should this be "a Power Apps app in Microsoft Teams."? --> As an alternative, you can play the app in a web player for diagnostics purposes.     | Canvas        |
 |Monitor isn't supported on Internet Explorer version 11.     |  Canvas and model-driven       |
 
 ### See also
 
-- [Monitor canvas apps using Monitor](monitor-canvasapps.md)
-- [Monitor model-driven apps using Monitor](monitor-modelapps.md)
+[Debugging canvas apps with Monitor](monitor-canvasapps.md)  
+[Debugging model-driven apps with Monitor](monitor-modelapps.md)

powerapps-docs/maker/monitor-canvasapps.md

@@ -1,6 +1,6 @@
 ---
-title: Debugging canvas apps with Monitor | Microsoft Docs
-description: Learn about debugging canvas apps using Monitor.
+title: Canvas app debugging with Monitor | Microsoft Docs
+description: Learn about debugging canvas apps by using Monitor.
 author: hasharaf
 ms.service: powerapps
 ms.topic: conceptual
@@ -15,24 +15,24 @@ search.app:
 ---
 
 # Debugging canvas apps with Monitor
-
-Monitor is available by default for all canvas apps. Using Monitor, you can trace events as they occur in a canvas app during the authoring experience using the Power Apps Studio, or use Monitor to debug a canvas app's published version. To learn more about Monitor, go to [Monitor overview](monitor-overview.md).
+<!--note from editor: Please check my edit to the title in metadata; it shouldn't be the same as the H1. Also, please note that the sister topic to this one, monitor-modelapps.md, should have an H1 of "Debugging model apps with Monitor," to be parallel. (The Writing Style Guide prefers the way you have it here, with the H1 as a noun and the H2s as verbs. I realize that you don't own that topic, though.)-->
+Monitor is available by default for all canvas apps. Using Monitor, you can trace events as they occur in a canvas app during the authoring experience in Power Apps Studio, or you can use Monitor to debug the published version of a canvas app. More information: [Monitor overview](monitor-overview.md)
 
 ## Get started with Monitor in canvas apps
-
-To open Monitor when authoring an app:
+<!--markdownlint-disable MD036-->
+**To open Monitor when authoring an app**
 
 1. Sign in to [Power Apps](https://make.powerapps.com/).
 
-1. Create a [new app](https://docs.microsoft.com/powerapps/maker/canvas-apps/get-started-test-drive) or [edit an existing app](https://docs.microsoft.com/powerapps/maker/canvas-apps/edit-app).
+1. Create a [new app](https://docs.microsoft.com/powerapps/maker/canvas-apps/get-started-test-drive), or [edit an existing app](https://docs.microsoft.com/powerapps/maker/canvas-apps/edit-app).
 
-1. Select **Advanced tools** in the left pane.
+1. On the left pane, select **Advanced tools**.
 
-1. Select **Open monitor** to open Monitor for this app.
+1. Select **Open monitor**.
 
     ![Open monitor](media/monitor/open-monitor.png "Open monitor")
 
-This action opens Monitor in a new browser tab and connects it to your existing Studio session:
+This action opens Monitor in a new browser tab and connects it to your existing Power Apps Studio session.
 
 ![Monitor - opened](media/monitor/monitor-opened.png "Monitor - opened")
 
@@ -42,92 +42,87 @@ A notification appears at the top to show the current monitoring session as a *S
 > Monitor has no impact on your app. You can use Monitor with any app in
 a test environment or in production.
 
-## Open Monitor for published app
+<a name="open-monitor-for-published-app"></a>
+## Open Monitor for a published app
 
 You can also use Monitor to debug the published app in the web player.
 
-To open Monitor for a published app:
+**To open Monitor for a published app**
 
 1. Sign in to [Power Apps](https://make.powerapps.com/).
 
-1. Select **Apps** in the left pane.
+1. On the left pane, select **Apps**.
 
 1. Select an app from the list.
 
-1. Select **Monitor** from the menu. You can also select **More
-    Commands** (**...**), and then select **Monitor** instead.
+1. Select **Monitor** from the menu. Or, you can select **More
+    Commands** (**...**), and then select **Monitor**.
 
     ![Open Monitor for a published app](media/monitor/open-published-app-monitor.png "Open Monitor for a published app")
 
 1. Select **Play published app**.
 
     ![Play published app](media/monitor/play-published-app.png "Play published app")
 
-This action opens the published app in a new browser tab and connects it to your current Monitor session. You'll immediately see events in the Monitor when the app loads in the web player, and as you interact with the published app.
+This action opens the published app in a new browser tab and connects it to your current Monitor session. You'll immediately see events in Monitor when the app is loaded in the web player, and as you interact with the published app.
 
-Monitor also shows a notification to display that the monitoring session currently open is for the published version of the app.
+Monitor also displays a notification that the monitoring session that's currently open is for the published version of the app.
 
 ![Published app session](media/monitor/published-app-session.png "Published app session")
 
 ### Advanced setting: Debug published app
 
-If you want to view the source expressions in the Monitor for the published app, you need to turn on a new setting to publish the expressions with the app. This setting is similar to generating a debug file in traditional development. Publishing source expressions with your app is optional. Even when this setting is off, you can still see the events happening in your app, but you can't map these events to specific expressions or formulas.
+If you want to view the source expressions in Monitor for the published app, you need to turn on the<!--note from editor: Unless you plan to come back and remove "new" at some point, I suggest not saying this is new because it won't always be.--> setting to publish the expressions with the app. This setting is similar to generating a debug file in traditional development. Publishing source expressions with your app is optional. Even when this setting is off, you'll be able to see the events happening in your app, but you won't be able to map these events to specific expressions or formulas.
 
-To enable this setting, go to **File** > **Settings** > **Advanced settings** > Turn **Debug published app** to *On*.
+To enable this setting, go to **File** > **Settings** > **Advanced settings**, and then turn on **Debug published app**.
 
 ![Debug published app](media/monitor/debug-published-app.png "Debug published app")
 
 ### View events in Monitor
 
-To view events from your app, play the app in the Studio. Monitor will then
-display the table of events occurring along with specific details.
+To view events from your app, play the app in Power Apps Studio. Monitor will then
+display the table of events as they're occurring, along with specific details.
 
 ![View events as they occur](media/monitor/monitor-events-occurring.png "View events as they occur")
 
 ## Example: Using Monitor with canvas apps
 
-In this example, you'll use the *Northwind Sample Data* app included with
+In this example, you'll use the Northwind Sample Data app included with
 the [Northwind sample solution](https://docs.microsoft.com/powerapps/maker/canvas-apps/northwind-install).
 
-*Northwind sample solution* is a canvas app that loads sample data into Common
-Data Service. You can also create a new app or use an existing app instead.
+The *Northwind sample solution* is a canvas app that loads sample data into Microsoft Dataverse<!--note from editor: Edit okay?-->. You can also create a new app or use an existing app instead.<!--note from editor: Generally, you want to reserve italics for defining a term (as you are here) and for a few other specific cases (parameters, variables, book titles), but not error messages or file names.-->
 
 ### Background
 
-Consider the scenario where the app is deployed and the initial app version
-experiences performance degradation. The app also intermittently generates
-errors with no clear pattern. Loading data in the app succeeds mostly and fails sometimes.
+Consider the scenario where an app has been deployed, and the initial version of the app experiences performance degradation. The app also intermittently generates errors with no clear pattern. Loading data in the app succeeds most of the time, but fails sometimes.<!--note from editor: Edits in this paragraph suggested, but if you don't like, note that "succeeds mostly" implies that it doesn't quite succeed all the way.-->
 
-When you check canvas app Monitor, you see data operations as expected. However, you also see several responses with HTTP status code 429 indicating too many requests in a specific timeframe.
+When you check Monitor, you see data operations as expected. However, you also see several responses that have HTTP status code 429, indicating that there have been too many requests in a specific timeframe.
 
-When you select such an event, you see the error as *Rate limit exceeded. Try
-again in XX seconds.*
+When you select such an event, you see the error as "Rate limit exceeded. Try again in XX seconds."
 
 ![Example scenario - error 429](media/monitor/error-429.png "Example scenario - error 429")
 
 ### **Analysis**
 
 The problem needs further analysis to understand why requests are getting
 throttled. In Monitor, you see that for each **createRow** call, there are
-several **getRows** requests from the **ProgressCount.Text** property, each to a different entity. These entities aren't the entities the app is creating rows for. The **ProgressCount.Text** formula is seen in Monitor:
+several **getRows** requests from the **ProgressCount.Text** property, each to a different entity. These entities aren't the entities the app is creating rows for. The **ProgressCount.Text** formula is seen in Monitor, as shown in the following image.<!--note from editor: If the reader can't see the image, will they understand what's going on here? It seems to me that you've explained the behavior fully, but you'd be the better judge of that. If the formula needs to be fully duplicated, you can use the :::image type="complex"::: extension.-->
 
 ![Error 429 - Formula](media/monitor/error-429-formula.png "Error 429 - Formula")
 
 For each record added, the formula is evaluated again and **CountRows** is
-called on several entities. This behavior resulted in **getRows** in the log,
-since **CountRows** isn't delegated for Common Data Service. For each single
+called on several entities. This behavior results in **getRows** in the log,
+because **CountRows** isn't delegated for Dataverse<!--note from editor: Edit okay?-->. For each single
 request to add a record, you're potentially making 12 additional requests to
 count the rows in each entity.
 
-These extra requests intermittently cause errors because of the Common Data
-Service platform throttling the requests to the service. And it also explains
-the overall performance problem.
+These extra requests intermittently cause errors because the Dataverse<!--note from editor: Edit okay?--> platform is throttling the requests to the service. This also explains the overall performance problem.
 
 ## Next steps
 
 [Collaborative debugging with Monitor](monitor-collaborative-debugging.md)
 
 ### See also
 
-- [Advanced monitoring](monitor-advanced.md)
-- [Monitor model-driven apps using Monitor](monitor-modelapps.md)
+[Advanced monitoring](monitor-advanced.md)  
+[Debugging model-driven apps with Monitor](monitor-modelapps.md)