Readme.md in parallel_tests-0.4.11 vs Readme.md in parallel_tests-0.4.12

@@ -1,6 +1,6 @@
-Speedup Test::Unit + RSpec + Cucumber by running parallel on multiple CPUs.
+Speedup Test::Unit + RSpec + Cucumber by running parallel on multiple CPUs(or cores).
 
 Setup for Rails
 ===============
 
 ## Install
@@ -88,12 +88,13 @@
     -p, --path [PATH]                run tests inside this path only
         --no-sort                    do not sort files before running them
     -m, --multiply-processes [FLOAT] use given number as a multiplier of processes to run
     -r, --root [PATH]                execute test commands from this path
     -e, --exec [COMMAND]             execute this code parallel and with ENV['TEST_ENV_NUM']
-    -o, --test-options '[OPTIONS]' execute test commands with those options
+    -o, --test-options '[OPTIONS]'   execute test commands with those options
     -t, --type [TYPE]                which type of tests to run? test, spec or features
+        --non-parallel               execute same commands but do not in parallel, needs --exec
     -v, --version                    Show Version
     -h, --help                       Show this.
 
 You can run any kind of code with -e / --execute
     parallel_test -n 5 -e 'ruby -e "puts %[hello from process #{ENV[:TEST_ENV_NUMBER.to_s].inspect}]"'
@@ -110,28 +111,29 @@
 </table>
 
 TIPS
 ====
  - [Capybara + Selenium] add to env.rb: `Capybara.server_port = 8888 + ENV['TEST_ENV_NUMBER'].to_i`
- - [RSpec] add a `spec/parallel_spec.opts` to use different options, e.g. no --drb (default: `spec/spec.opts`) 
+ - [RSpec] add a `spec/parallel_spec.opts` to use different options, e.g. no --drb (default: `spec/spec.opts`)
  - [RSpec] if something looks fishy try to delete `script/spec`
  - [RSpec] if `script/spec` is missing parallel:spec uses just `spec` (which solves some issues with double-loaded environment.rb)
  - [RSpec] 'script/spec_server' or [spork](http://github.com/timcharper/spork/tree/master) do not work in parallel
  - [RSpec] `./script/generate rspec` if you are running rspec from gems (this plugin uses script/spec which may fail if rspec files are outdated)
  - [Bundler] if you have a `Gemfile` then `bundle exec` will be used to run tests
  - [Capybara setup](https://github.com/grosser/parallel_tests/wiki)
- - [Sphinx setup](https://github.com/grosser/parallel_tests/wiki) 
+ - [Sphinx setup](https://github.com/grosser/parallel_tests/wiki)
+ - [SQL schema format] use :ruby schema format to get faster parallel:prepare`
  - with zsh this would be `rake "parallel:prepare[3]"`
 
 TODO
 ====
  - make jRuby compatible [basics](http://yehudakatz.com/2009/07/01/new-rails-isolation-testing/)
  - make windows compatible
 
 Authors
 ====
-inspired by [pivotal labs](http://pivotallabs.com/users/miked/blog/articles/849-parallelize-your-rspec-suite)  
+inspired by [pivotal labs](http://pivotallabs.com/users/miked/blog/articles/849-parallelize-your-rspec-suite)
 
 ### [Contributors](http://github.com/grosser/parallel_tests/contributors)
  - [Charles Finkel](http://charlesfinkel.com/)
  - [Indrek Juhkam](http://urgas.eu)
  - [Jason Morrison](http://jayunit.net)
@@ -147,8 +149,8 @@
  - [Will Bryant](http://willbryant.net/)
  - [Fred Wu](http://fredwu.me)
  - [xxx](https://github.com/xxx)
  - [Levent Ali](http://purebreeze.com/)
 
-[Michael Grosser](http://pragmatig.wordpress.com)  
[e-mail]  
+[Michael Grosser](http://grosser.it)<br/>
[e-mail]<br/>
 Hereby placed under public domain, do what you want, just do not hold me accountable...