Update README.md

exchange/bitswap/README.md

@@ -1,4 +1,5 @@
-#Welcome to Bitswap (The data trading engine)
+#Welcome to Bitswap
+###(The data trading engine)
 
 Bitswap is the module that is responsible for requesting and providing data
 blocks over the network to and from other ipfs peers. The role of bitswap is
@@ -7,15 +8,15 @@ to be a merchant in the large global marketplace of data.
 ##Main Operations
 Bitswap has three high level operations:
 
-###GetBlocks
-`GetBlocks` is a bitswap method used to request multiple blocks that are likely
+- **GetBlocks**
+  - `GetBlocks` is a bitswap method used to request multiple blocks that are likely
 to all be provided by the same set of peers (part of a single file, for example).
 
-###GetBlock
-`GetBlock` is a special case of `GetBlocks` that just requests a single block.
+- **GetBlock**
+  - `GetBlock` is a special case of `GetBlocks` that just requests a single block.
 
-###HasBlock
-`HasBlock` registers a local block with bitswap. Bitswap will then send that
+- **HasBlock**
+  - `HasBlock` registers a local block with bitswap. Bitswap will then send that
 block to any connected peers who want it (with the strategies approval), record
 that transaction in the ledger and announce to the DHT that the block is being
 provided.
@@ -41,6 +42,6 @@ If another peers wantlist is received, Bitswap will call its strategies
 be sent the block they are requesting (if we even have it).
 
 ##Outstanding TODOs:
-[] Ensure only one request active per key
-[] More involved strategies
-[] Ensure only wanted blocks are counted in ledgers
+- [ ] Ensure only one request active per key
+- [ ] More involved strategies
+- [ ] Ensure only wanted blocks are counted in ledgers