SEO edits for debugger and code analysis landing pages (#10382)

Mikejo5000 · web-flow · commit d49ead7761ed · 2022-09-06T09:43:52.000-06:00
* Add details for supported web and load test functionality supported in Visual Studio 2022

* SEO edits

* Link updates and minor edits

* restructured landing page
diff --git a/docs/code-quality/index.yml b/docs/code-quality/index.yml
@@ -1,10 +1,10 @@
 ### YamlMime:Landing
 
-title: Analyze code in Visual Studio
+title: Code analysis documentation - Visual Studio (Windows)
 summary: Visual Studio provides several different tools to analyze and improve code quality.
 
 metadata:
-  title: Code analyzers
+  title: Code analysis documentation - Visual Studio (Windows)
   description: Learn how Visual Studio can help you analyze code quality.
   ms.prod: visual-studio-windows
   ms.technology: vs-ide-code-analysis
diff --git a/docs/debugger/debugger-feature-tour.md b/docs/debugger/debugger-feature-tour.md
@@ -24,7 +24,11 @@ The features described here are applicable to C#, C++, Visual Basic, JavaScript,
 
 Breakpoints are a useful feature when you know the line of code or the section of code that you want to examine in detail at runtime. For more information on the different types of breakpoints, such as conditional breakpoints and function breakpoints, see [Using breakpoints](../debugger/using-breakpoints.md).
 
-To debug, you need to start your app with the debugger attached to the app process. **F5** (**Debug > Start Debugging**) is the most common way to do that. However, right now you may not have set any breakpoints to examine your app code, so we will do that first and then start debugging. Breakpoints are the most basic and essential feature of reliable debugging. A breakpoint indicates where Visual Studio should suspend your running code so you can take a look at the values of variables, or the behavior of memory, or whether or not a branch of code is getting run.
+To debug, you need to start your app with the debugger attached to the app process. To do this:
+
+- Press **F5** (**Debug > Start Debugging**), which is the most common method.
+
+However, right now you may not have set any breakpoints to examine your app code, so we will do that first and then start debugging. Breakpoints are the most basic and essential feature of reliable debugging. A breakpoint indicates where Visual Studio should suspend your running code so you can take a look at the values of variables, or the behavior of memory, or whether or not a branch of code is getting run.
 
 If you have a file open in the code editor, you can set a breakpoint by clicking in the margin to the left of a line of code.
 
diff --git a/docs/debugger/index.yml b/docs/debugger/index.yml
@@ -1,10 +1,10 @@
 ### YamlMime:Landing
 
-title: Visual Studio debugger documentation # < 60 chars
+title: Debugger documentation - Visual Studio (Windows) # < 60 chars
 summary: The Visual Studio debugger helps you observe the run-time behavior of your program and find problems. # < 160 chars
 
 metadata:
-  title: Debugging in Visual Studio (Windows) # Required; page title displayed in search results. Include the brand. < 60 chars.
+  title: Debugger documentation - Visual Studio (Windows) # Required; page title displayed in search results. Include the brand. < 60 chars.
   titleSuffix: ""
   description: Learn how to use Visual Studio to debug applications and code.
   ms.topic: landing-page
@@ -21,57 +21,42 @@ landingContent:
 # Start card title with a verb
   # Card (optional)
   - title: Get started
-    linkLists:
-      - linkListType: tutorial
-        links:
-          - text: Learn to debug C#
-            url: ../get-started/csharp/tutorial-debugger.md?toc=%252fvisualstudio%252fdebugger%252ftoc.json
-          - text: Learn to debug C++
-            url: getting-started-with-the-debugger-cpp.md
-          - text: Learn to debug Visual Basic
-            url: ../get-started/visual-basic/tutorial-debugger.md?toc=%252fvisualstudio%252fdebugger%252ftoc.json
-          - text: Run Python code in the debugger >>
-            url: ../python/tutorial-working-with-python-in-visual-studio-step-04-debugging.md
-      - linkListType: how-to-guide
-        links:
-          - text: Debugging for absolute beginners
-            url: debugging-absolute-beginners.md
-
-  # Card (optional)
-  - title: Fundamentals
     linkLists:
       - linkListType: overview
         links:
           - text: First look at the debugger
             url: debugger-feature-tour.md
           - text: What is debugging?
             url: what-is-debugging.md
-          - text: FAQ - Find your debugging feature
-            url: find-your-debugging-task.yml
-
-  # Card
-  - title: Use the debugger
-    linkLists:
       - linkListType: how-to-guide
         links:
+          - text: Start the debugger
+            url: debugger-feature-tour.md#set-a-breakpoint-and-start-the-debugger
           - text: Code stepping
             url: navigating-through-code-with-the-debugger.md
-          - text: Breakpoints
+          - text: Set a breakpoint
             url: using-breakpoints.md
           - text: Edit code and continue debugging
             url: edit-and-continue.md
           - text: Call stack
             url: how-to-use-the-call-stack-window.md
+      - linkListType: tutorial
+        links:
+          - text: Debugging for absolute beginners
+            url: debugging-absolute-beginners.md
 
-  # Card
-  - title: Inspect data
+  - title: Tutorials
     linkLists:
-      - linkListType: how-to-guide
+      - linkListType: tutorial
         links:
-          - text: Inspect variables
-            url: autos-and-locals-windows.md
-          - text: Set a watch on variables
-            url: watch-and-quickwatch-windows.md
+          - text: Learn to debug C#
+            url: ../get-started/csharp/tutorial-debugger.md?toc=%252fvisualstudio%252fdebugger%252ftoc.json
+          - text: Learn to debug C++
+            url: getting-started-with-the-debugger-cpp.md
+          - text: Learn to debug Visual Basic
+            url: ../get-started/visual-basic/tutorial-debugger.md?toc=%252fvisualstudio%252fdebugger%252ftoc.json
+          - text: Run Python code in the debugger >>
+            url: ../python/tutorial-working-with-python-in-visual-studio-step-04-debugging.md
 
     # Card
   - title: Go deeper with the debugger
@@ -94,4 +79,14 @@ landingContent:
       - linkListType: tutorial
         links:
           - text: Write and debug code with Live Share >>
-            url: /visualstudio/liveshare/use/vs
+            url: /visualstudio/liveshare/use/vs
+
+  # Card
+  - title: Inspect data
+    linkLists:
+      - linkListType: how-to-guide
+        links:
+          - text: Inspect variables
+            url: autos-and-locals-windows.md
+          - text: Set a watch on variables
+            url: watch-and-quickwatch-windows.md
diff --git a/docs/debugger/navigating-through-code-with-the-debugger.md b/docs/debugger/navigating-through-code-with-the-debugger.md
@@ -21,7 +21,7 @@ ms.workload:
 
  [!INCLUDE [Visual Studio](~/includes/applies-to-version/vs-windows-only.md)]
 
-The Visual Studio debugger can help you navigate through code to inspect the state of an app and show its execution flow. You can use keyboard shortcuts, debug commands, breakpoints, and other features to quickly get to the code you want to examine. If you're familiar with debugger navigation commands and shortcuts, you can find and resolve app problems faster and more easily.
+The Visual Studio debugger can help you navigate through code to inspect the state of an app and show its execution flow, which is also known as *code stepping*. You can use keyboard shortcuts, debug commands, breakpoints, and other features to quickly get to the code you want to examine. If you're familiar with debugger navigation commands and shortcuts, you can find and resolve app problems faster and more easily.
 
 > [!NOTE]
 > If you're new to debugging code, you might want to read [Debugging for absolute beginners](../debugger/debugging-absolute-beginners.md) and [Debugging techniques and tools](../debugger/write-better-code-with-visual-studio.md) before you read this article.
diff --git a/docs/debugger/using-breakpoints.md b/docs/debugger/using-breakpoints.md
@@ -49,7 +49,9 @@ Breakpoints are one of the most important debugging techniques in your developer
 
 You can set a breakpoint on any line of executable code. For example, in the following C# code, you could set a breakpoint on the line of code with the variable assignment (`int testInt = 1`), the `for` loop, or any code inside the `for` loop. You can't set a breakpoint on method signatures, declarations for a namespace or class, or variable declarations if there's no assignment and no getter/setter.
 
-To set a breakpoint in source code, click in the far left margin next to a line of code. You can also select the line and press **F9**, select **Debug** > **Toggle Breakpoint**, or right-click and select **Breakpoint** > **Insert breakpoint**. The breakpoint appears as a red dot in the left margin.
+To set a breakpoint in source code:
+
+- Click in the far left margin next to a line of code. You can also select the line and press **F9**, select **Debug** > **Toggle Breakpoint**, or right-click and select **Breakpoint** > **Insert breakpoint**. The breakpoint appears as a red dot in the left margin.
 
 For most languages including C#, breakpoint and current execution lines are automatically highlighted. For C++ code, you can turn on highlighting of breakpoint and current lines by selecting **Tools** (or **Debug**) > **Options** > **Debugging** >  **Highlight entire source line for breakpoints and current statement (C++ only)**.
 
