Links and redirects

Author: iriark01

docs/debugging-testing/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](../debug-test/setting-up-a-local-debug-toolchain.html).
 
-Also install [GNU Make](https://www.gnu.org/software/make/) or [Mbed CLI](../build-tools/mbed-cli.html) to build the project.
+Also install [GNU Make](https://www.gnu.org/software/make/) or [Mbed CLI](../build-tools/mbed_cli_1) to build the project.
 
 ## Installing Visual Studio Code
 

docs/debugging-testing/testing/testing_greentea.md

@@ -58,7 +58,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](../build-tools/mbed-cli.html).
+You can build tests through Arm Mbed CLI. For information on using Mbed CLI, please see the [CLI documentation](../build-tools/mbed_cli_1).
 
 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/mbed-os-tools/tree/master/packages/mbed-greentea#test-specification-json-formatted-input).
 

docs/debugging-testing/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](../build-tools/mbed-cli.html) with `pip install "gcovr>=4.1" mbed-cli`.
+1. Install Gcovr and [Mbed CLI](../build-tools/mbed_cli_1) with `pip install "gcovr>=4.1" mbed-cli`.
 
 ### Installing dependencies on macOS
 
@@ -46,7 +46,7 @@ In a terminal window:
    sudo easy_install pip
    ```
 
-1. Install Gcovr and [Mbed CLI](../build-tools/mbed-cli.html) with `pip install "gcovr>=4.1" mbed-cli`.
+1. Install Gcovr and [Mbed CLI](../build-tools/mbed_cli_1) with `pip install "gcovr>=4.1" mbed-cli`.
 1. (Optional) Install GCC with `brew install gcc`.
 
 ### Installing dependencies on Windows
@@ -57,7 +57,7 @@ In a terminal window:
 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](../build-tools/mbed-cli.html) with `pip install "gcovr>=4.1" mbed-cli`.
+1. Install Gcovr and [Mbed CLI](../build-tools/mbed_cli_1) with `pip install "gcovr>=4.1" mbed-cli`.
 
 ## Test code structure
 

docs/introduction/terms.md

@@ -6,7 +6,7 @@
 
 **Application** - An executable software module built out of libraries that acts as a final product.
 
-**Arm Mbed CLI** - The name of the Arm Mbed [command-line tool](../build-tools/mbed-cli.html), packaged as `mbed-cli`.
+**Arm Mbed CLI** - The name of the Arm Mbed [command-line tool](../build-tools/mbed_cli_1), 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`.
 

docs/program-setup/build-profiles-rules/debug_builds_cli.md

@@ -1,6 +1,6 @@
 <h1 id="debug-builds-cli">Debug builds</h1>
 
-After you've set up your [local debug toolchain](../program-setup/build-profiles-and-rules.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](../build-tools/mbed-cli.html).
+After you've set up your [local debug toolchain](../program-setup/build-profiles-and-rules.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](../build-tools/mbed_cli_1).
 
 <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/program-setup/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, in addition to the [scanning rules](../program-setup/build-rules.html).
 
