current > latest

We'll be killing current at some point, and latest already works. Better safe than sorry?

Author: iriark01

docs/pelion_ready/device-management-test.md

@@ -69,7 +69,7 @@ Mbed Device Management tests rely on the Python SDK to test the end-to-end solut
     $ mbed config -G CLOUD_SDK_API_KEY <API_KEY>
     ```
 
-    For instructions on how to generate an API key, please [see the documentation](https://cloud.mbed.com/docs/current/integrate-web-app/api-keys.html#generating-an-api-key).
+    For instructions on how to generate an API key, please [see the documentation](https://cloud.mbed.com/docs/latest/integrate-web-app/api-keys.html#generating-an-api-key).
 
 1. Initialize your Pelion DM credentials (once per project):
 

docs/pelion_ready/device-management.md

@@ -10,7 +10,7 @@ It:
 - Helps users avoid doing blocking network operations in interrupt contexts, by automatically defering actions to a separate thread.
 - Provides end-to-end Greentea tests for Pelion Device Management.
 
-This library makes it trivial to expose sensors, actuators and other variables to a cloud service. For a complete Pelion Device Management Client API, please see our [documentation](https://cloud.mbed.com/docs/current/mbed-cloud-client/index.html).
+This library makes it trivial to expose sensors, actuators and other variables to a cloud service. For a complete Pelion Device Management Client API, please see our [documentation](https://cloud.mbed.com/docs/latest/mbed-cloud-client/index.html).
 
 ### Device management for your Mbed OS application
 

docs/porting/porting_full_process/demo_testing.md

@@ -60,8 +60,8 @@ Then, test connectivity and firmware update:
 
 1. Application repository:[https://github.com/armmbed/mbed-cloud-client-example](https://github.com/armmbed/mbed-cloud-client-example).
     1. Again, if you have not merged your target into `mbed-os` you will need to add your fork.
-1. [Set up a Pelion Device Management account](https://cloud.mbed.com/docs/current/account-management/users.html).
-1. [Generate an API key](https://cloud.mbed.com/docs/current/integrate-web-app/api-keys.html) from the [Device Management Portal](https://portal.mbedcloud.com//login).
+1. [Set up a Pelion Device Management account](https://cloud.mbed.com/docs/latest/account-management/users.html).
+1. [Generate an API key](https://cloud.mbed.com/docs/latest/integrate-web-app/api-keys.html) from the [Device Management Portal](https://portal.mbedcloud.com//login).
 1. In the `mbed-cloud-client-example` clone on your machine, run the following command with the generated API key:
 
    ```

docs/porting/target/bootloader.md

@@ -8,9 +8,9 @@ The target needs to support the Flash HAL API. You can find the guide to porting
 
 ### Porting the bootloader
 
