README.md in guard-rspec-3.0.3 vs README.md in guard-rspec-3.1.0

@@ -60,11 +60,10 @@
   watch(%r{^app/(.*)(\.erb|\.haml|\.slim)$})          { |m| "spec/#{m[1]}#{m[2]}_spec.rb" }
   watch(%r{^lib/(.+)\.rb$})                           { |m| "spec/lib/#{m[1]}_spec.rb" }
   watch(%r{^app/controllers/(.+)_(controller)\.rb$})  { |m| ["spec/routing/#{m[1]}_routing_spec.rb", "spec/#{m[2]}s/#{m[1]}_#{m[2]}_spec.rb", "spec/acceptance/#{m[1]}_spec.rb"] }
 end
 ```
-
 Please read [Guard doc](https://github.com/guard/guard#readme) for more information about the Guardfile DSL.
 
 ## Options
 
 You can pass any of the standard RSpec CLI options using the `:cli` option:
@@ -142,12 +141,23 @@
 :zeus => true                # enable zeus support; default: false
 :foreman => true             # enable foreman support; default: false
 :focus_on_failed => false    # focus on the first 10 failed specs first, rerun till they pass
 :parallel => true            # run all specs in parallel using [ParallelTests](https://github.com/grosser/parallel_tests) gem, default: false
 :parallel_cli => "-n 2"      # pass arbitrary Parallel Tests arguments, default: ""
+:launchy => nil              # pass a path to an rspec results file, e.g. ./tmp/spec_results.html
 ```
 
 You can also use a custom binstubs directory using `:binstubs => 'some-dir'`.
+
+### Using Launchy to view rspec results
+guard-rspec can be configured to launch a results file in lieu of outputing rspec results to the terminal.
+Configure your Guardfile with the launchy option
+``` ruby
+guard 'rspec', :cli=>'--color --format html --out ./tmp/spec_results.html' do
+  :launchy => "./tmp/spec_results.html"
+  # ...
+end
+```
 
 ### DRb mode
 
 When you specify `--drb` within `:cli`, guard-rspec will circumvent the `rspec` command line tool by
 directly communicating with the RSpec DRb server.  This avoids the extra overhead incurred by your