README.md in platform-api-2.1.0 vs README.md in platform-api-2.2.0

@@ -54,13 +54,13 @@
 The [API documentation](http://heroku.github.io/platform-api/_index.html) contains a 
 description of all available resources and methods.
 
 ### Handling errors
 
-The client uses [Excon](https://github.com/geemus/excon) under the hood and
-raises `Excon::Errors::Error` exceptions when errors occur.  You can catch specific
-[Excon error types](https://github.com/geemus/excon/blob/master/lib/excon/errors.rb) if you want.
+The client uses [Excon](https://github.com/excon/excon) under the hood and
+raises `Excon::Error` exceptions when errors occur.  You can catch specific
+[Excon error types](https://github.com/excon/excon/blob/master/lib/excon/error.rb) if you want.
 
 ### A real world example
 
 Let's go through an example of creating an app and using the API to work with
 it.  The first thing you need is a client setup with an OAuth token.  You can
@@ -187,9 +187,19 @@
     "MYAPP"=>"ROCKS"}
 ```
 
 As you can see, any action that needs a request body takes it as a plain Ruby
 object, as the final parameter of the method call.
+
+Using the same principle you can even pass in a specific version of PostgreSQL
+at the time of creation:
+
+```ruby
+heroku.addon.create('floating-retreat-4255', {'plan' => 'heroku-postgresql:dev', 'config' => {'version' => '9.4'})
+```
+
+Make sure to use the correct version. If the version is incorrect or unsupported,
+it will just error out.
 
 Let's continue by deploying a sample app.  We'll use the
 [Geosockets](https://github.com/heroku-examples/geosockets) example app:
 
 ```bash