From 135c366f6223ecec4f7980ef3cf82c265db2b041 Mon Sep 17 00:00:00 2001
From: Tom Willemse
Date: Sat, 12 Apr 2014 13:46:30 +0200
Subject: Update README

---
 README.org | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/README.org b/README.org
index cf3227f..dd9a4da 100644
--- a/README.org
+++ b/README.org
@@ -33,23 +33,23 @@
     executable, or a script running this program (passing along all
     arguments).
 
-*** Usage
+** Usage
 
-    When used as a git ~commit-msg~ hook it should just be a question of
-    getting it in the right place and it'll work. If, however, you
-    have another use for it and need to run it manually, there are
-    some command-line options that you can use:
+   When used as a git ~commit-msg~ hook it should just be a question of
+   getting it in the right place and it'll work. If, however, you
+   have another use for it and need to run it manually, there are
+   some command-line options that you can use:
 
-    - =-h= :: Show a short help message to help you along.
-    - =-0= :: Always exit with a ~0~ exit status.
+   - =-h= :: Show a short help message to help you along.
+   - =-0= :: Always exit with a ~0~ exit status.
 
-    Some tools, such as the before-mentioned Flycheck, don't like it
-    when the back-end tool exits with a non-zero exit status and think
-    that means that the tool failed to run. To keep such tools happy
-    the =-0= can be used.
+   Some tools, such as the before-mentioned Flycheck, don't like it
+   when the back-end tool exits with a non-zero exit status and think
+   that means that the tool failed to run. To keep such tools happy
+   the =-0= can be used.
 
-    commit check expects the file to check as the last argument on the
-    command line (or actually, the first non-option argument).
+   commit check expects the file to check as the last argument on the
+   command line (or actually, the first non-option argument).
 
 ** License
 
-- 
cgit v1.2.3-54-g00ecf