[06/18] storm git commit: README formatting

[pt...@apache.org]

README formatting


Project: http://git-wip-us.apache.org/repos/asf/storm/repo
Commit: http://git-wip-us.apache.org/repos/asf/storm/commit/4b613083
Tree: http://git-wip-us.apache.org/repos/asf/storm/tree/4b613083
Diff: http://git-wip-us.apache.org/repos/asf/storm/diff/4b613083

Branch: refs/heads/1.x-branch
Commit: 4b61308349d8c66d48234de22190fe721aa0e621
Parents: d88d551
Author: P. Taylor Goetz <pt...@gmail.com>
Authored: Fri Jan 8 00:31:16 2016 -0500
Committer: P. Taylor Goetz <pt...@gmail.com>
Committed: Fri Jan 8 00:31:16 2016 -0500

----------------------------------------------------------------------
 external/storm-mqtt/README.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/storm/blob/4b613083/external/storm-mqtt/README.md
----------------------------------------------------------------------
diff --git a/external/storm-mqtt/README.md b/external/storm-mqtt/README.md
index 7c6bf4a..a67aa3c 100644
--- a/external/storm-mqtt/README.md
+++ b/external/storm-mqtt/README.md
@@ -77,9 +77,9 @@ well as the MQTT spout.
 
 The MQTT protocol defines the following QoS levels:
 
-`0` - At Most Once (AKA "Fire and Forget")
-`1` - At Least Once
-`2` - Exactly Once
+* `0` - At Most Once (AKA "Fire and Forget")
+* `1` - At Least Once
+* `2` - Exactly Once
 
 This can be a little confusing as the MQTT protocol specification does not really address the concept of a node being 
 completely incinerated by a catasrophic event. This is in stark contrast with Storm's reliability model, which expects 
@@ -87,7 +87,8 @@ and embraces the concept of node failure.
 
 So resiliancy is ultimately dependent on the underlying MQTT implementation and infrastructure.
 
-**Recommendations**
+###Recommendations
+
 *You will never get at exactly once processing with this spout. It can be used with Trident, but it won't provide 
 transational semantics.*