Tidying up debugging since material moved

This is an attempt - I may make further changes

Author: iriark01

docs.json

@@ -1101,9 +1101,6 @@
             "type": "markdown",
             "chapters": [{
                     "title": "Debugging",
-                    "intro": {
-                        "path": "docs/tools/debug/debug_intro.md"
-                    },
                     "sub_chapters": [{
                             "title": "Methods",
                             "sources": [{
@@ -1137,6 +1134,9 @@
                         },
                         {
                             "title": "Third party tools",
+                            "intro": {
+                                "path": "docs/tools/debug/debug_intro.md"
+                            },
                             "sources": [{
                                     "path": "docs/tools/debug/eclipse_pyocd.md"
                                 },

docs/program-setup/serial/serial_communication.md

@@ -16,11 +16,11 @@ This program prints a "Hello World!" message that you can view on a serial termi
 
 [![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Serial_STDOUT/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-Serial_STDOUT/blob/v6.0/main.cpp)
 
-### Viewing output in a serial terminal
+## Viewing output in a serial terminal
 
 Serial terminals run on your host PC. They provide an interface where your Mbed board can print and where you can type characters back to your board.
 
-Mbed CLI provides a serial terminal that is configured with a default baud rate of `9600`. When a single board is connected, run: 
+Mbed CLI provides a serial terminal that is configured with a default baud rate of `9600`. When a single board is connected, run:
 
 ```
 mbed sterm
@@ -45,26 +45,26 @@ To close the serial terminal, enter <kbd>Ctrl + C</kbd>.
 
 - To list all options, run `mbed sterm -h`:
 
-```
-usage: mbed sterm [-h] [-m TARGET] [-p PORT] [-b BAUDRATE] [-e ECHO] [-r] [-v] [-vv]
-
-Open serial terminal to connected target (usually board), or connect to a user-specified COM port
-
-optional arguments:
--h, --help            show this help message and exit
--m TARGET, --target TARGET
-                        Compile target MCU. Example: K64F, NUCLEO_F401RE,
-                        NRF51822...
--p PORT, --port PORT  Communication port. Default: auto-detect. Specifying
-                        this will also ignore the -m/--target option above.
--b BAUDRATE, --baudrate BAUDRATE
-                        Communication baudrate. Default: 9600
--e ECHO, --echo ECHO  Switch local echo on/off. Default: on
--r, --reset           Reset the targets (via SendBreak) before opening
-                        terminal.
--v, --verbose         Verbose diagnostic output
--vv, --very_verbose   Very verbose diagnostic output
-```
+    ```
+    usage: mbed sterm [-h] [-m TARGET] [-p PORT] [-b BAUDRATE] [-e ECHO] [-r] [-v] [-vv]
+
+    Open serial terminal to connected target (usually board), or connect to a user-specified COM port
+
+    optional arguments:
+    -h, --help            show this help message and exit
+    -m TARGET, --target TARGET
+                            Compile target MCU. Example: K64F, NUCLEO_F401RE,
+                            NRF51822...
+    -p PORT, --port PORT  Communication port. Default: auto-detect. Specifying
+                            this will also ignore the -m/--target option above.
+    -b BAUDRATE, --baudrate BAUDRATE
+                            Communication baudrate. Default: 9600
+    -e ECHO, --echo ECHO  Switch local echo on/off. Default: on
+    -r, --reset           Reset the targets (via SendBreak) before opening
+                            terminal.
+    -v, --verbose         Verbose diagnostic output
+    -vv, --very_verbose   Very verbose diagnostic output
+    ```
 
 ## Auto-opening a serial terminal after compilation
 
@@ -82,24 +82,24 @@ Use your terminal application to interact with the following examples.
 
 If you're not sure how to build these examples and run them on your board, please see our [build tools section](../build-tools/index.html).
 
-## Echo back characters you type
+### Echo back characters you type
 
 [![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Serial_EchoBack/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-Serial_EchoBack/blob/v6.0/main.cpp)
 
-## Use the U and D keys to make LED1 brighter or dimmer
+### Use the U and D keys to make LED1 brighter or dimmer
 
 <span class="tips">**Note:** This example only works if LED1 is on the Pwm pin of the board you are using, such as the NUCLEO-F401RE. </span>
 
 <span class="images">![](../../images/NUCLEOF401RE.png)<span>The pin map of the NUCLEO-F401RE shows LED1 on the Pwm pin.</span></span>
 
 [![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Serial_LEDControl/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-Serial_LEDControl/blob/v6.0/main.cpp)
 
-## Pass characters in both directions
+### Pass characters in both directions
 
 Tie pins together to see characters echoed back.
 
 [![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Serial_PassCharacters/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-Serial_PassCharacters/blob/v6.0/main.cpp)
 
-## Read to a buffer
+### Read to a buffer
 
 [![View code](https://www.mbed.com/embed/?url=https://github.com/ARMmbed/mbed-os-snippet-Serial_ReadToBuffer/tree/v6.0)](https://github.com/ARMmbed/mbed-os-snippet-Serial_ReadToBuffer/blob/v6.0/main.cpp)

docs/quick-start/quick-start-compiler.md

@@ -60,10 +60,3 @@ Alternatively, you may select the import button on the top left hand side of the
 1. Open the folder where the executable file was downloaded, and then click and drag (or copy and paste) the file to your Mbed board's USB device folder.
 
 1. Press the board's reset button.
-
-## Related links
-
-- [Collaborating with multiple authors](../build-tools/collaborative-work.html).
-- [Mbed OS statistics API](../apis/mbed-statistics.html).
-- [Mbed OS configuration](../program-setup/advanced-configuration.html).
-- [Mbed OS serial communication](../program-setup/serial-communication.html).

docs/tools/debug/debug_intro.md

@@ -1,4 +1,4 @@
-# Debugging
+<h1 id="debugging">Debugging with third party tools</h1>
 
 There are extensive instructions on debugging Arm Mbed OS applications with [uVision 5](../debug-test/keil-uvision.html), [Eclipse](../debug-test/third-party-tools.html) and [Visual Studio Code](../debug-test/visual-studio-code.html), but you can use any IDE that supports GDB to debug Mbed OS applications. This document gives advice on how to configure these IDEs. Before starting, first [configure your local debug toolchain](setting-up-a-local-debug-toolchain.html).
 

docs/tools/debug/debugging_mbed_os_apps.md

@@ -1,4 +1,4 @@
-# Debugging Arm Mbed OS applications
+# Debugging methods for Arm Mbed OS applications
 
 At the heart of Arm Mbed is the [Online Compiler](../build-tools/mbed-online-compiler.html). While that is incredibly convenient for getting a project started or while prototyping, chances are that at some point you'll miss a debugger, or you'll want to develop while not having an active internet connection. Through debugging, you can do things such as set breakpoints, set watchpoints, view registers, view disassembly, browse memory and examine the callstack. These docs will help you debug your applications.
 
@@ -8,7 +8,7 @@ The simplest way to debug your code is to augment your code with log statements,
 
 Keil uVision natively supports debugging Mbed OS applications. To set up uVision, read [Debugging with Keil uVision](../debug-test/keil-uvision.html).
 
-Mbed also supports debugging using any IDE that supports GDB. To set up the debugger, first read [Setting up your local debug toolchain](setting-up-a-local-debug-toolchain.html). Then read the section for your specific IDE. The same principles apply to any unlisted IDEs that supports GDB:
+Mbed also supports debugging using any IDE that supports GDB. To set up the debugger, first read [Setting up your local debug toolchain](../debug-test/setting-up-a-local-debug-toolchain.html). Then read the section for your specific IDE. The same principles apply to any unlisted IDEs that supports GDB:
 
 1. Producing [debug builds with Arm Mbed CLI](../program-setup/debug-builds-cli.html).
 1. Debugging with [Eclipse](../debug-test/third-party-tools.html).

redirects.json

@@ -50,7 +50,7 @@
     "reference/bare-metal-apis.html": "apis/index.html",
     "reference/configuration-mesh.html": "apis/configuration-mesh.html",
     "tools/greentea-testing-applications.html": "debug-test/greentea-for-testing-applications.html",
-    "tools/debugging-arm-mbed-os-applications.html": "debug-test/debugging-arm-mbed-os-applications.html",
+    "tools/debugging-arm-mbed-os-applications.html": "debug-test/debugging-methods-for-arm-mbed-os-applications.html",
     "tools/setting-up-a-local-debug-toolchain.html": "debug-test/setting-up-a-local-debug-toolchain.html",
     "tools/daplink.html": "debug-test/daplink.html",
     "tools/icetea-testing-applications.html": "debug-test/icetea-test-applications.html",