updating troubleshooting doc

docs/troubleshooting.md

@@ -2,7 +2,7 @@
 
 This document describes reasons and workarounds for errors you might run into when using the Makefile Tools extension.
 
-Header squiggles:
+If you see header squiggles:
 
 - Verify headers are not missing from the expected location
   - Some headers may be automatically generated by a build, so squiggles are expected on clean repository
@@ -10,7 +10,7 @@ Header squiggles:
   - Check the Makefile Tools output tab or makefile.extensionLog to see which include paths are parsed and sent by Makefile Tools
   - Then check the C/C++ output tab and diagnostics channel to see which include paths are received by the C++ extension
 
-Language squiggles:
+If you see language squiggles:
 
 - Verify (with makefile.loggingLevel set to "Verbose" or "Debug") in the output channel or in the makefile.extensionLog what are the compiler switches that Makefile Tools parses from the original compiler command line. These need to match the compiler switches from C/C++ output and diagnostic channels, with C\_Cpp.loggingLevel set to "Debug"
 
@@ -29,11 +29,11 @@ Various issues may happen if the project:
   - If the above workaround is missing, the extension is still able to handle the following most commonly found backtick pattern:
     - \`test –f 'cord/cordxtra.c' || echo './'`cord/cordxtra.c
 
-makefile.ignoreDirectoryCommands
+makefile.ignoreDirectoryCommands behavior:
 
 - Defaults to True (when we look only at what make prints from the -C argument or when make knows it changes directory)
 - True will miss any target-specific defined operations like cd, pushd, popd and the extension may calculate a wrong current path, which can result in can result in IntelliSense information being associated to a file URL that does not point to the original source file.
-  - This is rare, which is why True is default.
+    - This is rare, which is why True is default.
 
 Dryrun behavior:
 
@@ -71,7 +71,7 @@ If there is no Makefile in the root:
 - Point  **makefile.makefilePath** or makefile.configurations.makefilePath to your Makefile. Depending how the makefile is written and how paths are defined, you may need to ask make to run from that folder of the makefile instead of from the root, in which case you need to define makefile.configurations.makeArgs to include the switch "-C".
 - Manually activate the extension by either reloading the window or running any Makefile Tools command (like Configure) from the Command Palette
 
-Launch targets:
+Launch targets missing:
 
 - If there are launch targets that you expected to be found but are missing, try building first.
   - Before building, the extension only sees the output file of a link command and it will create a launch target with running that output file from the location where it is built and without passing any arguments. The output file does not have to exist in order to be included in launch targets list.