diff --git a/ChangeLog.md b/ChangeLog.md
--- a/ChangeLog.md
+++ b/ChangeLog.md
@@ -1,5 +1,9 @@
 # Revision history for shh
 
+## 0.7.0.1 -- 2019-08-12
+
+Change how we test for library installation.
+
 ## 0.7.0.0 -- 2019-08-06
 
 This is a fairly major refactor which consolidates a bunch of type classes
diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -180,7 +180,7 @@
 
 ## Usage
 
-Enable Temlpate Haskell and load the environment
+Enable Template Haskell and load the environment
 
     {-# LANGUAGE TemplateHaskell #-}
     $(loadEnv SearchPath)
@@ -205,6 +205,13 @@
 GHCi which automatically loads your environment and allows you to have custom
 config when using GHCi as a shell.
 
+To install it, one option is to use `cabal new-install`
+
+```bash
+cabal new-install --lib shh
+cabal new-install --lib ssh-extras
+```
+
 The `shh` binary will look in your `$SHH_DIR` (defaults to `$HOME/.shh`) for
 a `Shell.hs`, `init.ghci` and `wrapper` files. If these don't exist default
 ones will be created.
@@ -273,7 +280,7 @@
 This table attempts to summarise some of the differences.
 
  * `Pipe Style` refers to how processes are joined together, "native" means
-   that the mechanisms provided by the OS are used, while "via haskell" means
+   that the mechanisms provided by the OS are used, while "via Haskell" means
    that the data is read into the Haskell process, and then written into the
    subprocess.
  * `Via Shell` refers to whether subprocesses are launched directly or via
diff --git a/app/shh-app.hs b/app/shh-app.hs
--- a/app/shh-app.hs
+++ b/app/shh-app.hs
@@ -83,14 +83,17 @@
             setOwnerWritable True $
             emptyPermissions
         doIfMissing "init.ghci" $ do
-            tryFailure (exe (pack wrapper) "ghc-pkg" "latest" "shh") >>= \case
+            putStrLn "Generating init.ghci..."
+            putStrLn " ... checking for shh..."
+            tryFailure (exe (pack wrapper) "ghc" "-e" "import Shh") >>= \case
                 Left _ -> do
                     putStrLn "Please make the shh and shh-extras packages available in the shh"
                     putStrLn "environment (install it globally or modify the wrapper, see docs)."
                     putStrLn "Aborting"
                     exitFailure
                 Right _ -> writeFile "init.ghci" defaultInitGhci
-            tryFailure (exe (pack wrapper) "ghc-pkg" "latest" "shh-extras") >>= \case
+            putStrLn " ... checking for shh-extras..."
+            tryFailure (exe (pack wrapper) "ghc" "-e" "import Shh.Prompt") >>= \case
                 Left _ -> do
                     putStrLn "## WARNING ##########################################################"
                     putStrLn "# You do not have the shh-extras library installed, and so we are"
diff --git a/shh.cabal b/shh.cabal
--- a/shh.cabal
+++ b/shh.cabal
@@ -1,5 +1,5 @@
 name:                shh
-version:             0.7.0.0
+version:             0.7.0.1
 synopsis:            Simple shell scripting from Haskell
 description:         Provides a shell scripting environment for Haskell. It
                      helps you use external binaries, and allows you to
diff --git a/src/Shh/Internal.hs b/src/Shh/Internal.hs
--- a/src/Shh/Internal.hs
+++ b/src/Shh/Internal.hs
@@ -485,11 +485,11 @@
 captureLines :: Shell io => io [ByteString]
 captureLines = captureEndBy "\n"
 
--- | Capture the words of the output.
+-- | Capture stdout, splitting it into words.
 captureWords :: Shell io => io [ByteString]
 captureWords = readInput (pure . BC8.words)
 
--- | Capture the output of the process and attempt to `read` it.
+-- | Capture stdout, and attempt to @`read`@ it
 captureRead :: (Shell io, Read a, NFData a) => io a
 captureRead = readInput (pure . read . toString)
 
diff --git a/test/Readme.lhs b/test/Readme.lhs
--- a/test/Readme.lhs
+++ b/test/Readme.lhs
@@ -180,7 +180,7 @@
 
 ## Usage
 
-Enable Temlpate Haskell and load the environment
+Enable Template Haskell and load the environment
 
     {-# LANGUAGE TemplateHaskell #-}
     $(loadEnv SearchPath)
@@ -205,6 +205,13 @@
 GHCi which automatically loads your environment and allows you to have custom
 config when using GHCi as a shell.
 
+To install it, one option is to use `cabal new-install`
+
+```bash
+cabal new-install --lib shh
+cabal new-install --lib ssh-extras
+```
+
 The `shh` binary will look in your `$SHH_DIR` (defaults to `$HOME/.shh`) for
 a `Shell.hs`, `init.ghci` and `wrapper` files. If these don't exist default
 ones will be created.
@@ -273,7 +280,7 @@
 This table attempts to summarise some of the differences.
 
  * `Pipe Style` refers to how processes are joined together, "native" means
-   that the mechanisms provided by the OS are used, while "via haskell" means
+   that the mechanisms provided by the OS are used, while "via Haskell" means
    that the data is read into the Haskell process, and then written into the
    subprocess.
  * `Via Shell` refers to whether subprocesses are launched directly or via