Update how-to-get-power-automate-desktop-installer-logs.md

Author: johndund

support/power-platform/power-automate/desktop-flows/how-to-get-power-automate-desktop-installer-logs.md

@@ -7,7 +7,7 @@ ms.custom: sap:Desktop flows\Working with Power Automate for desktop
 ---
 # Power Automate for desktop logs
 
-During the course of troubleshooting a problem with Power Automate for desktop, you may need to gather logs on the machine for support to analyze. These can be for a failed installation, for a problem running your desktop flows, or for a problem using Power Automate or the machine runtime application.
+During the course of troubleshooting a problem with Power Automate for desktop, you may need to gather logs on the machine for customer support to analyze. These can be for a failed installation, a problem running your desktop flows, or a problem using Power Automate or the machine runtime application.
 
 _Applies to:_   Power Automate  
 _Original KB number:_   4555577
@@ -27,7 +27,7 @@ The _Power Automate for desktop\_*.log_ file contains the general reason why the
 
 :::image type="content" source="media/how-to-get-power-automate-desktop-installer-logs/power-automate-installer-logs.png" alt-text="Screenshot of the Power automate for desktop installer logs.":::
 
-## Runtime or issues using the applications
+## On-premises product logs
 
 For issues with using Power Automate to create your flows, the Runtime Application to register or configure your machine, or during cloud runtime, you may need to gather on-premises logs.
 
@@ -40,12 +40,12 @@ If you need to gather on-premises logs manually, they can be found can be found
 
 ## Event Viewer logs
 
-These logs are helpful when a Windows service fails to start.
+Event viewer application logs are helpful when an application crashes or a Windows service fails to start.
 
 Follow these steps to view and save the logs:
 
 1. Open the Windows Event Viewer.
-2. Go to **Windows Logs** > **Application**, find the error, and review the information in the **General** and **Details** tabs.
+2. Go to **Windows Logs** > **Application**, look for an error with the source corresponding to the application that experienced the problem.
 3. If needed, use the **Filter Current Log** menu to filter by **Event level** or **Logged** time (such as the last hour).
 4. To save the filtered log file, select **Save Filtered Log File As** and save it as an event file.