Skip to content

Commit cb8d0be

Browse files
committed
fix table
1 parent 7371b10 commit cb8d0be

File tree

2 files changed

+4
-2
lines changed

2 files changed

+4
-2
lines changed

docs/debugger/toc.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,9 @@
4040
items:
4141
- name: Navigation
4242
href: navigating-through-code-with-the-debugger.md
43-
- name: Breakpoints
43+
- name: Get started with breakpoints
44+
href: get-started-with-breakpoints.md
45+
- name: Using the right type of breakpoint
4446
href: using-breakpoints.md
4547
- name: Move the execution pointer
4648
href: move-the-execution-pointer-with-the-debugger.md

docs/debugger/using-breakpoints.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ This article shows how to use different types of breakpoints in Visual Studio to
2828
## Scenarios
2929

3030
| Scenario | Description |
31-
|----------|---------==----|
31+
|----------|---------------|
3232
| How do I pause running code to inspect a line of code that may contain a bug? | Set a breakpoint. For more information, see [Get started with breakpoints](get-started-with-breakpoints.md). |
3333
| Does my variable have an unexpected value? Or, do I want to inspect my app when it reaches a specific state? | Try a conditional breakpoint to control where and when a breakpoint gets activated by using conditional logic. Right-click on a breakpoint to add conditions. Set the condition to be true when the variable equals the unexpected value. For more information, see [Breakpoint conditions](#breakpoint-conditions). |
3434
| How do I log information to the Output window under configurable conditions without modifying or stopping my code? | Tracepoints allow you to log information to the Output window under configurable conditions without modifying or stopping your code. |

0 commit comments

Comments
 (0)