diff --git a/README.md b/README.md
--- a/README.md
+++ b/README.md
@@ -11,11 +11,11 @@
 
 ### Usage
 You can start GHCi in your project with one of the following commands to enable
-the necessary plugin. You can add `pinned-warnings` as a package dependency to
-avoid having to include the additional argument.
+the necessary plugin. Add `pinned-warnings` as a package dependency to avoid
+having to include the additional argument.
 ```
 cabal update
-cabal new-repl -b pinned-warnings --ghc-options="-fplugin PinnedWarnings"
+cabal new-repl -b pinned-warnings --repl-options="-fplugin PinnedWarnings"
 
 stack update
 stack repl --package pinned-warnings --ghci-options "-fplugin PinnedWarnings"
@@ -35,6 +35,8 @@
 With this you can simply use `:sw` to view warnings.
 
 ### Known limitations
-- Warnings produced outside of module type checking are not captured,
-  for example those related to `.cabal` file omissions.
+- Warnings produced outside of module type checking are not captured, for
+  example those related to `.cabal` file omissions.
 - Only the specified versions of GHC are supported
+- If you make changes to files and call `showWarnings` without reloading first,
+  the messages may not be referencing the right code anymore.
diff --git a/pinned-warnings.cabal b/pinned-warnings.cabal
--- a/pinned-warnings.cabal
+++ b/pinned-warnings.cabal
@@ -4,7 +4,7 @@
 -- http://haskell.org/cabal/users-guide/
 
 name:                pinned-warnings
-version:             0.1.0.0
+version:             0.1.0.1
 synopsis: Preserve warnings in a GHCi session
 description: Please see the README on GitHub at <https://github.com/aaronallen8455/pinned-warnings#readme>
 homepage:       https://github.com/aaronallen8455/pinned-warnings#readme