edits

Author: Mikejo5000

docs/debugger/how-to-use-the-call-stack-window.md

@@ -90,9 +90,11 @@ Non-user code is any code that is not shown when [Just My Code](../debugger/just
   ::: moniker range=">=vs-2022"
 
 ## View all related threads
-Toggle the **View all threads** button to see all the related threads in the [Parallel Stack window](../debugger/using-the-parallel-stacks-window.md). 
 
-## Call Stack Search 
+Toggle the **View all threads** button to see all the related threads in the [Parallel Stack window](../debugger/using-the-parallel-stacks-window.md). The Parallel Stacks window provides visualizations of the call stacks for multithreaded apps.
+
+## Call Stack Search
+
 You can search for relevant call stack frames by typing relevant search terms in the search box located in the top left corner of the call stack window. The pertinent call stack frames will get highlighted. 
 
   ::: moniker-end

docs/debugger/navigating-through-code-with-the-debugger.md

@@ -1,7 +1,7 @@
 ---
 title: "Navigate code with the debugger"
 description: "Learn how to use the Visual Studio debugger to troubleshoot your code. Topics include entering break mode, stepping through code, and running to a target."
-ms.date: 06/27/2024
+ms.date: 06/09/2025
 ms.topic: how-to
 f1_keywords: 
   - vs.debug.execution
@@ -192,9 +192,6 @@ While the debugger is paused, you can hover over a statement in source code or t
 
 ![Screenshot that shows Run to Click and the green arrow.](../debugger/media/dbg-run-to-click.png)
 
-> [!NOTE]
-> **Run to Click** is available starting in Visual Studio 2017.
-
 ::: moniker range=">= vs-2022"
 ### Force run to click