Merge pull request ARMmbed#69 from pan-/improve_documentation

Improve documentation.

Author: pan-

BLE_BatteryLevel/readme.md

@@ -25,9 +25,11 @@ Building instructions for all samples are in the [main readme](https://github.co
 
 1. Build the application and install it on your board as explained in the building instructions.
 1. Open the BLE scanner on your phone.
-1. Find your device.
-1. View the device's characteristics; the exact steps depend on which scanner you're using.
-1. The value of the battery level characteristic should be incrementing as explained above.
+1. Find your device; it should be named `BATTERY`.
+1. Establish a connection with your device.
+1. Discover the services and the characteristics on the device. The *Battery service* has the UUID 0x180F and includes the *Battery level* characteristic which has the UUID 0x2A19.
+1. Register for the notifications sent by the *Battery level* characteristic.
+1. You should see the battery level value change every half second. It begins at 50, goes up to 100 (in steps of 1), resets to 20 and so on.
 
-If you can see the characteristic, and if its value incrementing correctly, the application worked properly.
+If you can see the characteristic, and if its value incrementing correctly, the application is working properly.
 

BLE_Beacon/readme.md

@@ -24,7 +24,7 @@ Building instructions for all samples are in the [main readme](https://github.co
 
 1. Build the application and install it on your board as explained in the building instructions.
 1. Open the BLE scanner on your phone.
-1. Find your device and observe its advertisements (there is no need to connect to the beacon).
+1. Find your device; it should be tagged as an `iBeacon` and observe its advertisements (there is no need to connect to the beacon).
 1. View the beacon's details; the exact steps depend on which scanner you're using.
 
 **Tip:** If you are in an area with many BLE devices, it may be difficult to identify your beacon. The simplest solution is to turn your board off and on, initiate a new scan on your BLE scanner every time, and look for the beacon that appears only when your board is on.

BLE_Button/readme.md

@@ -32,7 +32,7 @@ Building instructions for all samples are in the [main readme](https://github.co
 
 1. Build the application and install it on your board as explained in the building instructions.
 1. Open the BLE scanner on your phone.
-1. Find your device, it should appear with the name `Button` in the scanner.
+1. Find your device; it should appear with the name `Button` in the scanner.
 1. Establish a connection with the device.
 1. Discover the services and the characteristics on the device. The *Button service* has the UUID `0xA000` and includes the *Button state characteristic* which has the UUID `0xA001`.
 1. Register for the notifications sent by the button state characteristic then the scanner will automatically receive a notification containing the new state of the button every time the state of the button changes.

BLE_EddystoneObserver/readme.md

@@ -32,4 +32,4 @@ To see the application's output:
 
 1. Run a terminal program with the correct serial port and the baud rate set to 9600. For example, to use GNU Screen, run: ``screen /dev/tty.usbmodem1412 9600``.
 
-1. The Eddystone Observer should start printing URLs to the terminal.
+1. The Eddystone Observer should start printing URLs of nearby Eddystone beacons to the terminal.

BLE_EddystoneService/readme.md

@@ -1,4 +1,4 @@
-Eddystone beacons broadcast a small amount of information, like URLs, to nearby BLE devices. 
+Eddystone beacons broadcast a small amount of information, like URLs, to nearby BLE devices.
 
 The Eddystone Beacon sample application runs in two stages:
 
@@ -48,8 +48,11 @@ By default, the beacon directs to the url ``http://mbed.org``. You can change th
 
 1. Open the BLE scanner on your phone.
 
-1. Find your device.
+1. Find your device; it should be tagged as `EDDYSTONE CONFIG` while the configuration service is running and it should be tagged as `Eddystone`once the device work as a beacon.
 
-1. Check that the URL is correct.
+1. Once the device operate as a beacon, observe its advertisements packets:
+    * UID frame are used to identify a beacon.
+    * URL frame should report the URL advertised by the beacon.
+    * TLM frames report telemetry informations such as battery level, temperature or the uptime of the beacon.
 
 You can use the [Eddystone Observer](https://github.com/ARMmbed/ble-examples/tree/master/BLE_EddystoneObserver) sample instead of a phone application.

BLE_GAPButton/README.md

@@ -28,7 +28,7 @@ Building instructions for all samples are in the [main readme](https://github.co
 
 1. Open the BLE scanner on your phone.
 
-1. Find your device and look at the advertisement broadcasted by your device (there is no need to connect to your device).
+1. Find your device; it should be named `GAPButton`; and look at the advertisement broadcasted by your device (there is no need to connect to your device).
 
 1. The Service Data field of the advertisement packet broadcasted by your device reflects the button press count. The starting value is 0.
 

BLE_LED/readme.md

@@ -33,7 +33,7 @@ Building instructions for all samples are in the [main readme](https://github.co
 
 1. Build the application and install it on your board as explained in the building instructions.
 1. Open the BLE scanner on your phone.
-1. Find your device.
+1. Find your device; it should be named `LED`.
 1. Find the LED service; its UUID is `0xA000`. The exact instructions to do this depend on the scanner you're using.
 1. Find the LED characteristic; its UUID is `0xA001`. The exact instructions to do this depend on the scanner you're using.
 1. The characteristic accept a 1-bytes value:

BLE_URIBeacon/readme.md

@@ -49,7 +49,7 @@ Checking for Success
 ====================
 
 Your URI beacon should be detectable by BLE scanners (e.g. a smartphone) and by the
-Google Physical Web app.
+Google Physical Web app. By default, the application should point to `http://uribeacon.org`.
 
 **Please note that the URIBeacon spec requires the URIBeacon app to remain in
 config mode for the first 60 seconds before switching to being a beacon. So if