-You can learn to port the Update Client bootloader to new targets in [the porting guide](https://cloud.mbed.com/docs/current/porting/porting-the-device-management-update-client.html).
+You can learn to port the Update Client bootloader to new targets in [the porting guide](https://cloud.mbed.com/docs/latest/porting/porting-the-device-management-update-client.html).
 
-An example walkthrough of porting the bootloader to the K64F platform can be found [here](https://cloud.mbed.com/docs/current/porting/update-k64f-port.html).
+An example walkthrough of porting the bootloader to the K64F platform can be found [here](https://cloud.mbed.com/docs/latest/porting/update-k64f-port.html).
 
 ### Creating and using a new bootloader
 

docs/reference/configuration/Storage.md

@@ -422,7 +422,7 @@ Name: nvstore.max_keys
 
 The Mbed OS configuration allows you to add block devices as components using the `targets.json` file or target overrides in the application configuration file.
 
-When [one of the following components](https://cloud.mbed.com/docs/current/connecting/mbed-os-storage-configuration.html) is enabled, a default block device is set in the system ("components": ["xxx","yyy"]):
+When [one of the following components](https://cloud.mbed.com/docs/latest/connecting/mbed-os-storage-configuration.html) is enabled, a default block device is set in the system ("components": ["xxx","yyy"]):
 
 1. SPIF
 1. QSPIF

docs/reference/technology/firmware_update.md

@@ -12,7 +12,7 @@ Update support in Mbed OS relies on two features:
 The active firmware, made up of Mbed OS and an application, can be updated only if the binary installed on the device has:
 
 1. A bootloader, as [reviewed below](#the-mbed-os-bootloader). The bootloader can load a new version of the firmware. If for some reason, the update fails, the bootloader falls back to the firmware version last known to work. As a security feature, the default behavior of the bootloader is to refuse to roll back to old firmware versions once an update succeeds.
-1. Mbed OS with the Device Management Client (which includes the Update client). The clients allow your device to communicate with the Device Management Update service, receive update manifests and firmware, and verify the binary's validity. They are [reviewed in details in our Pelion Device Management documentation](https://cloud.mbed.com/docs/current/updating-firmware/index.html).
+1. Mbed OS with the Device Management Client (which includes the Update client). The clients allow your device to communicate with the Device Management Update service, receive update manifests and firmware, and verify the binary's validity. They are [reviewed in details in our Pelion Device Management documentation](https://cloud.mbed.com/docs/latest/updating-firmware/index.html).
 
     Note: Because some embedded devices don't require remote update capabilities, Mbed OS does not include the Device Management Client by default; you need to explicitly import the client to your application.
 
@@ -62,7 +62,7 @@ Note two things about the Mbed OS bootloader's design:
 1. It does not process encrypted off-chip candidate images.
 1. It does not currently verify signatures of candidate images. To save code size and speed up boot time, we use a unique, per-device Message Authentication Code (MAC) to authenticate the firmware in the bootloader: firmware is distributed with a signature, and the Update client verifies the signature and replaces it with a MAC that the bootloader understands.
 
-This means that the default bootloader does not implement secure boot; for high-security applications, further implementation is required. Please see [the full bootloader documentation](https://cloud.mbed.com/docs/latest/updating-firmware/bootloaders.html) and the [porting section](https://cloud.mbed.com/docs/current/porting/porting-the-device-management-update-client.html) on the Pelion Device Management site.
+This means that the default bootloader does not implement secure boot; for high-security applications, further implementation is required. Please see [the full bootloader documentation](https://cloud.mbed.com/docs/latest/updating-firmware/bootloaders.html) and the [porting section](https://cloud.mbed.com/docs/latest/porting/porting-the-device-management-update-client.html) on the Pelion Device Management site.
 
 ### Managing updates with the bootloader
 

docs/tools/CLI/cli-device-management.md

@@ -1,6 +1,6 @@
 <h2 id="cli-update">Updating devices</h2>
 
-Arm Mbed OS allows you to update your device firmware, enabled by the Pelion Device Management IoT platform. Mbed CLI includes features to prepare and ship updates for devices managed through the [Device Management Portal](https://cloud.mbed.com/docs/current/introduction/index.html).
+Arm Mbed OS allows you to update your device firmware, enabled by the Pelion Device Management IoT platform. Mbed CLI includes features to prepare and ship updates for devices managed through the [Device Management Portal](https://cloud.mbed.com/docs/latest/introduction/index.html).
 
 Mbed CLI provides the subcommand `mbed device-management` to manage devices (`mbed dev-mgmt` and `mbed dm` are also available as shorter aliases). The remainder of this document uses the `mbed dm` alias for all device management subcommands. This document explains the steps to enable and use Device Management with a project.
 
@@ -10,11 +10,11 @@ Mbed CLI provides the subcommand `mbed device-management` to manage devices (`mb
 
 To use the `mbed dm` command to update a device, your device must be running an application with Device Management Client and a supported managed or unmanaged bootloader.
 
-This command only works for devices running Device Management Client, and the application is combined with a bootloader. To test this feature, you can run the [Device Management Client Example](https://github.com/ARMmbed/mbed-cloud-client-example) or [using our tutorials](https://cloud.mbed.com/docs/current/connecting/device-management-client-tutorials.html) on one of our reference platforms.
+This command only works for devices running Device Management Client, and the application is combined with a bootloader. To test this feature, you can run the [Device Management Client Example](https://github.com/ARMmbed/mbed-cloud-client-example) or [using our tutorials](https://cloud.mbed.com/docs/latest/connecting/device-management-client-tutorials.html) on one of our reference platforms.
 
 ### Project setup
 
-Configure your Mbed Cloud SDK API key, target and toolchain. [Obtain the API key](https://cloud.mbed.com/docs/current/integrate-web-app/api-keys.html) from the the Device Management Portal.
+Configure your Mbed Cloud SDK API key, target and toolchain. [Obtain the API key](https://cloud.mbed.com/docs/latest/integrate-web-app/api-keys.html) from the the Device Management Portal.
 
 ```
 $ mbed config -G CLOUD_SDK_API_KEY <API_KEY>
@@ -92,8 +92,8 @@ $ mbed dm update prepare -n <PAYLOAD_NAME> -d <PAYLOAD_DESCRIPTION>\
 
 Both methods of creating a manifest use the defaults created in `mbed dm init`. You can override each default using an input file or command-line arguments.
 
-Once you execute `mbed dm update prepare`, Mbed CLI automatically uploads the payload and manifest to Device Management, and you can then create and start an [update campaign](https://cloud.mbed.com/docs/current/updating-firmware/update-campaigns.html) using the Device Management Portal.
+Once you execute `mbed dm update prepare`, Mbed CLI automatically uploads the payload and manifest to Device Management, and you can then create and start an [update campaign](https://cloud.mbed.com/docs/latest/updating-firmware/update-campaigns.html) using the Device Management Portal.
 
 ### Advanced use
 
-Mbed CLI allows for significantly more flexibility than the model above shows in exactly the same way as [the manifest tool](https://cloud.mbed.com/docs/current/updating-firmware/manifest-tool.html). You can override each of the defaults that `mbed dm init` sets by using the command-line or an input file. Mbed CLI supports a variety of commands. You can print a full list of commands by using `manifest-tool --help`.
+Mbed CLI allows for significantly more flexibility than the model above shows in exactly the same way as [the manifest tool](https://cloud.mbed.com/docs/latest/updating-firmware/manifest-tool.html). You can override each of the defaults that `mbed dm init` sets by using the command-line or an input file. Mbed CLI supports a variety of commands. You can print a full list of commands by using `manifest-tool --help`.