README.md in tork-19.5.0

- old
+ new

@@ -41,16 +41,17 @@
 Following UNIX philosophy, Tork is composed of simple text-based programs that
 *do one thing well*.  As a result, you can even create your own user interface
 for Tork by wrapping the tork-driver(1) program appropriately!
 
 * tork(1) is an interactive command-line user interface for tork-driver(1)
+* tork-runner(1) runs your test suite once, non-interactively, and then exits
 * tork-herald(1) monitors current directory tree and reports changed files
 * tork-driver(1) drives the engine according to the herald's observations
 * tork-engine(1) tells master to run tests and keeps track of test results
 * tork-master(1) absorbs test execution overhead and forks to run your tests
 * tork-remote(1) remotely controls any Tork program running in the same `pwd`
-* tork-notify(1) shows how to receive and process messages from Tork programs
+* tork-notify(1) notifies you when previously passing tests fail or vice versa
 
 When the herald observes that files in or beneath the current directory have
 been written to, it tells the driver, which then commands the master to fork a
 worker process to run the tests affected by those changed files.  This is all
 performed *automatically*.  However, to run a test file *manually*, you can:
@@ -74,10 +75,13 @@
         echo run_test_file test/some_test.rb | tork-remote tork-engine
 
         # run lines 4, 33, and 21 of test/some_test.rb
         echo run_test_file test/some_test.rb 4 33 21 | tork-remote tork-engine
 
+Alternatively, you can use tork-runner(1) to run your test suite in one shot
+and then exit with a nonzero status if tests failed, similar to `rake test`.
+
 ## Installation
 
     gem install tork
 
 ### Prerequisites
@@ -125,10 +129,10 @@
     # run lines 4, 33, and 21 of test/some_test.rb
     echo run_test_file test/some_test.rb 4 33 21 | tork-remote tork-engine
 
 You can monitor your test processes from another terminal:
 
-    watch 'pgrep -f ^tork | xargs -r ps u'
+    watch 'pgrep -f ^tork | xargs -r ps uf'
 
 ### With MiniTest
 
 MiniTest 1.3.2 and newer contain a bug where `minitest/autorun` won't run any
 tests if someone calls `Kernel#exit` explicitly or simply loads a library