README.md in futuroscope-0.0.5 vs README.md in futuroscope-0.0.6

@@ -126,29 +126,30 @@
 
 If you're looking for other ways to improve your code performance via
 concurrency, you should probably deal directly with [Ruby's
 threads](http://ruby-doc.org/core-2.0/Thread.html).
 
-## Thread pool
+## Worker Pool
 
-Futures are scheduled in a thread pool that helps managing concurrency in a way
+Futures are scheduled in a worker pool that helps managing concurrency in a way
 that doesn't get out of hands. Also comes with great benefits since their
 threads are spawned at load time (and not in runtime).
 
-The default thread pool comes with a concurrency of 8 threads, which seems
-reasonable for the most use cases.
+The default thread pool comes with a concurrency of 8 Workers, which seems
+reasonable for the most use cases. It will elastically expand to the default of
+16 threads and will kill them when they're not needed.
 
-The default thread pool can be replaced by a new pool with different 
-concurrency like this:
+The default thread pool can be configured like this:
 
 ```Ruby
-Futuroscope.default_pool = Futuroscope::Pool.new(24)
+Futuroscope.default_pool.min_workers = 2
+Futuroscope.default_pool.max_workers = 16
 ```
 
 Also, each future can be scheduled to a different pool like this:
 
 ```Ruby
-pool = Futuroscope::Pool.new(32)
+pool = Futuroscope::Pool.new(16, 32)
 
 future = Future.new(pool){ :edballs }
 
 # Or with the convenience method
 future = future(pool){ :edballs }