Fixed README.

README.md

@@ -40,7 +40,7 @@ You can pass other types then just strings using the `field:=value` notation. It
 
 Produces the following JSON request:
 
-{"bool": true, "list": [1, 2, 3], "object": {"a": "b", "c": "d"}}
+    {"bool": true, "list": [1, 2, 3], "object": {"a": "b", "c": "d"}}
 
 You can use the `--form` flag to set `Content-Type` and serialize the data as `application/x-www-form-urlencoded`.
 
@@ -50,22 +50,22 @@ The data to be sent can also be passed via `stdin`:
 
 Most of the flags mirror the arguments you would use with `requests.request`. See `http -h`:
 
-usage: http [-h] [--json | --form] [--traceback] [--ugly] [--headers | --body]
+    usage: http [-h] [--json | --form] [--traceback] [--ugly] [--headers | --body]
                 [--request] [--style STYLE] [--auth AUTH] [--verify VERIFY]
                 [--proxy PROXY] [--allow-redirects] [--file PATH]
                 [--timeout TIMEOUT]
                 method URL [item [item ...]]
 
-HTTPie - cURL for humans.
+    HTTPie - cURL for humans.
 
-positional arguments:
+    positional arguments:
       method                HTTP method to be used for the request (GET, POST,
                             PUT, DELETE, PATCH, ...).
       URL                   Protocol defaults to http:// if the URL does not
                             include it.
       item                  HTTP header (key:value) or data field (key=value)
 
-optional arguments:
+    optional arguments:
       -h, --help            show this help message and exit
       --json, -j            Serialize data items as a JSON object and set Content-
                             Type to application/json, if not specified.