added links to property pages

Mikejo5000 · Mikejo5000 · commit b4b190d56aae · 2017-11-07T14:37:34.000-08:00
diff --git a/docs/linux/configure-a-linux-project.md b/docs/linux/configure-a-linux-project.md
@@ -64,4 +64,8 @@ Since all compilation is happening on a remote computer, several additional Buil
 ![Build Events](media/settings_buildevents.png)
 
 ## See Also
-[Working with Project Properties](../ide/working-with-project-properties.md)
+[Working with Project Properties](../ide/working-with-project-properties.md)  
+[C++ General Properties (Linux C++)](../linux/prop-pages/general-linux.md)  
+[VC++ Directories (Linux C++)](../linux/prop-pages/directories-linux.md)  
+[Copy Sources Project Properties (Linux C++)](../linux/prop-pages/copy-sources-project.md)  
+[Build Event Properties (Linux C++)](../linux/prop-pages/build-events-linux.md)
diff --git a/docs/linux/deploy-run-and-debug-your-linux-project.md b/docs/linux/deploy-run-and-debug-your-linux-project.md
@@ -47,11 +47,13 @@ There are several ways to interact with and debug your Linux project.
 
     ![Remote Architecture](media/architecture.png)
 
-3. Set a breakpoint by clicking in the left gutter of some code that you know will execute. A red circle appears.
+3. Set a breakpoint by clicking in the left gutter of some code that you know will execute.
+
+    A red dot appears on the line of code where you set the breakpoint.
 
 4. Press **F5** (or **Debug > Start Debugging**) to start debugging.
 
-    When you start debugging the application first will be compiled on the remote target. Any compilation errors will appear in the **Error List** window.
+    When you start debugging, the application is compiled on the remote target before it starts. Any compilation errors will appear in the **Error List** window.
 
     If there are no errors, the app will start and the debugger will pause at the breakpoint.
 
@@ -76,3 +78,6 @@ There are several ways to interact with and debug your Linux project.
 * Specific debugger options can be passed to GDB using the **Additional Debugger Commands** entry.  For example, you might want to ignore SIGILL (illegal instruction) signals.  You could use the **handle** command to achieve this.  by adding the following to the **Additional Debugger Commands** entry as shown above:
 
   ```handle SIGILL nostop noprint```
+
+## See also
+[C++ Debugging Properties (Linux C++)](../linux/prop-pages/debugging-linux.md).
