README.md in elasticsearch-transport-1.0.7 vs README.md in elasticsearch-transport-1.0.9

@@ -25,14 +25,15 @@
 * Pluggable transport implementation, customizable and extendable
 * Pluggable serializer implementation
 * Request retries and dead connections handling
 * Node reloading (based on cluster state) on errors or on demand
 
-For optimal performance, you should use a HTTP library which supports persistent ("keep-alive") connections,
-e.g. [Patron](https://github.com/toland/patron) or [Typhoeus](https://github.com/typhoeus/typhoeus).
-Just `require 'patron'` or `require 'typhoeus'; require 'typhoeus/adapters/faraday'` in your code,
-and it will be automatically used; other automatically used libraries are
+For optimal performance, use a HTTP library which supports persistent ("keep-alive") connections,
+such as [Typhoeus](https://github.com/typhoeus/typhoeus).
+Just require the library (`require 'typhoeus'; require 'typhoeus/adapters/faraday'`) in your code,
+and it will be automatically used; currently these libraries will be automatically detected and used:
+[Patron](https://github.com/toland/patron),
 [HTTPClient](https://rubygems.org/gems/httpclient) and
 [Net::HTTP::Persistent](https://rubygems.org/gems/net-http-persistent).
 
 For detailed information, see example configurations [below](#transport-implementations).
 
@@ -168,10 +169,11 @@
 When the client is initialized with multiple hosts, it makes sense to retry a failed request
 on a different host:
 
     Elasticsearch::Client.new hosts: ['localhost:9200', 'localhost:9201'], retry_on_failure: true
 
-You can specify how many times should the client retry the request before it raises an exception:
+You can specify how many times should the client retry the request before it raises an exception
+(the default is 3 times):
 
     Elasticsearch::Client.new hosts: ['localhost:9200', 'localhost:9201'], retry_on_failure: 5
 
 ### Reloading Hosts