Rewrite CLI options handling and output

README.md

@@ -14,15 +14,13 @@ Basic Example
 In a terminal, run:
 
     huptime --exec python -m SimpleHTTPServer &
-    echo $!
-
-Record the result of the echo, we'll call it $PID.
+    PID=$!
 
 Then, in a second terminal:
 
-    while true; do curl http://localhost:8080 2>/dev/null || echo "fail"; done
+    while true; do curl http://localhost:8000 2>/dev/null || echo "fail"; done
 
-Finally, in a third terminal:
+Finally, in a third terminal (or back in the first):
 
     kill -HUP $PID
 
@@ -37,7 +35,7 @@ Why?
 ----
 
 With continuous deployment, software can be updated dozens, hundreds or even
-thousands of times per day. It critical that service is not interrupted during
+thousands of times per day. It is critical that service is not interrupted during
 upgrades.
 
 In an ideal world, all applications would support a mechanism for doing zero
@@ -50,7 +48,7 @@ Compound this with the fact that many applications consist of many different
 small components (written using different languages and frameworks), and you've
 got yourself a headache.
 
-Because of this complexity, one of first things people have to do is implement
+Because of this complexity, one of the first things people have to do is implement
 a custom load balancing tier and a complex upgrade process. Although this is
 important at a certain scale, it shouldn't be that hard for simple services.
 It's crazy to add a whole new tier when the problem can be solved in a much