Change 5.6 to 5.7

Update sections that weren't affected last time.

Author: AnotherButler

docs/reference/configuration/configuration.md

@@ -6,7 +6,7 @@ Mbed OS provides some default memory configurations for thread memory allocation
 
 #### Configuring the main thread stack
 
-The default stack size of the main application thread is 4 kilobytes. This memory is dynamically allocated from the global heap. You can configure the stack size of the main thread by using the <a href="/docs/v5.6/tools/index.html#the-configuration-system" target="_blank">Mbed config system</a>. To reduce the stack size from 4K to 2K, create an `mbed_app.json` file for your project with the following content:
+The default stack size of the main application thread is 4 kilobytes. This memory is dynamically allocated from the global heap. You can configure the stack size of the main thread by using the <a href="/docs/v5.7/tools/index.html#the-configuration-system" target="_blank">Mbed config system</a>. To reduce the stack size from 4K to 2K, create an `mbed_app.json` file for your project with the following content:
 
 ```JSON
 {
@@ -20,7 +20,7 @@ The default stack size of the main application thread is 4 kilobytes. This memor
 
 #### Configuring user spawned thread stacks
 
-The default stack size of a user spawned thread is 4 kilobytes. You can configure the stack size of user spawned threads by using the <a href="/docs/v5.6/tools/index.html#the-configuration-system" target="_blank">Mbed config system</a> or passing in the <a href="/docs/v5.6/reference/thread.html" target="_blank">Thread constructor</a>. You can reduce the default stack size for user spawned threads from 4K to 2K in the following two ways:
+The default stack size of a user spawned thread is 4 kilobytes. You can configure the stack size of user spawned threads by using the <a href="/docs/v5.7/tools/index.html#the-configuration-system" target="_blank">Mbed config system</a> or passing in the <a href="/docs/v5.7/reference/thread.html" target="_blank">Thread constructor</a>. You can reduce the default stack size for user spawned threads from 4K to 2K in the following two ways:
 
 1. Create an `mbed_app.json` file for your project with the following content:
 
@@ -38,7 +38,7 @@ The default stack size of a user spawned thread is 4 kilobytes. You can configur
 
     `Thread thread(osPriorityNormal, 2000);`
 
-By default, mbed OS dynamically allocates the memory for the thread's stack from the global heap, though you can change it in the <a href="/docs/v5.6/reference/thread.html" target="_blank">Thread constructor</a>. Here is an example application that uses memory allocated from the main thread's stack for the newly spawned thread stack:
+By default, mbed OS dynamically allocates the memory for the thread's stack from the global heap, though you can change it in the <a href="/docs/v5.7/reference/thread.html" target="_blank">Thread constructor</a>. Here is an example application that uses memory allocated from the main thread's stack for the newly spawned thread stack:
 
 ```
 int main() {

docs/reference/contributing/connectivity/CellularInterface.md

@@ -182,7 +182,7 @@ Only valid when **Case 4** is applicable.
 
 Only valid when **Case 1** is applicable.
 
-- This is the most complex case - the bulk of the work is implementing the <a href="/docs/v5.6/reference/network-socket-overview.html" target="_blank">NSAPI socket and network interfaces</a>. The driver implementation derives from `CellularBase` to provide both the `NetworkInterface API` and the standard cellular API. Further layering to abstract connection type may be appropriate, as for the PPP case.
+- This is the most complex case - the bulk of the work is implementing the <a href="/docs/v5.7/reference/network-socket-overview.html" target="_blank">NSAPI socket and network interfaces</a>. The driver implementation derives from `CellularBase` to provide both the `NetworkInterface API` and the standard cellular API. Further layering to abstract connection type may be appropriate, as for the PPP case.
 
 - Use a file handle, such as `UARTSerial`, to provide the raw data connection; then you can use `ATCmdParser` to handle connection logic and the data flow of the socket API, assuming that you use AT commands to control the sockets.
 
@@ -210,4 +210,4 @@ Once you have your target and driver port ready, you can verify your implementat
  	mbed test -n YOUR_TEST_SUITE_NAME
  	```
 
-For more information on the  `mbed-greentea` testing suite, please visit <a href="/docs/v5.6/tools/greentea.html" target="_blank">its documentation</a>.
+For more information on the  `mbed-greentea` testing suite, please visit <a href="/docs/v5.7/tools/greentea.html" target="_blank">its documentation</a>.

docs/reference/contributing/connectivity/MeshInterface.md

@@ -12,7 +12,7 @@ The Mbed OS port of Nanostack consist of a few helper modules that provide easie
 
 ![Nanostack inside Mbed OS](https://s3-us-west-2.amazonaws.com/mbed-os-docs-images/nanostack_in_mbed_OS.png)
 
-- <a href="/docs/v5.6/reference/mesh.html" target="_blank">Mbed Mesh API</a> controls and initializes Nanostack on Mbed OS.
+- <a href="/docs/v5.7/reference/mesh.html" target="_blank">Mbed Mesh API</a> controls and initializes Nanostack on Mbed OS.
     - Security settings.
     - Channel configuration.
     - Connection and reconnection logic.
@@ -32,7 +32,7 @@ In Mbed OS, Socket API hides the differences between the networking stacks. User
 
 For an example of a simple application using Nanostack, see <a href="https://github.com/ARMmbed/mbed-os-example-mesh-minimal" target="_blank">Example mesh application for Mbed OS</a>.
 
-For more information, see the <a href="/docs/v5.6/reference/network-socket-overview.html" target="_blank">documentation of the Socket API</a>.
+For more information, see the <a href="/docs/v5.7/reference/network-socket-overview.html" target="_blank">documentation of the Socket API</a>.
 
 ##### Providing RF driver for Mbed OS applications
 

docs/reference/contributing/connectivity/NetworkStack.md

@@ -4,11 +4,11 @@ The Network-Socket-API (NSAPI) provides a TCP/UDP API on top of any IP based net
 
 #### Class hierarchy
 
-All network-socket API implementations inherit from two classes: a [NetworkStack](https://os.mbed.com/docs/v5.6/mbed-os-api-doxy/class_network_stack.html) and a communication specific subclass of [NetworkInterface](https://os.mbed.com/docs/v5.6/mbed-os-api-doxy/class_network_interface.html).
+All network-socket API implementations inherit from two classes: a [NetworkStack](https://os.mbed.com/docs/v5.7/mbed-os-api-doxy/class_network_stack.html) and a communication specific subclass of [NetworkInterface](https://os.mbed.com/docs/v5.7/mbed-os-api-doxy/class_network_interface.html).
 
 ##### NetworkInterface Class
 
-The current NetworkInterface subclasses are [CellularInterface](https://os.mbed.com/docs/v5.6/mbed-os-api-doxy/class_cellular_interface.html), [EthernetInterface](https://os.mbed.com/docs/v5.6/mbed-os-api-doxy/class_ethernet_interface.html), [MeshInterface](https://os.mbed.com/docs/v5.6/mbed-os-api-doxy/class_mesh_interface.html) and [WiFiInterface](https://os.mbed.com/docs/v5.6/mbed-os-api-doxy/class_wi_fi_interface.html). Your communication interface is a subclass of one of these, as well as the NetworkStack. For example, the [ESP8266Interface](https://github.com/ARMmbed/esp8266-driver) inheritance structure looks like this:
+The current NetworkInterface subclasses are [CellularInterface](https://os.mbed.com/docs/v5.7/mbed-os-api-doxy/class_cellular_interface.html), [EthernetInterface](https://os.mbed.com/docs/v5.7/mbed-os-api-doxy/class_ethernet_interface.html), [MeshInterface](https://os.mbed.com/docs/v5.7/mbed-os-api-doxy/class_mesh_interface.html) and [WiFiInterface](https://os.mbed.com/docs/v5.7/mbed-os-api-doxy/class_wi_fi_interface.html). Your communication interface is a subclass of one of these, as well as the NetworkStack. For example, the [ESP8266Interface](https://github.com/ARMmbed/esp8266-driver) inheritance structure looks like this:
 
 ![Class](/img/esp-class.png)
 
@@ -23,7 +23,7 @@ Each subclass has distinct pure virtual methods. Visit their class references (l
 
 `NetworkStack` provides a common interface that hardware shares. By implementing the NetworkStack, you can use a class as a target for instantiating network sockets.
 
-`NetworkStack` provides [these functions](https://os.mbed.com/docs/v5.6/mbed-os-api-doxy/class_network_stack.html). Look for the function signature like [`declarator virt-specifier(optional) = 0`](http://en.cppreference.com/w/cpp/language/abstract_class) to determine which functions are pure virtual and which you must override in your child class.
+`NetworkStack` provides [these functions](https://os.mbed.com/docs/v5.7/mbed-os-api-doxy/class_network_stack.html). Look for the function signature like [`declarator virt-specifier(optional) = 0`](http://en.cppreference.com/w/cpp/language/abstract_class) to determine which functions are pure virtual and which you must override in your child class.
 
 #### Errors
 

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 <a href="/docs/v5.6/reference/guidelines.html#style" target="_blank">contributing code</a> for style and ABI requirements.
+Please see the contributing guide's section on <a href="/docs/v5.7/reference/guidelines.html#style" target="_blank">contributing code</a> 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 <a href="/docs/v5.6/reference/guidelines.html#style" target="_blank">Mbed style guide</a>.
+Please refer to the <a href="/docs/v5.7/reference/guidelines.html#style" target="_blank">Mbed style guide</a>.
 
 #### Organization
 
@@ -56,7 +56,7 @@ The Arm Mbed OS codebase is organized into conceptual submodules to limit the sc
 - Special directories should follow consistent naming convention.
 
 #### Contribution
-1. Please refer to the <a href="/docs/v5.6/reference/contributing-overview.html" target="_blank">Mbed contribution guide</a>.
+1. Please refer to the <a href="/docs/v5.7/reference/contributing-overview.html" target="_blank">Mbed contribution guide</a>.
 1. Each pull request should serve a single purpose.
 1. The code must compile every commit.
 1. Commit message should be prefixed with the submodule name and a colon:
@@ -174,7 +174,7 @@ A general module can be split into two APIs, the frontend (or user API) and the
 - Tests included in the codebase must be compatible with the Mbed OS test framework.
 - To avoid regressions, every bug fix should include an additional test case that identifies the bug and deterministically fails before the bug is fixed.
 
-<a href="/docs/v5.6/tools/test-and-debug.html" target="_blank">Full documentation</a>.
+<a href="/docs/v5.7/tools/test-and-debug.html" target="_blank">Full documentation</a>.
 
 #### Configuration
 
@@ -188,4 +188,4 @@ Mbed OS provides a powerful configuration system for application development. Ho
 - Targets and applications should be able to override each configuration.
 - The default choice of optimization should be size, on all platforms.
 
-<a href="/docs/v5.6/tools/the-configuration-system.html" target="_blank">Full documentation</a>.
+<a href="/docs/v5.7/tools/the-configuration-system.html" target="_blank">Full documentation</a>.

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 <a href="/docs/v5.6/reference/guidelines.html#cla" target="_blank">CLA</a> and <a href="/docs/v5.6/reference/guidelines.html#workflow" target="_blank">workflow</a> sections for a review of the process and legal requirements.</span>
+<span class="tips">**Tip:** Please also read the <a href="/docs/v5.7/reference/guidelines.html#cla" target="_blank">CLA</a> and <a href="/docs/v5.7/reference/guidelines.html#workflow" target="_blank">workflow</a> sections for a review of the process and legal requirements.</span>
 
 #### Code acceptance
 
-<a href="/docs/v5.6/reference/guidelines.html#cla" target="_blank">After the CLA</a> 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.
+<a href="/docs/v5.7/reference/guidelines.html#cla" target="_blank">After the CLA</a> 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

@@ -2,7 +2,7 @@
 
 #### Contributions
 
-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](#contributing-new-features-to-mbed-os) and [bugs](#reporting-and-fixing-bugs). In both cases, please follow the <a href="/docs/v5.6/reference/guidelines.html#style" target="_blank">code style guide and GitHub pull request guidelines</a>. Please also read the <a href="/docs/v5.6/reference/guidelines.html#cla" target="_blank">CLA</a> 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](#contributing-new-features-to-mbed-os) and [bugs](#reporting-and-fixing-bugs). In both cases, please follow the <a href="/docs/v5.7/reference/guidelines.html#style" target="_blank">code style guide and GitHub pull request guidelines</a>. Please also read the <a href="/docs/v5.7/reference/guidelines.html#cla" target="_blank">CLA</a> guidelines because we will immediately close pull requests submitted without a CLA.
 
 #### Contributing new features to Mbed OS
 
@@ -22,15 +22,15 @@ All Mbed OS is on GitHub; please use GitHub's <a href="https://guides.github.com
 
 ##### Bug fixes
 
-Please refer to the <a href="/docs/v5.6/reference/guidelines.html#style" target="_blank">code contributions chapter</a>.
+Please refer to the <a href="/docs/v5.7/reference/guidelines.html#style" target="_blank">code contributions chapter</a>.
 
 A member of the Mbed team must verify bug fixes before we pull the fixes into the main branch. You must therefore use GitHub to fork the repo and then submit a pull request with your changes.
 
 The last line in your commit message description should say “Fixes #deadbeef”, where “deadbeef” is the issue number in GitHub. This allows GitHub to automatically close the issue when the commit is merged into the default branch.
 
 #### Further reading
 
-Please see the <a href="/docs/v5.6/reference/guidelines.html#style" target="_blank">code contributions chapter</a> for the guidelines to GitHub pull requests and the coding style guide.
+Please see the <a href="/docs/v5.7/reference/guidelines.html#style" target="_blank">code contributions chapter</a> for the guidelines to GitHub pull requests and the coding style guide.
 
 #### Guidelines for GitHub pull requests
 

docs/reference/contributing/storage/BlockDevice.md

@@ -4,7 +4,7 @@
 
 #### BlockDevice class reference
 
-[![View code](https://www.mbed.com/embed/?type=library)](https://os.mbed.com/docs/v5.6/mbed-os-api-doxy/class_block_device.html)
+[![View code](https://www.mbed.com/embed/?type=library)](https://os.mbed.com/docs/v5.7/mbed-os-api-doxy/class_block_device.html)
 
 <a href="https://github.com/ARMmbed/mbed-os/blob/master/features/filesystem/bd/BlockDevice.h" target="_blank">C++ API Reference</a>
 

docs/reference/contributing/storage/FileSystem.md

@@ -4,7 +4,7 @@
 
 #### File system class reference
 
-[![View code](https://www.mbed.com/embed/?type=library)](https://os.mbed.com/docs/v5.6/mbed-os-api-doxy/classmbed_1_1_file_system.html)
+[![View code](https://www.mbed.com/embed/?type=library)](https://os.mbed.com/docs/v5.7/mbed-os-api-doxy/classmbed_1_1_file_system.html)
 
 #### Assumptions
 

docs/reference/contributing/target/entropy.md

@@ -134,7 +134,7 @@ Both of the above options are secure if done properly, and depending on the plat
 
 This option is very dangerous because compiling with it results in a build that is not secure! You have to let Mbed TLS know that you are using it deliberately and you are aware of the consequences. That is why you have to turn off any entropy sources explicitly first.
 
-Because it is a very dangerous option and no one should use it in production, we recommend you limit its scope as much as possible; you should apply these settings to the application specific configuration file, instead of the target related configuration as we did it above. You can read more about <a href="/docs/v5.6/tools/adding-and-configuring-targets.html" target="_blank">how to add a macro for your application</a>.
+Because it is a very dangerous option and no one should use it in production, we recommend you limit its scope as much as possible; you should apply these settings to the application specific configuration file, instead of the target related configuration as we did it above. You can read more about <a href="/docs/v5.7/tools/adding-and-configuring-targets.html" target="_blank">how to add a macro for your application</a>.
 
 To turn the unsafe testing mode on:
 

docs/reference/contributing/target/exporter.md

@@ -20,7 +20,7 @@ You can open the generated `.creator` project in Qt Creator, enabling integratio
 
 #### CMSIS Packs
 
-uVision and IAR both use <a href="http://www.keil.com/pack/doc/CMSIS/Pack/html/index.html" target="_blank">CMSIS packs</a> to find target information necessary to create a valid project file. Add a `"device_name"` attribute to your target as <a href="https://os.mbed.com/docs/v5.6/tools/adding-and-configuring-targets.html" target="_blank">Adding and configuring targets</a> describes to support these exporters.
+uVision and IAR both use <a href="http://www.keil.com/pack/doc/CMSIS/Pack/html/index.html" target="_blank">CMSIS packs</a> to find target information necessary to create a valid project file. Add a `"device_name"` attribute to your target as <a href="https://os.mbed.com/docs/v5.7/tools/adding-and-configuring-targets.html" target="_blank">Adding and configuring targets</a> describes to support these exporters.
 
 #### uVision
 <a href="https://github.com/ARMmbed/mbed-os/blob/master/tools/export/uvision/uvision.tmpl#L15" target="_blank">uVision project file template</a> uses target information from CMSIS Packs to generate valid uVision5 projects. If the uVision exporter cannot find the `"device_name"`, it substitutes a generic Arm CPU target.

docs/reference/contributing/target/flash.md

@@ -61,7 +61,7 @@ Bootloader-ready declaration of flash VTOR address:
 
 #### `targets.json` metadata
 
-The managed and unmanaged bootloader builds require some target metadata from CMSIS Packs. Add a `"device_name"` attribute to your target as <a href="https://os.mbed.com/docs/v5.6/tools/adding-and-configuring-targets.html" target="_blank">Adding and configuring targets</a> describes.
+The managed and unmanaged bootloader builds require some target metadata from CMSIS Packs. Add a `"device_name"` attribute to your target as <a href="https://os.mbed.com/docs/v5.7/tools/adding-and-configuring-targets.html" target="_blank">Adding and configuring targets</a> describes.
 
 #### Start application