minor case, spelling, and organization fixes

Dane Springmeyer · Dane Springmeyer · commit 24e65e77f816 · 2018-11-09T09:07:59.000-08:00
diff --git a/README.md b/README.md
@@ -37,6 +37,9 @@ make test
 # Cleans your current builds and removes potential cache
 make clean
 
+# Build binaries in Debug mode (https://github.com/mapbox/cpp/blob/master/glossary.md#debug-build)
+make debug
+
 # Cleans everything, including the things you download from the network in order to compile (ex: npm packages).
 # This is useful if you want to nuke everything and start from scratch.
 # For example, it's super useful for making sure everything works for Travis, production, someone else's machine, etc
@@ -133,9 +136,9 @@ Once your project has ported node-cpp-skel, follow these steps to integrate your
 ### Adding dependencies
 With updated versions of npm, a `package-lock.json` file is created, which is now included in node-cpp-skel. See [`npm-and-package-lock.md`](./docs/npm-and-package-lock.md) for more info on how to interact with this file and how to add new dependencies.
 
-### Debug
+### Interactive Debugging
 
-* [Debug with VS CODE](./docs/howToDebugWithVSCode.md)
+* [Debugging with VS Code](./docs/debugging-with-vs-code.md)
 
 # Code coverage
 
diff --git a/docs/debugging-with-vs-code.md b/docs/debugging-with-vs-code.md
@@ -1,14 +1,22 @@
 # How to debug C++ with VS Code
 
-VS Code is a great tool to develop code in many languages. This document is to tell you how to debug C++ addon with the VS Code.
+VS Code is a great source code editor for developing code in many languages. This document is to tell you how to debug a node C++ addon with VS Code.
 
-### 1. Setting up VSCode debug
+### 1. Setting up VS Code debug
 
-To Set up the VSCode debug you have two ways to achieve:
+First open the node C++ addon folder in VS Code by choosing `File > Open`.
 
-Option 1: Press Cmd + Shift + P to open the command bar, and type open `open launch.json`, choose `C++`.
+Then to start debugging there are two ways:
 
-Option 2: Click the debug button on the right sidebar, and Click the ⚙ button on the right top, choose `C++`.
+#### Option 1
+
+Press `Cmd + Shift + P` to open the command bar, type open `open launch.json`, and then choose `C++`.
+
+Note: the first time you do this you will need to `install` the C++ Extension and reload the app.
+
+#### Option 2
+
+Click the debug button on the right sidebar, click the `⚙` button on the right top, and then choose `C++`.
 
 ![howtodebug](./image/howtodebug1.png)
 
@@ -34,15 +42,15 @@ In the `launch.json` you can see some template, like this:
 }
 ```
 
-`launch.json` defined which program you want to run after you click the run debug button, let's say we want run `node test/vtshaver.test.js`(In this command we want to use `node` to run `test/vtshaver.test.js`), so we need to change the configurations, put `program` to node's absolute path(you can use `which node` to find the path of current version of node), and change the `args` to `test/vtshaver.test.js`'s absolute path. 
+`launch.json` defines which program you want to run after you click the run debug button. Let's say we want run `node test/vtshaver.test.js`. In this case we need to change the configurations, put `program` to node's absolute path (you can use `which node` to find the path of current version of node), and change the `args` to `${workspaceFolder}/test/vtshaver.test.js`.
 
 Additional we want build C++ everytime before we start debug, so we add `preLaunchTask` into the config:
 
 ```
 "preLaunchTask": "npm: build:dev",
 ```
 
-Untill now, the config file could looks like this:
+Now the config file could look like this:
 
 
 ```json
@@ -55,7 +63,7 @@ Untill now, the config file could looks like this:
             "request": "launch",
             "preLaunchTask": "npm: build:dev",
             "program": "/Users/mapbox-mofei/.nvm/versions/node/v8.11.3/bin/node",
-            "args": ["/Users/mapbox-mofei/dev/mapbox/vtshaver/test/vtshaver.test.js"],
+            "args": ["${workspaceFolder}/test/vtshaver.test.js"],
             "stopAtEntry": false,
             "cwd": "${workspaceFolder}",
             "environment": [],
@@ -66,10 +74,10 @@ Untill now, the config file could looks like this:
 }
 ```
 
-Now you can open any C++ files and click the left side of the line number to add a breakpoint, then go to the debug button on the sidebar, click the run button on the top. 
+Now you can open any C++ files and click the left side of the line number to add a breakpoint, then go to the debug button on the sidebar, click the run button on the top.
 
 ![howtodebug](./image/howtodebug2.png)
 
-Now everything is done! Debug is Done! The program will stop at the breakpoint, you can use your mouse to explore the variable. If you want you program to continue from the breakpoint, you can navigate the program use the top control box. 
+Now everything is done! Debug is Done! The program will stop at the breakpoint, you can use your mouse to explore the variable. If you want your program to continue past the breakpoint, you can navigate the program using the top control box.
 
 ![howtodebug](./image/howtodebug3.png)
