Merge pull request #50574 from v-thpra/azure-triage-fix-1055016

Technical Review 1055016: Interactively debug .NET apps with the Visual Studio debugger

Author: JamesJBarnett

learn-pr/language/dotnet-debug-visual-studio/8-knowledge-check.yml

@@ -3,7 +3,7 @@ uid: learn.dotnet-debug-visual-studio.knowledge-check
 title: Module assessment
 metadata:
   title: Module assessment
-  description: Check what you've learned.
+  description: Check what you learned about debugging in Visual Studio.
   author: alexwolfmsft
   ms.author: alexwolf
   manager: jmartens
@@ -33,36 +33,36 @@ quiz:
       choices:
         - content: '`Debug.Assert(count != 0, "Count should not be 0.");`'
           isCorrect: false
-          explanation: "Assert tests a condition. If it's true, nothing will happen or else the application will enter break mode. So here, if the count is 0, it will enter break mode."
+          explanation: "Assert tests a condition. If it's true, nothing happens or else the application enters break mode. So here, if the count is 0, it enters break mode."
         - content: '`Debug.Assert(count == 0, "Count should not be 0.");`'
           isCorrect: false
-          explanation: "Assert tests a condition. If it's true, nothing will happen or else the application will enter break mode. So here, if the count is 0, nothing will happen."
+          explanation: "Assert tests a condition. If it's true, nothing happens or else the application enters break mode. So here, if the count is 0, nothing happens."
         - content: '`Debug.WriteIf(count != 0, "Count should not be 0.");`'
           isCorrect: false
           explanation: "This code prints a message when the count doesn't equal 0."
         - content: '`Debug.WriteIf(count == 0, "Count should not be 0.");`'
           isCorrect: true
-          explanation: "This code will only print a debug message when the count is 0."
+          explanation: "This code only prints a debug message when the count is 0."
     - content: "What are the top two values a debugger provides?"
       choices:
         - content: "Control of your program execution and observation of your program's state"
           isCorrect: true
           explanation: "The two main values almost every debugger provides are the ability to control program execution and to observe program state."
-        - content: "Modifying program values and changing your program output"
+        - content: "Modifying program values and changing your program output."
           isCorrect: false
-          explanation: "Changing your program's output isn't useful because it will only have effect when the application is being debugged."
-        - content: "Observing your program's state and modifying your program values"
+          explanation: "Changing your program's output isn't useful because it only has effect when the application is being debugged."
+        - content: "Observing your program's state and modifying your program values."
           isCorrect: false
           explanation: "Observing and modifying values are important, but it's also important to be able to control the flow of program execution."
-        - content: "Editing your program while running and editing program values"
+        - content: "Editing your program while running and editing program values."
           isCorrect: false
           explanation: "Editing programs is useful, but observing your program's operational state is another important value that the .NET debugger provides."
     - content: "Which Visual Studio debugger window is most useful to observe the current value of a specific variable across different functions?"
       choices:
         - content: "Use the Locals window because it shows all variables that are currently in scope."
           isCorrect: false
           explanation: "While the Locals window does display all variables currently in scope, it's not the best way to watch the value of a specific variable."
-        - content: "Hover over the variable in the code editor to display the value."
+        - content: "Display the value by hovering over the variable in the code editor."
           isCorrect: false
           explanation: "While hovering does display the variable's current value, it's a manual process and isn't efficient."
         - content: "Use the Watch window to select specific variables or expressions to watch throughout the program's execution."

learn-pr/language/dotnet-debug-visual-studio/includes/1-introduction.md

@@ -1,17 +1,17 @@
-Visual Studio provides very powerful tools to help you debug and diagnose issues in your applications. These tools are especially valuable for analyzing state and tracking down bugs while your application is running.
+Visual Studio provides powerful tools to help you debug and diagnose issues in your applications. These tools are especially valuable for analyzing state and tracking down bugs while your application is running.
 
 :::image source="../media/visual-studio-tools.png" alt-text="Screenshot of Visual Studio debugging tools.":::
 
-## Fix Bugs Before the Application Launches
+## Fix bugs before the application launches
 
-Suppose that you work for a team that's building a new application, but you keep finding bugs in the code. The team would like to find and fix all of these issues before the app goes live. However, the issues are too subtle or complex to diagnose just by reading the code. You're looking for additional tools and assistance to track down problems while the app is running with different inputs and parameters.
+Suppose that you work for a team that's building a new application, but you keep finding bugs in the code. The team would like to find and fix all of these issues before the app goes live. However, the issues are too subtle or complex to diagnose just by reading the code. You're looking for tools to assist you in tracking down problems while the app is running with different inputs and parameters.
 
