Add more clear instructions

Author: Chetan Pandey

diagnostics/README.md

@@ -1,17 +1,15 @@
 # Gathering Diagnostics and Logs
-
-This folder contains directions for gathering various detailed diagnostics/logs when reporting WV2-related issues. There's generally no need to proactively get any of these diagnostics before opening an issue, but if one seems obvious feel free to get it before opening an issue. Otherwise, a WV2 developer might link you to one of these pages to help them investigate an issue.
+This folder provides step-by-step instructions for collecting detailed diagnostics and logs to help troubleshoot WebView2-related issues. Before opening a new issue, please review the table below and gather the most relevant diagnostic logs for your scenario. Supplying the appropriate logs greatly improves the chances of a quick and accurate resolution.
 
 | Tool / Log                | Purpose                                                                 | Use Case                                                                 |
 |---------------------------|-------------------------------------------------------------------------|--------------------------------------------------------------------------|
 | [Crash Dumps](crash.md)               | Capture crash data for WebView2 processes.                              | Used when a child process crashes (via ProcessFailed event) or browser process fails. |
+| [ETW Trace](etw.md)                 | Event Tracing for Windows logs detailed system and WebView2 activity.   | **Preferred log for most WebView2 issues.** Used to analyze system state and WebView2 behavior before/during issues. |
 | [Memory Dumps (Task Manager)](task_manager_dump.md)| Manual memory capture for unresponsive processes.                      | Helpful when WebView2 hangs or becomes non-responsive.                   |
-| [ETW Trace](etw.md)                 | Event Tracing for Windows logs detailed system and WebView2 activity.   | Used to analyze system state and WebView2 behavior before/during issues. |
 | [Installer Logs](install.md)            | Logs errors encountered during WebView2 runtime installation or updates.| Diagnose installation failures or update issues.                         |
-| [GPU Info](gpu.md)                  | Provides details about the GPU and rendering pipeline.                  | Useful for troubleshooting graphics-related problems.                    |
+| [GPU Info](gpu.md)                  | Provides details about  the GPU and rendering pipeline.                  | Useful for troubleshooting graphics-related problems.                    |
 | [Network Logs](network.md)              | Records network requests, responses, and errors.                        | Diagnose issues with loading resources or connectivity failures.         |
 | [Code Integrity](code_integrity.md)            | Identifies root causes of `STATUS_INVALID_IMAGE_HASH` errors.           | Used when encountering image hash validation failures.                   |
 | [Test in Canary](test_canary.md)            | Allows testing of WebView2 runtime changes using Edge Canary builds.    | Preview and validate fixes or features before stable release.            |
-| [Procmon (Process Monitor)](procmon.md) | Logs file and registry access events.                                   | Useful for diagnosing file not found or access denied errors.            |
-| [Time Travel Debugging (TTD)](ttd.md)  | Captures detailed call stacks and execution sequences.                                        | Ideal for deep debugging when other logs are insufficient.                 |
- 
+| [Procmon (Process Monitor)](procmon.md) | Captures detailed file system, registry, and process activity.           | Useful for diagnosing issues such as missing files, access denied errors, or interference from other processes.                    |
+| [Time Travel Debugging (TTD)](ttd.md)  | Captures detailed call stacks and execution sequences.                                        | Ideal for deep debugging when other logs are insufficient.                 |

diagnostics/etw.md

@@ -7,7 +7,7 @@ ETW traces can get fairly large, so try to keep the amount of extra time spent w
 
 1. Close Edge and any other apps using WV2 to make the trace more clear. Common apps using WV2 may include `widgets.exe`, `msteams.exe`, and Microsoft Office products.
 2. Download [WebView2_CPU.wprp](resources/WebView2_CPU.wprp) from this repo.
-3. If your app has a specific profile, merge it with [WebView2_CPU.wprp](resources/WebView2_CPU.wprp) to ensure all events are captured in a single ETL file.
+3. **Optional**: If your app has a specific profile, merge it with [WebView2_CPU.wprp](resources/WebView2_CPU.wprp) to ensure all events are captured in a single ETL file.
 4. In an elevated command prompt run `wpr -start WebView2_CPU.wprp -filemode` (wpr.exe is included in Windows).
 5. Reproduce the issue.
 6. In an elevated command prompt run `wpr -stop trace.etl "trace"`.

