Bluetooth: add socket & low_energy manifest check

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

Index: chrome/common/extensions/docs/templates/articles/app_bluetooth.html
diff --git a/chrome/common/extensions/docs/templates/articles/app_bluetooth.html b/chrome/common/extensions/docs/templates/articles/app_bluetooth.html
index 822e8855d98e553a3934ea22da6e6feecaea2d75..a3d749e0bbb1ca3a45a1906274f7044dc3aa27e1 100644
--- a/chrome/common/extensions/docs/templates/articles/app_bluetooth.html
+++ b/chrome/common/extensions/docs/templates/articles/app_bluetooth.html
@@ -18,21 +18,41 @@
   For Chrome Apps that use Bluetooth, add the
   <a href="manifest/bluetooth">bluetooth</a> entry to the manifest
   and specify, if appropriate, the UUIDs of profiles, protocols or services
-  you wish to implement.
-  For example:
+  you wish to implement along with whether you wish to implement these with the
+  socket and/or Low Energy APIs.
+</p>
+
+<p>
+  For example for a socket implementation:
+</p>
+
+<pre data-filename="manifest.json">
+"bluetooth": {
+  "uuids": [ "1105", "1106" ],
+  "socket": true
+}
+</pre>
+
+<p>
+  And for a Low Energy implementation:
 </p>
 
 <pre data-filename="manifest.json">
 "bluetooth": {
-  "uuids": [ "1105", "1106" ]
+  "uuids": [ "180D", "1809", "180F" ],
+  "low_energy": true
 }
 </pre>
 
 <p>
   To only access adapter state, discover nearby devices, and obtain basic
-  information about devices, omit the <code>uuids</code> list.
+  information about devices, only the entry itself is required:
 </p>
 
+<pre data-filename="manifest.json">
+"bluetooth": { }
+</pre>
+
 <h2 id="adapter_info">Adapter information</h2>
 
 <h3 id="adapter_state">Obtaining adapter state</h3>