README.md in vcr-2.9.0 vs README.md in vcr-2.9.1

@@ -36,23 +36,23 @@
 * Automatically records and replays your HTTP interactions with minimal setup/configuration code.
 * Supports and works with the HTTP stubbing facilities of multiple libraries.  Currently, the
   following are supported:
   * [WebMock](https://github.com/bblimke/webmock)
   * [Typhoeus](https://github.com/typhoeus/typhoeus)
-  * [Faraday](https://github.com/technoweenie/faraday)
+  * [Faraday](https://github.com/lostisland/faraday)
   * [Excon](https://github.com/geemus/excon)
   * [FakeWeb](https://github.com/chrisk/fakeweb) (deprecated)
 * Supports multiple HTTP libraries:
   * [Patron](http://github.com/toland/patron) (when using WebMock)
   * [Curb](http://github.com/taf2/curb) (when using WebMock -- only supports Curl::Easy at the moment)
   * [HTTPClient](http://github.com/nahi/httpclient) (when using WebMock)
   * [em-http-request](http://github.com/igrigorik/em-http-request) (when using WebMock)
   * [Net::HTTP](http://www.ruby-doc.org/stdlib/libdoc/net/http/rdoc/index.html) (when using FakeWeb and WebMock)
   * [Typhoeus](https://github.com/typhoeus/typhoeus) (Typhoeus::Hydra, but not Typhoeus::Easy or Typhoeus::Multi)
   * [Excon](https://github.com/geemus/excon)
-  * [Faraday](https://github.com/technoweenie/faraday)
-  * And of course any library built on Net::HTTP, such as [Mechanize](http://github.com/tenderlove/mechanize),
-    [HTTParty](http://github.com/jnunemaker/httparty) or [Rest Client](http://github.com/archiloque/rest-client).
+  * [Faraday](https://github.com/lostisland/faraday)
+  * And of course any library built on Net::HTTP, such as [Mechanize](http://github.com/sparklemotion/mechanize),
+    [HTTParty](http://github.com/jnunemaker/httparty) or [Rest Client](http://github.com/rest-client/rest-client).
 * Request matching is configurable based on HTTP method, URI, host, path, body and headers, or you can easily
   implement a custom request matcher to handle any need.
 * The same request can receive different responses in different tests--just use different cassettes.
 * The recorded requests and responses are stored on disk in a serialization format of your choice
   (currently YAML and JSON are built in, and you can easily implement your own custom serializer)