README.markdown in testr-14.2.0 vs README.markdown in testr-14.3.0

@@ -191,20 +191,18 @@
 4. An array of names of tests inside the test file that will be run.  If this
    array is empty, then all tests in the test file will be run.
 
 For example, to see some real values:
 
-    TestR::Config.before_fork_hooks << lambda {
-      |worker_number, log_file, test_file, test_names|
-
+    TestR::Config.before_fork_hooks << lambda do |worker_number, log_file, test_file, test_names|
       p :before_fork_hooks => {
         :worker_number => worker_number,
         :log_file      => log_file,
         :test_file     => test_file,
         :test_names    => test_names,
       }
-    }
+    end
 
 ### TestR::Config.after_fork_hooks
 
 Array of lambda functions that are executed inside a worker process forked
 by `testr-master`.  These functions are given:
@@ -218,20 +216,18 @@
 4. An array of names of tests inside the test file that will be run.  If this
    array is empty, then all tests in the test file will be run.
 
 For example, to see some real values, including the worker process' PID:
 
-    TestR::Config.after_fork_hooks << lambda {
-      |worker_number, log_file, test_file, test_names|
-
+    TestR::Config.after_fork_hooks << lambda do |worker_number, log_file, test_file, test_names|
       p :after_fork_hooks => {
         :worker_pid    => $$,
         :worker_number => worker_number,
         :log_file      => log_file,
         :test_file     => test_file,
         :test_names    => test_names,
       }
-    }
+    end
 
 The first function in this array instructs Test::Unit and RSpec to only run
 those tests that correspond to the given `test_names` values.  This
 accelerates your test-driven development cycle and improves productivity!