Bluetooth: write documentation

chrome/common/extensions/docs/templates/articles/app_serial.html

 <h1>Serial Devices</h1>
 
 <p>
 </p>
 
 <p>
 This document describes how to use the <a href="serial.html">serial API</a> to read
 and write from serial devices. Chrome Apps can also connect to
-<a href="app_usb.html">USB</a> and <a href="bluetooth.html">Bluetooth</a> devices.
+<a href="app_usb.html">USB</a> and <a href="app_bluetooth.html">Bluetooth</a> devices.
 </p>
 
 <p class="note">
 <b>Samples:</b> For examples that illustrate how Chrome Apps can connect to hardware devices through a serial port, see the
 <a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/serial/adkjs#readme">adkjs</a>,
 <a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/serial/ledtoggle#readme">ledtoggle</a> and the
 <a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/servo#readme">servo</a> samples.
 </p>
 
 <h2 id="requirement">Manifest requirement</h2>
@@ skipping 61 matching lines @@
   _this.connectionId = connectionInfo.connectionId;
   // Do whatever you need to do with the opened port.
 }
 // Connect to the serial port /dev/ttyS01
 chrome.serial.connect("/dev/ttyS01", {bitrate: 115200}, onConnect);
 </pre>
 
 <h2 id="disconnect">Disconnect from a serial port</h2>
 
 <p>
-When an app terminates, connections to serial ports that are not persistent 
+When an app terminates, connections to serial ports that are not persistent
 are automatically closed by the platform. However, if you want to disconnect
 while your app is still running, you can use the $ref:serial.disconnect method:
 </p>
 
 <pre>
 var onDisconnect = function(result) {
   if (result) {
     console.log("Disconnected from the serial port");
   } else {
     console.log("Disconnect failed");
   }
 }
 chrome.serial.disconnect(connectionId, onDisconnect);
 </pre>
 
 <h2 id="reading">Reading from a serial port</h2>
 
 <p>
 The serial API reads from the serial port and delivers the read bytes as an ArrayBuffer to event listeners.
 
-Every port that your application is connected to will generate read events to all listeners added through 
+Every port that your application is connected to will generate read events to all listeners added through
 <code>chrome.serial.onReceive.addListener(onReceiveCallback)</code>. If you are connected to more than one port at the
-same time, you may find the corresponding <code>connectionId</code> of an incoming read event in the callback parameter 
+same time, you may find the corresponding <code>connectionId</code> of an incoming read event in the callback parameter
 of $ref:serial.onReceive.
 </p>
 <p>
 The following example can accumulate read bytes until a new line is read, converting the received ArrayBuffer to String and
 calling a method when a newline is found as the last character received:
 </p>
 
 <pre>
 var stringReceived = '';
 
@@ skipping 50 matching lines @@
   chrome.serial.flush(connectionId, onFlush);
 </pre>
 
 <h2 id="More">More</h2>
 
 <p>
 The Serial API has several other features. You can, for example, set a connection to persistent, so it can receive data
 even when your app is not running, or you can update connection parameters on the fly, like bitrate, timeouts, control signals, and many others
  with the $ref:serial.update method. See the full reference of the $ref:serial API for more information.
 </p>