[ci skip] fix docs and bump version

Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    cassandra-driver (2.1.1)
+    cassandra-driver (2.1.3)
       ione (~> 1.2)
 
 GEM

README.md

@@ -91,7 +91,7 @@ __Note__: if you want to use compression you should also install [snappy](http:/
 
 Some of the new features added to the driver have unfortunately led to changes in the original cql-rb API. In the examples directory, you can find [an example of how to wrap the ruby driver to achieve almost complete interface parity with cql-rb](https://github.com/datastax/ruby-driver/blob/master/examples/cql-rb-wrapper.rb) to assist you with gradual upgrade.
 
-## What's new in v2.1.1
+## What's new in v2.1.3
 
 Features:
 

docs.yaml

@@ -29,20 +29,14 @@ links:
   - title: Releases
     href:  https://github.com/datastax/ruby-driver/releases
 versions:
-  - name: v2.1.1
-    ref:  aca873205f0d17d8fdeda315e5c99be4fc49c037
-  - name: v2.1.0
-    ref:  4821258dce39c47b936672b3b870048e40990708
+  - name: v2.1.3
+    ref:  c93eac55227e1d188d863d53bf5a90df95264dba
   - name: v2.0.1
     ref:  80cab0ad188511ec16eb39111c0b67329c754729
-  - name: v2.0.0
-    ref:  4b0b0efd8e8e3d36d7eb0bfe809a4ce0f5d5aa73
   - name: v1.2.0
     ref:  6c398cb3dbc5218f6a77177dcc2130d11bf0158a
   - name: v1.1.1
     ref:  1763066e2f70db8889799aa0af4a8eb63ad9ab74
-  - name: v1.1.0
-    ref:  3a69e5b21113b91b1bc364ceeefb4e2940181194
   - name: v1.0.0
     ref:  72bfc9609f94e904c0186b061a02404fb2c0d22e
   - name: v1.0.0-rc.1

features/README.md

@@ -40,7 +40,7 @@ For queries that will be run repeatedly, [you should use Prepared statements](#p
 **If you're using Cassandra 2.0 or later** you no longer have to build CQL strings when you want to insert a value in a query, there's a new feature that lets you bind values with regular statements:
 
 ```ruby
-session.execute("UPDATE users SET age = ? WHERE user_name = ?", 41, 'Sam')
+session.execute("UPDATE users SET age = ? WHERE user_name = ?", arguments: [41, 'Sam'])
 ```
 
 If you find yourself doing this often, it's better to use prepared statements. As a rule of thumb, if your application is sending a request more than once, a prepared statement is almost always the right choice.
@@ -61,7 +61,7 @@ data = [
 
 # execute all statements in background
 futures = data.map do |(age, username)|
-  session.execute_async("UPDATE users SET age = ? WHERE user_name = ?", age, username)
+  session.execute_async("UPDATE users SET age = ? WHERE user_name = ?", arguments: [age, username])
 end
 
 # block until both statements executed
@@ -77,7 +77,7 @@ The driver supports prepared statements. Use `#prepare` to create a statement ob
 ```ruby
 statement = session.prepare('INSERT INTO users (username, email) VALUES (?, ?)')
 
-session.execute(statement, 'avalanche123', '[email protected]')
+session.execute(statement, arguments: ['avalanche123', '[email protected]'])
 ```
 
 You should prepare a statement for a given query **only** once and then resue it by calling #execute. Re-preparing the same statement will have a negative impact on the performance and should be avoided.

lib/cassandra/version.rb

@@ -17,5 +17,5 @@
 #++
 
 module Cassandra
-  VERSION = '2.1.1'.freeze
+  VERSION = '2.1.3'.freeze
 end