bluetooth: README.md fixes for gitiles rendering.

device/bluetooth/README.md

 Bluetooth
 =========
 
 `device/bluetooth` abstracts
 [Bluetooth Classic](https://en.wikipedia.org/wiki/Bluetooth) and
 [Low Energy](https://en.wikipedia.org/wiki/Bluetooth_low_energy) features
 across multiple platforms.
 
 Classic and Low Energy based profiles differ substantially. Platform
 implementations may support only one or the other, even though several classes
 have interfaces for both, e.g. `BluetoothAdapter` & `BluetoothDevice`.
 
-  |          | Classic |  Low Energy |
-  |----------|:-------:|:-----------:|
-  | Android  |    no   | in progress |
-  | ChromeOS |   yes   |     yes     |
-  | Linux    |   yes   |     yes     |
-  | Mac OSX  |   yes   | in progress |
-  | Windows  |  some   | in progress |
+|          | Classic |  Low Energy |
+|----------|:-------:|:-----------:|
+| Android  |    no   | in progress |
+| ChromeOS |   yes   |     yes     |
+| Linux    |   yes   |     yes     |
+| Mac OSX  |   yes   | in progress |
+| Windows  |  some   | in progress |
 
 ChromeOS and Linux are supported via BlueZ, see `*_bluez` files.
 
 
---------------------------------------------------------------------------------
 Maintainer History
 --------------------------------------------------------------------------------
 
 Initial implementation OWNERS were youngki@chromium.org, keybuk@chromium.org,
 armansito@chromium.org, and rpaquay@chromium.org. They no longer contribute to
 chromium fulltime. They were responsible for support for ChromeOS Bluetooth
 features and the Chrome Apps APIs:
 
 * [bluetooth](https://developer.chrome.com/apps/bluetooth)
 * [bluetoothLowEnergy](https://developer.chrome.com/apps/bluetoothLowEnergy)
 * [bluetoothSocket](https://developer.chrome.com/apps/bluetoothSocket)
 
 Active development in 2015 & 2016 is focused on enabling GATT features for:
 
 * [Web Bluetooth](https://crbug.com/419413)
 
 Known future work is tracked in the
 [Refactoring meta issue](https://crbug.com/580406).
 
---------------------------------------------------------------------------------
+
 Testing
 --------------------------------------------------------------------------------
 
 Implementation of the Bluetooth component is tested via unittests. Client code
 uses Mock Bluetooth objects:
 
 
 ### Cross Platform Unit Tests
 
 New feature development uses cross platform unit tests. This reduces test code
@@ skipping 31 matching lines @@
 
 ### ChromeOS Blueooth Controller Tests
 
 Bluetooth controller system tests generating radio signals are run and managed
 by the ChromeOS team. See:
 https://chromium.googlesource.com/chromiumos/third_party/autotest/+/master/server/site_tests/
 https://chromium.googlesource.com/chromiumos/third_party/autotest/+/master/server/cros/bluetooth/
 https://chromium.googlesource.com/chromiumos/third_party/autotest/+/master/client/cros/bluetooth/
 
 
---------------------------------------------------------------------------------
 Android
 --------------------------------------------------------------------------------
 
 The android implementation requires crossing from C++ to Java using
 [__JNI__](https://www.chromium.org/developers/design-documents/android-jni).
 
 Object ownership is rooted in the C++ classes, starting with the Adapter, which
 owns Devices, Services, etc. Java counter parts interface with the Android
 Bluetooth objects. E.g.
 
@@ skipping 12 matching lines @@
         * `android/.../ChromeBluetoothDevice.java` uses:
             * `android/.../Wrappers.java`: `BluetoothDeviceWrapper`
                 * Which under test is a `FakeBluetoothDevice`
         * `bluetooth_gatt_service_android.h` owns:
             * `android/.../ChromeBluetoothService.java` uses:
                 * `android/.../Wrappers.java`: `BluetoothServiceWrapper`
                     * Which under test is a `FakeBluetoothService`
             * ... and so on for characteristics and descriptors.
 
 Fake objects are controlled by `bluetooth_test_android.cc`.