Merge pull request #14225 from Mikejo5000/mikejo-br24

Clarify content in article on debugging a deadlock

Author: prmerger-automator[bot]

docs/debugger/how-to-use-the-threads-window.md

@@ -23,7 +23,7 @@ monikerRange: '>= vs-2022'
 
 This tutorial shows how to use the **Threads** view of **Parallel Stacks** windows to debug a multithreaded application. This window helps you understand and verify the run-time behavior of multithreaded code.
 
-The Threads view is supported for C#, C++, and Visual Basic. Sample code is provided for C# and C++, but some of the content and illustrations apply only to the C# sample code.principles.
+The Threads view is supported for C#, C++, and Visual Basic. Sample code is provided for C# and C++, but some of the code references and illustrations apply only to the C# sample code.
 
 The Threads view helps you to:
 
@@ -35,7 +35,7 @@ The Threads view helps you to:
 
 Identical sections of the call stack are grouped together to simplify the visualization for complex apps.
 
-The following conceptual animation shows how grouping is applied to call stacks. Only identical segments of a call stack are grouped.
+The following conceptual animation shows how grouping is applied to call stacks. Only identical segments of a call stack are grouped. Hover over a grouped call stack to idenitfy the threads.
 
 ![Illustration of the grouping of call stacks.](../debugger/media/vs-2022/debug-multithreaded-call-stacks.gif)
 

docs/debugger/walkthrough-debugging-a-parallel-application.md

@@ -47,7 +47,7 @@ Here are a few important points to remember when interpreting data in the Tasks
 
 - Identical sections of the virtual call stack are grouped together to simplify the visualization for complex apps.
 
-  The following conceptual animation shows how grouping is applied to virtual call stacks. Only identical segments of a virtual call stack are grouped.
+  The following conceptual animation shows how grouping is applied to virtual call stacks. Only identical segments of a virtual call stack are grouped. Hover over a grouped call stack to idenitfy the threads that are running the tasks.
 
   ![Illustration of the grouping of virtual call stacks.](../debugger/media/vs-2022/debug-asynchronous-virtual-call-stacks-top-bottom.gif)