LinkChecker fun

Author: iriark01

docs/api/api.md

@@ -2,13 +2,13 @@
 
 ### Platform APIs
 
-[Platform APIs](platform.html) provide general purpose MCU management infrastructure, common data structures and a consistent user experience on top of different standard libraries and toolchains. 
+[Platform APIs](platform.html) provide general purpose MCU management infrastructure, common data structures and a consistent user experience on top of different standard libraries and toolchains.
 
 <table>
 <tbody>
 <tr>
 <td><a href="wait.html">Wait</a></td>
-<td><a href="idleloop.html">IdleLoop</a></td>
+<td><a href="Idle-loop.html">IdleLoop</a></td>
 <td><a href="debug.html">Debug</a></td>
 <td><a href="noncopyable.html">NonCopyable</a></td>
 <td><a href="circularbuffer.html">CircularBuffer</a></td>
@@ -38,7 +38,7 @@
 
 ### Drivers APIs
 
-[Driver APIs](drivers.html) include analog and digital inputs and outputs on development boards, as well as digital interfaces, which allow your board to interface with a computer or external devices. 
+[Driver APIs](drivers.html) include analog and digital inputs and outputs on development boards, as well as digital interfaces, which allow your board to interface with a computer or external devices.
 
 <table>
 <tbody>

docs/api/drivers/RawSerial.md

