Fix comment formatting.

Was supposed to be removed in the previously merged PR.
realm · Dec 27, 2023 · ca7386e · ca7386e
1 parent 0aa24c6
commit ca7386e
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/contrib/debugging-cpp.md b/contrib/debugging-cpp.md
@@ -99,7 +99,7 @@ Click on the `Run and Debug` tab in the left bar of VS Code:
 
 ![Debug Icon](./assets/debugIcon.png)
 
-Select `LLDB & Node: Integration test` from the run tab:
+Select `LLDB & Node: Integration tests` from the run tab:
 
 ![Run and Debug Tab](./assets/launch-run-and-debug.png)
 
@@ -117,7 +117,7 @@ Visual Studio Code with the [CodeLLDB](https://marketplace.visualstudio.com/item
 
 The [launch.json](https://github.com/realm/realm-js/blob/main/.vscode/launch.json) file contains various useful debugger launch configurations which attach `lldb` to the `node` process so that breakpoints can be set and exceptions can be caught. These profiles can be selected from the list in the top of the `Run and Debug` pane in VS Code.
 
-[//]: # "TODO: Possibly update this statement or launch.json (we only have 1 "preLaunchTask"):"
+[//]: # "TODO: Possibly update this statement or launch.json (we only have 1 'preLaunchTask'):"
 All the launch configurations are configured to compile Realm JS in debug mode (by prelaunching a task from [tasks.json](https://github.com/realm/realm-js/blob/main/.vscode/tasks.json)) before starting the debug session, so you do not need to remember to compile between sessions.
 
 By default, running the tests will prompt you for a string to filter out which tests to run each time you invoke it. If you are debugging a specific test, it can save time if you temporarily hardcode the filter as in the example below (for the "LLDB: Integration tests" configuration):