From b0429315ec152c8fbf92068a8e231a26f849b0c9 Mon Sep 17 00:00:00 2001
From: Thomas Levine <_@thomaslevine.com>
Date: Wed, 5 Nov 2014 17:47:36 +0000
Subject: [PATCH] urchin -sh to urchin -x

---
 HISTORY   | 4 ++--
 readme.md | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/HISTORY b/HISTORY
index ade78da..7aa0fca 100644
--- a/HISTORY
+++ b/HISTORY
@@ -1,7 +1,7 @@
 HISTORY
 -------
 
-Version 0.0.3
+Version 0.0.4
 ---------------------
 General tidying
 
@@ -9,7 +9,7 @@ Run with different shells in three ways
 
 * urchin -s
 * $TEST_SHELL variable with $TEST_SHELL
-* $TEST_SHELL variable with urchin -sh
+* $TEST_SHELL variable with urchin -x
 
 Before version 0.0.3
 ----------------------
diff --git a/readme.md b/readme.md
index ef14bfe..9222ea9 100644
--- a/readme.md
+++ b/readme.md
@@ -138,13 +138,13 @@ To test with multiple shells in sequence, use something like:
       urchin -s $shell ./tests
     done
 
-#### (c) Cross shell tests with `urchin -sh` (experimental)
+#### (c) Cross shell tests with `urchin -x` (experimental)
 If you run urchin with the `-sh` flag, it will be as if you ran
 `$TEST_SHELL`. Unless `$TEST_SHELL` isn't set, in which case it'll
 be as if you ran `/bin/sh`. Putting this in she shebang line might
 eventually work out to be a cleaner way of doing cross-shell testing.
 
-    #!/usr/bin/env urchin -sh
+    #!/usr/bin/env urchin -x
     test a = a
 
 ## Alternatives to Urchin