-## What will we be doing?
+## What are you going to do?
 
-This module shows you how to use the Visual Studio debugger with a .NET program. You'll learn how to leverage common features like break points and step through your code line by line. You'll also learn how to inspect the state of your program as it executes using tools like the Watch and Locals windows. Finally, you'll also use diagnostic features like the Call Stack and Traces to review code execution in greater depth.
+This module shows you how to use the Visual Studio debugger with a .NET program. You learn how to use common features like break points and how to step through your code line by line. You also learn how to inspect the state of your program as it executes, by using tools like the Watch and Locals windows. Finally, you learn how to use diagnostic features like the Call Stack and Traces to review code execution in greater depth.
 
 :::image source="../media/visual-studio-intro.png" alt-text="Screenshot of Visual Studio debugging in action.":::
 
 ## What's the main goal?
 
-By the end of this module, you'll understand how to use Visual Studio's debugging tools to analyze and fix issues in your application code.
+By the end of this module, you understand how to use Visual Studio's debugging tools to analyze and fix issues in your application code.

learn-pr/language/dotnet-debug-visual-studio/includes/2-debugger.md

@@ -2,31 +2,29 @@ During your journey as a developer, there's always *that* moment when you end up
 
 > Why isn't my code working?
 
-Asking this question is a normal part of any developer's day. The trick is to get comfortable with finding and fixing your bugs with a minimum of time and frustration. When there's a bug in your program, everyone usually has their own way of dealing with this problem.
+Asking this question is a normal part of any developer's day. The trick is to get comfortable with finding and fixing your bugs with a minimum of time and frustration. When there's a bug in your program, do you deal with it in one of these ways?
 
-You probably already have tried one or more of these debugging approaches yourself:
-
-- Try running your program again because it *should* work.
+- Run the program again because it *should* work.
 - Explain your issue to a rubber duck.
-- Read through your code again to find out the issue.
+- Read through your code again to find the issue.
 - Take a walk outside.
 - Spam a few `Console.WriteLine("here")` messages in your code.
 
-You might have various degrees of success with these methods. The one approach that's commonly regarded as being more often successful is using a debugger. But what's a debugger exactly?
+You might have various degrees of success with these methods, but one approach is commonly regarded as being the most successful. Using a debugger. But what exactly is a debugger?
 
-A debugger is a software tool you can use to observe and control the execution flow of your program with an analytical approach. Its design goal is to help find the root cause of a bug and help you resolve it. It works by either hosting your program in its own execution process or running as a separate process that's attached to your running program, like .NET.
+A debugger is a software tool you can use to observe and control the execution flow of your program with an analytical approach. Its design goal is to help you find the root cause of a bug and help you resolve it. It works by hosting your program in its own execution process. Or, by running as a separate process attached to your program, like .NET.
 
-Debuggers come in different flavors. Some work directly from the command line while others come with a graphical user interface. In this module, we'll use Visual Studio's integrated graphical debugger.
+Debuggers come in different flavors. Some work directly from the command line while others come with a graphical user interface. In this module, we use Visual Studio's integrated graphical debugger.
 
 ## Why use a debugger?
 
-If you're not running your code through a debugger, that means you're probably *guessing* what's happening in your program. The primary benefit of using a debugger is that you can *watch* your program running. You can follow your program execution one line of code at a time. In this way, you avoid the chance of guessing wrong.
+If you're not running your code through a debugger, it means you're probably *guessing* what's happening in your program. The primary benefit of using a debugger is that you can *watch* your program running. You can follow your program execution one line of code at a time. In this way, you avoid the chance of guessing wrong.
 
 Every debugger has its own set of features. The two most important ones that come with almost all of them are:
 
-- *Controlling your program execution*. You can pause your program and run it step by step, which allows you to see which code is executed and how it affects your program's state.
+- *Controlling your program execution*. You can pause your program and run it step by step, which allows you to see which code is executing and how it affects your program's state.
 - *Observing of your program's state*. For example, you can look at the value of your variables and function parameters at any point during your code execution.
 
-Mastering debugger usage is an important skill for a developer that's often overlooked. It makes you more efficient at hunting bugs in your code and can help you quickly understand how a program works.
+Using a debugger effectively is an important but overlooked skill for a developer. It makes you more efficient at hunting bugs in your code and can help you quickly understand how a program works.
 
 Let's discover that in the next unit.