README.markdown in respec-0.8.3 vs README.markdown in respec-0.9.0

@@ -11,11 +11,11 @@
 
 3 fail. Rerun just the 3 failures like this:
 
     respec f
 
-Need to debug failure #1? Pop a `debugger` in your code, and rerun it
+Need to debug failure #1? Pop a `debugger` (or `pry`) in your code, and rerun it
 like this:
 
     respec 1
 
 This will just rerun failure 1. Once it's passing, rerun the 3 failing
@@ -48,21 +48,29 @@
 If the argument doesn't name an existing file, it's assumed to be an
 example name.
 
 It'll even `bundle exec` for you automatically, or use a binstub if present.
 
+If you use git, run all specs modified since the last commit with:
+
+    respec d
+
+(**d** for "git **d**iff", which this uses.)
+
 There are a few other shortcuts. `respec --help` to see them all.
 
-If you're using this on CI, you may want to control where the failure file is
-written. You can do this in one of 2 ways:
+If you're using this on CI to [rerun your failures][junit-merge], you may want
+to control where the failure file is written. You can do this in one of 2 ways:
 
-Either pass a FAILURES argument:
+Either pass a `FAILURES=...` argument:
 
     respec FAILURES=/path/to/file ...
 
 Or use the `RESPEC_FAILURES` environment variable.
 
     RESPEC_FAILURES=/path/to/file respec ...
+
+[junit-merge]: https://github.com/oggy/junit_merge
 
 ## Contributing
 
  * [Bug reports](https://github.com/oggy/respec/issues)
  * [Source](https://github.com/oggy/respec)