README.md in pitchfork-0.8.0 vs README.md in pitchfork-0.9.0

@@ -7,17 +7,10 @@
 only serve fast clients on low-latency, high-bandwidth connections and take
 advantage of features in Unix/Unix-like kernels. Slow clients should
 only be served by placing a reverse proxy capable of fully buffering
 both the request and response in between `pitchfork` and slow clients.
 
-## Disclaimer
-
-Until this notice is removed from the README, `pitchfork` should be
-considered experimental. As such it is not encouraged to run it in
-production just yet unless you feel capable of debugging yourself
-any issue that may arise.
-
 ## Features
 
 * Designed for Rack, Linux, fast clients, and ease-of-debugging. We
   cut out everything that is better supported by the operating system,
   [nginx](https://nginx.org/) or [Rack](https://rack.github.io/).
@@ -38,11 +31,25 @@
 * Process management: `pitchfork` will reap and restart workers that
   die from broken apps. There is no need to manage multiple processes
   or ports yourself. `pitchfork` can spawn and manage any number of
   worker processes you choose to scale to your backend.
 
+* Adaptative timeout: request timeout can be extended dynamically on a
+  per request basis, which allows to keep a strict overall timeout for
+  most endpoints, but allow a few endpoints to take longer.
+
 * Load balancing is done entirely by the operating system kernel.
   Requests never pile up behind a busy worker process.
+
+## When to Use
+
+Pitchfork isn't inherently better than other Ruby application servers, it mostly
+focus on different tradeoffs.
+
+If you are fine with your current server, it's best to stick with it.
+
+If there is a problem you are trying to solve, please read the
+[migration guide](docs/WHY_MIGRATE.md) first.
 
 ## Requirements
 
 Ruby(MRI) Version 2.5 and above.