diagnostics/procmon.md

@@ -2,25 +2,25 @@
 
 Process Monitor is an advanced monitoring tool for Windows that shows real-time file system, Registry and process/thread activity. Read more [here](https://learn.microsoft.com/en-us/sysinternals/downloads/procmon).
 
-Procmon logs can be helpful for cases where we get file not found error or access denied.
+Procmon logs help quickly identify issues like missing files, registry errors, or process conflicts affecting WebView2.
 
 
 ### Steps to collect Procmon logs 
 
-1.	Download Procmon from [Microsoft Learn](https://learn.microsoft.com/en-us/sysinternals/downloads/procmon)
+1.	Download Procmon from [Microsoft Learn](https://learn.microsoft.com/en-us/sysinternals/downloads/procmon).
 
 2.	Extract the zip file  and copy **Procmon.exe** ( or **Procmon64.exe** for 64-bit systems) to the target machine.
 
-3.	Launch **Procmon.exe** and accept the license agreement
+3.	Launch **Procmon.exe** and accept the license agreement.
 
 4.	By default, Procmon starts capturing events immediately. 
 
-5.	Stop the capture by clicking the **Play button**.
+5.	Stop the capture by clicking the **Capture button** (or **File > Capture Events**).
 
-6.	Before capturing the logs, one can add filters using the Filter button. 
+6.	Before capturing the logs, one can add also filters like process id, process name, etc. using the **Filter button**. 
 
-7.	After applying the filters, start capturing the log by clicking the **Play button**.
+7.	After applying the filters, start capturing the log by clicking the **Capture button**.
 
-8.	After your repro, again click the **Play button** to stop the capturing and then using the save button, save the logs as .PML file to any location.
+8.	After your repro, again click the **Capture button** to stop the capturing and then using the save button, save the logs as .PML file to any location.
 
 9.	Compress these logs and share the zip file.

diagnostics/resources/pid-taskbar.png

@@ -4,7 +4,7 @@ In some cases, a user might need to manually gather a memory dump, normally for
 1. Open Task Manager (Ctrl+Shift+Esc).
 2. Click "Details" on the left menu.
 3. Sort by the "Name" column.
-4. Scroll to find "msedgewebview2.exe"
+4. Search for "msedgewebview2.exe" in search box.
 5. To find the right msedgewebview2.exe, you can use a combination of:
     1. The "Package name" column, which will represent the application using WebView2. (you might need to right-click the column headers, choose "select columns" and check the box for "Package name")
     2. The "Description" column, which will describe which of WebView2's processes it is. (you might need to make Task Manager very wide to see this one, you can drag to re-arrange the columns if needed)

diagnostics/task_manager_dump.md

@@ -3,9 +3,9 @@ Time Travel Debugging (TTD) is a powerful debugging tool that records comprehens
 
 ### Prerequisites
 
-1. Download and install TTD using this [link](https://aka.ms/ttd/download)
-2. After installation, the TTD command (`ttd.exe`) will be available in your system PATH
-3. **Important**: TTD requires administrative privileges - always run commands from an elevated command prompt
+1. Download and install TTD using the [Preferred Method](https://learn.microsoft.com/en-us/windows-hardware/drivers/debuggercmds/time-travel-debugging-ttd-exe-command-line-util).
+2. After installation, the TTD command (`ttd.exe`) will be available in your system PATH.
+3. **Important**: TTD requires administrative privileges - always run commands from an elevated command prompt.
 ### Collecting TTD Traces
 
 #### Browser Process Tracing
@@ -14,9 +14,9 @@ Time Travel Debugging (TTD) is a powerful debugging tool that records comprehens
 
 2. **Start TTD tracing** with the following command:
    ```
-   ttd.exe -attach <browser-pid> -dumpfull
+   ttd.exe -attach <browser-pid>
    ```
-   > **Tip**: Use the `-out` parameter to specify a custom output location for the trace files
+   > **Tip**: Use the `-out` parameter to specify a custom output location for the trace files.
 
 3. **Wait for confirmation** - You should see a message indicating that tracing has started:
    ![TTD Started](resources/ttd-started.png)
@@ -25,21 +25,21 @@ Time Travel Debugging (TTD) is a powerful debugging tool that records comprehens
 
    ![TTD Control Window](resources/ttd-window.png)
 
-5. **Reproduce the issue** - Execute the scenario you want to debug. Note that TTD may cause slight performance degradation during recording
+5. **Reproduce the issue** - Execute the scenario you want to debug. Note that TTD may cause slight performance degradation during recording.
 
-6. **Stop tracing** - Click the **Tracing Off** button in the control window when you've finished reproducing the issue
+6. **Stop tracing** - Click the **Tracing Off** button in the control window when you've finished reproducing the issue.
 
 #### Renderer Process Tracing
 
-For renderer process or any sandboxed process, it’s important to use the `--no-sandbox` browser argument. These are the options to set this to the setting:
+For renderer process or any sandboxed process, it’s important to use the `--no-sandbox` argument as sandboxing restricts debugger-level access and prevents trace recording. These are the options to set this to the setting:
 
-- **Option 1**: 
+- **Option 1: "Windows Environment Variable Update"**: 
 
     * Search **Edit the System environment variable** in windows search and open the window.
 
-    * Click on the Environment variables button and add a new entry with key: `WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS` and value: `--no-sandbox`
+    * Click on the Environment variables button and add a new entry with key: `WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS` and value: `--no-sandbox`.
 
-- **Option2**: 
+- **Option 2: "WebView2 Utility"**: 
 
     * Open [WebView2 utilities](https://david-risney.github.io/WebView2Utilities/) and go to your app.
 
@@ -50,22 +50,22 @@ For renderer process or any sandboxed process, it’s important to use the `--no
 2. **Find the renderer process ID** following the [steps outlined below](#finding-process-id)
 3. **Start TTD tracing**:
    ```
-   ttd.exe -attach <renderer-pid> -dumpFull
+   ttd.exe -attach <renderer-pid>
    ```
-4. **Monitor and reproduce** - The TTD control window will appear. Reproduce your scenario and click "Tracing Off" when complete
-5. **Security cleanup** - Remove the `--no-sandbox` argument after collecting the trace to restore normal security
+4. **Monitor and reproduce** - The TTD control window will appear. Reproduce your scenario and click "Tracing Off" when complete.
+5. **Security cleanup** - Remove the `--no-sandbox` argument after collecting the trace to restore normal security.
 
-In both the cases, *.out* and *.run* will be saved to the specified location ( or in the same folder from where you are running your commands if you haven't specified anything ). 
+In both the cases, *.out* and *.run* files will be saved to the specified location (or in the same folder from where you are running your commands if you haven't specified anything). 
 
-For more details on the ttd and to capture other processes., refer to this [link](https://learn.microsoft.com/en-us/windows-hardware/drivers/debuggercmds/time-travel-debugging-ttd-exe-command-line-util)
+For more details on the ttd and to capture other processes, refer to [Microsoft Learn](https://learn.microsoft.com/en-us/windows-hardware/drivers/debuggercmds/time-travel-debugging-ttd-exe-command-line-util)
 
 
-### Steps to find pid for a process
+### Steps to find PID for a process
 
 - Open the Task Manager and go to Details pane.
 
-- If the Details view doesn't show **Command Line** column, right click on any column and select **Select Columns**. Now add **Command Line** column to the view.
+- If the Details view does not show **Command Line** column, right click on any column and select **Select Columns**. Now add **Command Line** column to the view.
 
-- Search for msedgewebview2.exe process and find the process which contains  “--embedded-browser-webview=1 --webview-exe-name={`app-exe-name`}” argument. Get the pid of the process
+- Search for the msedgewebview2.exe process and find the process which contains the  “--embedded-browser-webview=1 --webview-exe-name={`app-exe-name`}” argument. Get the PID of the process.
 
 ![pid-taskbar](resources/pid-taskbar.png)