@@ -22,7 +22,7 @@ _9600-8-N-1_, a  common notation for serial port settings, describes the default
 
 [![View code](https://www.mbed.com/embed/?type=library)](http://os-doc-builder.test.mbed.com/docs/development/mbed-os-api-doxy/classmbed_1_1_raw_serial.html)
 
-<span class="notes">**Note**: On a Windows machine, you need to install a USB serial driver. See [Windows serial configuration](/docs/development/tutorials/serial-communication.html#windows-serial-driver).</span>
+<span class="notes">**Note**: On a Windows machine, you need to install a USB serial driver. See [Windows serial configuration](/docs/development/tutorials//docs/development/tutorials/serial-communication.html#windows-serial-driver).</span>
 
 ### RawSerial hello, world
 

docs/api/networkinterfaces/networkinterface.md

@@ -82,7 +82,7 @@ if (wifi) {
 ### Related content
 
 - [Configuring the default network interface](/docs/development/reference/configuration-connectivity.html#selecting-the-default-network-interface).
-- [Network connectivity](/docs/development/reference/connectivity-tech.html).
+- [Network connectivity](/docs/development/reference/connectivity-stacks.html).
 - [IP networking](/docs/development/reference/ip-networking.html).
 - [Network status API](network-status.html).
 - [Network sockets](/docs/development/apis/network-socket.html).

docs/api/platform/IdleLoop.md

@@ -1,4 +1,4 @@
-### Idle loop
+## Idle loop
 
 Idle loop is a background system thread, which scheduler executes when no other threads are ready to run. That may happen when your application is waiting for an event to happen. By default, the idle loop invokes sleep manager to enter a sleep mode. You can overwrite this behavior by providing a different handler:
 
@@ -14,7 +14,7 @@ void main()
 }
 ```
 
-#### Function reference
+### Function reference
 
 [![View code](https://www.mbed.com/embed/?type=library)](http://os-doc-builder.test.mbed.com/docs/development/mbed-os-api-doxy/group__rtos___idle.html)
 
@@ -24,8 +24,6 @@ void main()
 
 ### Related content
 
-### Related content
-
 - [DeepSleepLock API reference](deepsleeplock.html).
 - [Power management API reference](power-management.html).
 - [Office Hours video about low power, tickless and sleep](https://www.youtube.com/watch?v=OFfOlBaegdg).

docs/introduction/terms.md

@@ -6,11 +6,11 @@
 
 **Application** - An executable module built out of libraries that acts as a final product.
 
-**Arm Mbed CLI** - The name of the Arm Mbed [command-line tool](/docs/development/tools/developing-arm-mbed-cli.html), packaged as `mbed-cli`.
+**Arm Mbed CLI** - The name of the Arm Mbed [command-line tool](/docs/development/tools/developing-mbed-cli.html), packaged as `mbed-cli`.
 
 **Arm Mbed interface** - The extra chip that sits on all [Mbed Enabled development boards](index.html). It's what makes the target chip (for example, K64F) look like a USB drive. It usually runs a separate piece of software that generally doesn't change. That software is usually `DAPLink`, `CMSIS-DAP` or `STLink`.
 
-**Arm Mbed Online Compiler** - [Arm’s online tool](/docs/development/tools/developing-arm-mbed-online-compiler.html), which you can use to create and compile your code.
+**Arm Mbed Online Compiler** - [Arm’s online tool](/docs/development/tools/developing-mbed-online-compiler.html), which you can use to create and compile your code.
 
 **Arm Mbed OS** - Arm's [platform operating system](https://os.mbed.com/docs) for the Internet of Things.
 

docs/porting/connectivity/LoRaPortingGuide.md

@@ -1,6 +1,6 @@
 <h2 id="lora-port">Porting LoRaWAN stack and LoRa RF drivers</h2>
 
-Mbed OS contains a native LoRaWAN stack (inside the Mbed OS tree) augmented with most commonly used LoRa RF drivers (outside the Mbed OS tree). Arm encourages developers around the globe to contribute to any of the Mbed OS features and functionality, including the LoRaWAN stack and related RF drivers using the [general guidelines provided](/docs/development/reference/guidelines.html).
+Mbed OS contains a native LoRaWAN stack (inside the Mbed OS tree) augmented with most commonly used LoRa RF drivers (outside the Mbed OS tree). Arm encourages developers around the globe to contribute to any of the Mbed OS features and functionality, including the LoRaWAN stack and related RF drivers using the [general guidelines provided](/docs/development/reference/contributing.html).
 
 The information in this section can be classified in two subsections:
 

docs/reference/configuration/mesh.md

@@ -8,7 +8,7 @@ This guide is divided in sections, and generic Nanostack configurations are firs
 
 For understanding the technologies and APIs, please refer to following sections before this one:
 
-- [Network connectivity in Mbed OS](connectivity-tech.html) technology page.
+- [Network connectivity in Mbed OS](connectivity-stacks.html) technology page.
 - [6LoWPAN Mesh technology](mesh-tech.html) page.
 - [6LoWPAN Mesh class reference](/docs/development/apis/mesh-api.html) user API.
 - [Socket API](/docs/development/apis/network-socket.html).

docs/reference/contributing/contributing.md

@@ -2,4 +2,4 @@
 
 The Arm Mbed OS porting guide describes how to a add development board Mbed OS and configure it. It includes porting information about related features, such as cellular, exporters and Mbed TLS. It also contains information about CMSIS, RTX and Thread safety.
 
-Please see the contributing guide's section on [contributing code](/docs/development/reference/guidelines.html#style) for style and ABI requirements.
+Please see the contributing guide's section on [contributing code](/docs/development/reference/style.html) for style and ABI requirements.

docs/reference/contributing/guidelines/design_guidelines.md

@@ -9,7 +9,7 @@ Principles of Arm Mbed software:
 
 ### Style
 
-Please refer to the [Mbed style guide](/docs/development/reference/guidelines.html#style).
+Please refer to the [Mbed style guide](/docs/development/reference/style.html).
 
 ### Organization
 

docs/reference/contributing/guidelines/style.md

@@ -2,11 +2,11 @@
 
 The Arm Mbed OS codebase is hosted on GitHub, and you can submit new features or bug fixes. Please follow the [guidelines for GitHub pull requests](#guidelines-for-github-pull-requests) and the [coding style guide](#coding-style) in your submissions.
 
-<span class="tips">**Tip:** Please also read the [CLA](guidelines.html#cla) and [workflow](guidelines.html#workflow) sections for a review of the process and legal requirements.</span>
+<span class="tips">**Tip:** Please also read the [CLA](/docs/development/reference/license.html) and [workflow](/docs/development/reference/workflow.html) sections for a review of the process and legal requirements.</span>
 
 ### Code acceptance
 
-[After the CLA](guidelines.html#cla) is in place and the code has gone through automated testing, developers will take a look and comment on the pull request. If all is well and acceptable, your code will be ready for merging into the central development branch.
+[After the CLA](/docs/development/reference/license.html) is in place and the code has gone through automated testing, developers will take a look and comment on the pull request. If all is well and acceptable, your code will be ready for merging into the central development branch.
 
 ### Coding style
 

docs/reference/contributing/guidelines/workflow.md

@@ -1,6 +1,6 @@
 ## Workflow
 
-All code changes and additions to Mbed OS are handled through GitHub. If you want to contribute, either by adding features or by fixing bugs, please follow the guidelines for [new features](#features) and [bugs](#reporting-bugs). In both cases, please follow the [code style guide and GitHub pull request guidelines](guidelines.html#style). Please also read the [Contributor License Agreement (CLA)](guidelines.html#cla) guidelines because we will immediately close pull requests submitted without a CLA.
+All code changes and additions to Mbed OS are handled through GitHub. If you want to contribute, either by adding features or by fixing bugs, please follow the guidelines for [new features](#features) and [bugs](#reporting-bugs). In both cases, please follow the [code style guide and GitHub pull request guidelines](/docs/development/reference/style.html). Please also read the [Contributor License Agreement (CLA)](/docs/development/reference/license.html) guidelines because we will immediately close pull requests submitted without a CLA.
 
 ### Mbed OS maintainers
 

docs/tools/CLI/debug_builds_cli.md

@@ -1,6 +1,6 @@
 <h2 id="debug-builds-cli">Debug builds</h2>
 
-After you've set up your [local debug toolchain](toolchain-profiles.html), you need firmware that includes program symbols (an `.elf` file). Because the Arm Mbed Online Compiler only produces binaries that omit the program symbols, you need to compile locally using [Arm Mbed CLI](developing-arm-mbed-cli.html).
+After you've set up your [local debug toolchain](toolchain-profiles.html), you need firmware that includes program symbols (an `.elf` file). Because the Arm Mbed Online Compiler only produces binaries that omit the program symbols, you need to compile locally using [Arm Mbed CLI](developing-mbed-cli.html).
 
 <span class="notes">**Note:** Make sure to do a clean build when switching to and from debug and release by removing the `BUILD` folder.</span>
 

docs/tools/IDE/compiler_pull_requests.md

@@ -10,4 +10,4 @@ An important thing to know about pull requests is that they can only exist betwe
 
 #### Tutorial
 
-For more information about using pull requests on the Online Compiler, please see [our tutorial](/docs/development/tutorials/pr-tutorial.html), which covers creating and editing a pull request, viewing a pull request and accepting or rejecting a pull request.
+For more information about using pull requests on the Online Compiler, please see [our tutorial](/docs/development/tools/pr-tutorial.html), which covers creating and editing a pull request, viewing a pull request and accepting or rejecting a pull request.

docs/tools/IDE/oc_tut.md

@@ -97,7 +97,7 @@ The **Compile** menu offers five options:
 
 ### Copying the file to the board
 
-<span class="notes">**Note:** If you're working on Windows, you might need to install a driver to allow you to copy to your board. Please see the [Windows Serial Driver section](serial-communication.html).</span>
+<span class="notes">**Note:** If you're working on Windows, you might need to install a driver to allow you to copy to your board. Please see the [Windows Serial Driver section](/docs/development/tutorials/serial-communication.html).</span>
 
 Your board should appear on your computer as removable storage. To run your program on the board, simply drag and drop the file you downloaded in the previous section.
 

docs/tools/debug/debugging_mbed_os_apps.md

@@ -1,6 +1,6 @@
 ## Debugging Arm Mbed OS applications
 
-At the heart of Arm Mbed is the [Online Compiler](developing-arm-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.
+At the heart of Arm Mbed is the [Online Compiler](developing-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.
 
 The simplest way to debug your code is to augment your code with log statements, which you can observe from your computer.
 

docs/tools/mbed_targets.md

@@ -2,7 +2,7 @@
 
 Arm Mbed uses JSON as a description language for its build targets. You can find the JSON description of Mbed targets in `targets/targets.json` and in `custom_targets.json` in the root of a project directory. If you provide a source directory using the `--source` switch, Mbed looks for `custom_targets.json` in that directory instead. When you add new targets with `custom_targets.json`, they are added to the list of available targets.
 
-<span class="notes">**Note:** The Online Compiler does not support this functionality. You need to use [Mbed CLI](developing-arm-mbed-cli.html) to take your code offline.</span>
+<span class="notes">**Note:** The Online Compiler does not support this functionality. You need to use [Mbed CLI](developing-mbed-cli.html) to take your code offline.</span>
 
 You are not allowed to redefine existing targets in `custom_targets.json`. To better understand how a target is defined, we'll use this example (taken from `targets.json`):
 

docs/tools/testing/testing_greentea.md

@@ -44,7 +44,7 @@ A test case is named by its position in your project's file structure. For insta
 
 #### Building tests
 
-You can build tests through Arm Mbed CLI. For information on using Mbed CLI, please see the [CLI documentation](developing-arm-mbed-cli.html).
+You can build tests through Arm Mbed CLI. For information on using Mbed CLI, please see the [CLI documentation](developing-mbed-cli.html).
 
 When you build tests for a target and a toolchain, the script first discovers the available tests and then builds them in parallel. You can also create a **test specification** file, which our testing tools can use to run automated hardware tests. For more information on the test specification file, please see the [Greentea documentation](https://github.com/ARMmbed/greentea#test-specification-json-formatted-input).
 

docs/tools/testing/testing_icetea.md

@@ -18,7 +18,7 @@ Test names are defined in the Python scripts themselves. For example, `TEST_APPS
 
 #### Building tests
 
-You can build tests through Arm Mbed CLI. For information on using Mbed CLI, please see the [CLI documentation](developing-arm-mbed-cli.html).
+You can build tests through Arm Mbed CLI. For information on using Mbed CLI, please see the [CLI documentation](developing-mbed-cli.html).
 
 When you build tests for a target and a toolchain, the script discovers the available test cases. The required C++ applications are determined from the available test cases and build in parallel.
 

docs/tools/testing/unit_testing.md

@@ -30,7 +30,7 @@ Detailed instructions for supported operating systems are below.
    sudo easy_install pip
    ```
 
-1. Install Gcovr and [Mbed CLI](developing-arm-mbed-cli.html) with `pip install "gcovr>=4.1" mbed-cli`.
+1. Install Gcovr and [Mbed CLI](developing-mbed-cli.html) with `pip install "gcovr>=4.1" mbed-cli`.
 
 #### Installing dependencies on macOS
 
@@ -43,15 +43,15 @@ Detailed instructions for supported operating systems are below.
    sudo easy_install pip
    ```
 
-1. Install Gcovr and [Mbed CLI](developing-arm-mbed-cli.html) with `pip install "gcovr>=4.1" mbed-cli`.
+1. Install Gcovr and [Mbed CLI](developing-mbed-cli.html) with `pip install "gcovr>=4.1" mbed-cli`.
 
 #### Installing dependencies on Windows
 
 1. Download and install [MinGW-W64](http://mingw-w64.org/).
 1. Download CMake binaries from https://cmake.org/download/, and run the installer.
 1. Download Python 2.7 or Python 3 from https://www.python.org/getit/, and run the installer.
 1. Add MinGW, CMake and Python into system PATH.
-1. Install Gcovr and [Mbed CLI](developing-arm-mbed-cli.html) with `pip install "gcovr>=4.1" mbed-cli`.
+1. Install Gcovr and [Mbed CLI](developing-mbed-cli.html) with `pip install "gcovr>=4.1" mbed-cli`.
 
 ### Test code structure
 
@@ -69,7 +69,7 @@ The build system automatically generates names of test suites. The name is const
 
 ### Unit testing with Mbed CLI
 
-Mbed CLI supports unit tests through `mbed test --unittests` command. To learn how to use unit tests with Mbed CLI, please see the [appropriate documentation section](test-and-debug.html#unit-testing). For other information on using Mbed CLI, please see the [CLI documentation in handbook](developing-arm-mbed-cli.html).
+Mbed CLI supports unit tests through `mbed test --unittests` command. To learn how to use unit tests with Mbed CLI, please see the [appropriate documentation section](test-and-debug.html#unit-testing). For other information on using Mbed CLI, please see the [CLI documentation in handbook](developing-mbed-cli.html).
 
 ### Writing unit tests
 

docs/tools/toolchains/export_to_third_party.md

@@ -35,7 +35,7 @@ The export process generates a ZIP archive with a project file matching your sel
 
 ### Exporting from Arm Mbed CLI
 
-[Mbed CLI](developing-arm-mbed-cli.html) currently supports [exporting](exporting.html#exporting-from-arm-mbed-cli) to all of the development environments mentioned above by using the `export` command.
+[Mbed CLI](developing-mbed-cli.html) currently supports [exporting](exporting.html#exporting-from-arm-mbed-cli) to all of the development environments mentioned above by using the `export` command.
 
 For example, to export to uVision5 with the K64F target, run:
 

docs/tools/tools_intro.md

@@ -15,7 +15,7 @@ We developed Mbed OS 5 using the Mbed CLI tool, which is a Python program that c
 
 ##### Arm Mbed CLI
 
-We created the Mbed command-line tool (Mbed CLI), a Python-based tool, specifically for Mbed OS 5. For more information, see the [Mbed CLI page](developing-arm-mbed-cli.html).
+We created the Mbed command-line tool (Mbed CLI), a Python-based tool, specifically for Mbed OS 5. For more information, see the [Mbed CLI page](developing-mbed-cli.html).
 
 ##### Compiler versions
 
@@ -27,7 +27,7 @@ Mbed OS 5 can be built with various toolchains. The currently supported versions
 
 ##### Arm Mbed Online Compiler
 
-The Mbed Online Compiler is our in-house IDE, and should be familiar to anyone who's been working with Mbed for a while. For more information, see the [Online Compiler page](developing-arm-mbed-online-compiler.html).
+The Mbed Online Compiler is our in-house IDE, and should be familiar to anyone who's been working with Mbed for a while. For more information, see the [Online Compiler page](developing-mbed-online-compiler.html).
 
 ##### Third party development tools
 

docs/tutorials/debug/vs_code.md

@@ -2,7 +2,7 @@
 
 This document explains how to build and debug Arm Mbed OS applications using Visual Studio Code. Before starting, first [configure your local debug toolchain](/docs/development/tools/setting-up-a-local-debug-toolchain.html).
 
-Also install [GNU Make](https://www.gnu.org/software/make/) or [Mbed CLI](/docs/development/tools/developing-arm-mbed-cli.html) to build the project.
+Also install [GNU Make](https://www.gnu.org/software/make/) or [Mbed CLI](/docs/development/tools/developing-mbed-cli.html) to build the project.
 
 ### Installing Visual Studio Code