Update 6LoWPAN mesh documentation

-Update EUI64 reading in Thread commissioning
-Fix few broken links
-Update Thread application list

Author: Arto Kinnunen

docs/reference/technology/mesh/thread_commissioning.md

@@ -18,7 +18,7 @@ A model network setup could look like this:
 
 #### Building the end node application
 
-By default, the Mbed Thread applications/examples use the static network link configuration defined in the [mesh-api configuration file](https://github.com/ARMmbed/mbed-os/blob/master/features/nanostack/FEATURE_NANOSTACK/mbed-mesh-api/mbed_lib.json). If you want to use the Thread commissioning, add the following lines to your `.json` file. You can use the [mesh-minimal](https://github.com/ARMmbed/mbed-os-example-mesh-minimal) application as an example.
+By default, the Mbed Thread applications/examples use the static network link configuration defined in the [mesh-api configuration file](https://github.com/ARMmbed/mbed-os/blob/master/features/nanostack/mbed-mesh-api/mbed_lib.json). If you want to use the Thread commissioning, add the following lines to your `.json` file. You can use the [mesh-minimal](https://github.com/ARMmbed/mbed-os-example-mesh-minimal) application as an example.
 
 - `"mbed-mesh-api.thread-use-static-link-config": false` under `"target_overrides":`
 - `"macros": ["MBEDTLS_USER_CONFIG_FILE=\"mbedtls_config.h\""]` in to the same level as `"config":` and `"target_overrides":`
@@ -35,14 +35,12 @@ Once the binary is generated, flash the binary to the end device, and run the ap
 
 You can use [a free online tool](http://www.qr-code-generator.com/) to generate a QR code.
 
-In the online tool, fill in the URL field. The following is an example: `v=1&eui=000b57fffe07a8be&cc=PV7TUCB0`. Fill in the correct values for your device, and ensure `v=1` is always present. The other required parameters are:
+In the online tool, fill in the URL field. The following is an example: `v=1&eui=000b57fffe07a8be&cc=ABCDEFGH`. Fill in the correct values for your device, and ensure `v=1` is always present. The other required parameters are:
 
 - `cc` is the PSKd, which is configured in the `.json` file (see the mesh-api configuration). *PSKd must be uppercase characters (0-9, A-Y excluding I,O,Q and Z)*
-- `eui` is equal to the RF MAC address by default.
+- `eui` is equal to the EUI64 address.
 
-To get the MAC address for your end device, connect the node to the Thread network with static configuration enabled. In other words, `"mbed-mesh-api.thread-use-static-link-config": true`, unless you have your own configuration for the MAC address.
-
-For example, in the **mesh-minimal** application, place this `printf("MAC address = %s\n", mesh.get_mac_address());` after `printf("connected. IP = %s\n", mesh.get_ip_address());`
+You can get EUI64 address for your end device by using method `device_eui64_get` in your application. An example can be found from the [mesh-minimal](https://github.com/ARMmbed/mbed-os-example-mesh-minimal).
 
 There are four additional (optional) query parameters you can put into this field:
 

docs/reference/technology/mesh/thread_faq.md

@@ -32,12 +32,11 @@ Ad-hoc networks with devices from different manufacturers can be easily created
 
 An example application is [downloadable from the Android store](https://play.google.com/store/apps/details?id=org.threadgroup.commissioner).
 
-#### Are there any application examples? What are the Thread features supported/not supported by them?
+#### Are there any application examples?
 
-- Application examples supporting SED and REED types:
-  - [Mbed OS Client example](https://github.com/ARMmbed/mbed-os-example-client).
-  - [Mesh minimal example](https://github.com/ARMmbed/mbed-os-example-mesh-minimal).
+- [Mesh minimal example](https://github.com/ARMmbed/mbed-os-example-mesh-minimal).
 - [Thread border router](https://github.com/ARMmbed/nanostack-border-router).
+- [Mbed Cloud client example](https://github.com/ARMmbed/mbed-cloud-client-example)
 
 #### How to debug and visualize the network?
 

docs/reference/technology/mesh/thread_intro.md

@@ -33,10 +33,10 @@ The key elements of Mbed OS are:
 
 Mbed Thread is implemented in the Nanostack library, which also supports the 6LoWPAN protocol. In Mbed OS, the Thread stack runs in its own RTOS thread using an internal event scheduler. Mbed OS provides the [Mesh C++ API](../apis/mesh-api.html) for building Thread applications.
 
-- To connect to the Thread network, use the [Thread interface API](https://github.com/ARMmbed/mbed-os/blob/master/features/nanostack/FEATURE_NANOSTACK/mbed-mesh-api/mbed-mesh-api/ThreadInterface.h).
+- To connect to the Thread network, use the [Mbed Mesh API](../apis/mesh-api.html) or [Thread interface API](https://github.com/ARMmbed/mbed-os/blob/master/features/nanostack/mbed-mesh-api/mbed-mesh-api/ThreadInterface.h).
 - For the socket communication over the Thread network, use the [Mbed sockets API](../apis/network-socket.html).
 
-Nanostack provides a set of C API headers with more functionalities. The [nanostack repository](https://github.com/ARMmbed/mbed-os/tree/master/features/nanostack/FEATURE_NANOSTACK/sal-stack-nanostack/nanostack) has the following header files():
+Nanostack provides a set of C API headers with more functionalities. The [nanostack repository](https://github.com/ARMmbed/mbed-os/tree/master/features/nanostack/sal-stack-nanostack/nanostack) has the following header files():
 
 - `thread_management_if.h` for initializing the stack and managing the network data.
 - `thread_commissioning_api.h` for implementing an on-mesh or a native Thread commissioner.