-<span class="notes">**Note:** The Online Compiler does not support this functionality. You need to use [Mbed CLI](../build-tools/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](../build-tools/mbed_cli_1) 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`):
 
@@ -431,5 +431,5 @@ The `orphans` command shows all targets that you cannot reach from a public targ
 ## Related content
 
 - [Defining a PSA-compliant target in targets.json](../program-setup/adding-and-configuring-targets.html#defining-a-psa-compliant-target-in-targets.json).
-- [Developing: Mbed CLI](../build-tools/mbed-cli.html).
+- [Developing: Mbed CLI](../build-tools/mbed_cli_1).
 - [Custom targets in Mbed Studio](https://os.mbed.com/docs/mbed-studio/current/mbed-os/custom-targets.html).

docs/quick-start/cli_setting_up.md

@@ -1,4 +1,4 @@
-<h1 id="cli-setup">Installing Mbed CLI</h1>
+<h1 id="cli-setup">Installing Mbed CLI 1</h1>
 
 The setup process for Arm Mbed CLI depends on your operating system. We recommend using our installers, but have also provided links to manual installation instructions.
 

docs/quick-start/quick-start.md

@@ -8,8 +8,8 @@ The quick start offers two versions of Blinky: the full profile version and the
 
 ## Please choose how to proceed
 
-| [Build with Mbed Studio](https://os.mbed.com/docs/mbed-studio/current/getting-started/index.html) | [Build with Mbed Online Compiler](../quick-start/build-with-the-online-compiler.html) |  [Build with Mbed CLI](../quick-start/build-with-mbed-cli.html) |
+| [Build with Mbed Studio](https://os.mbed.com/docs/mbed-studio/current/getting-started/index.html) | [Build with Mbed Online Compiler](../quick-start/build-with-the-online-compiler.html) |  [Build with Mbed CLI 1](../quick-start/build-with-mbed-cli.html) |
 | --- | --- | --- |
-|Download our dedicated desktop IDE, including all the necessary tools to work with Mbed OS.<br> This link will take you to the Mbed Studio documentation site. | Zero-installation web IDE to explore Mbed OS; great for rapid prototyping and education. | Command-line tool requiring manual setup of tools, but providing the greatest degree of flexibility. |
+|Download our dedicated desktop IDE, including all the necessary tools to work with Mbed OS.<br> This link will take you to the Mbed Studio documentation site. | Zero-installation web IDE to explore Mbed OS; great for rapid prototyping and education. | Command-line tool requiring manual setup, but providing the greatest degree of flexibility. |
 
 Once you have this application working, check the [further reading section](../quick-start/further-reading.html) to add functionality.

docs/tools/mbed_cli_2/use.md

@@ -178,7 +178,7 @@ To perform an iterative build on a previously configured project:
 mbed-tools build
 ```
 
-## List library dependencies of an application
+## List an application's library dependencies
 
 To list all library dependencies with their URL and Git reference:
 

docs/tools/toolchains/export_to_third_party.md

@@ -28,7 +28,7 @@ The export process generates a ZIP archive with a project file matching your sel
 
 ## Exporting from Arm Mbed CLI
 
-[Mbed CLI](../build-tools/mbed-cli.html) currently supports [exporting](../build-tools/third-party-build-tools.html#exporting-from-arm-mbed-cli) to all of the development environments mentioned above by using the `export` command.
+[Mbed CLI](../build-tools/mbed_cli_1) currently supports [exporting](../build-tools/third-party-build-tools.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:
 

redirects.json

@@ -1,6 +1,6 @@
 {
     "reference/mesh-tech.html": "apis/6LoWPAN-ND-tech.html",
-    "tools/developing-arm-mbed-cli.html": "build-tools/mbed-cli.html",
+    "tools/developing-arm-mbed-cli.html": "build-tools/mbed-cli-1.html",
     "tools/windows.html": "build-tools/install-and-set-up.html",
     "tools/macos.html": "build-tools/install-and-set-up.html",
     "tools/linux.html": "build-tools/install-and-set-up.html",
@@ -170,11 +170,12 @@
     "apis/batteryservice.html" : "apis/bluetooth-apis.html",
     "apis/messagebuilder.html" : "apis/nfc-apis.html",
     "reference/using-small-c-libraries.html" : "bare-metal/using-small-c-libraries.html",
-    "tools/developing-mbed-cli.html" :  "build-tools/mbed-cli.html",
+    "tools/developing-mbed-cli.html" :  "build-tools/mbed-cli-1.html",
     "apis/using-mbed-tls-to-communicate-securely.html" : "apis/tls-tutorial.html",
     "introduction/how-we-release-arm-mbed-os.html" : "introduction/versions-and-releases.html",
     "apis/quadspi.html" : "apis/spi-apis.html",
     "apis/mesh.html" : "apis/mesh-api.html",
     "apis/dns.html" : "apis/dns-apis.html",
-    "porting/psa-compliance-port.html" : "porting/porting-security.html"
+    "porting/psa-compliance-port.html" : "porting/porting-security.html",
+    "build-tools/mbed-cli.html" : "build-tools/mbed-cli-1.html"
 }