README.md in intercom-3.4.0 vs README.md in intercom-3.5.1

@@ -20,11 +20,11 @@
 
     gem install intercom
 
 Using bundler:
 
-    gem 'intercom', "~> 3.4.0"
+    gem 'intercom', "~> 3.5.0"
 
 ## Basic Usage
 
 ### Configure your client
 
@@ -189,11 +189,11 @@
 # User (identified by email) replies with a comment
 intercom.conversations.reply(:id => conversation.id, :type => 'user', :email => '[e-mail]', :message_type => 'comment', :body => 'foo')
 # Admin (identified by id) replies with a comment
 intercom.conversations.reply(:id => conversation.id, :type => 'admin', :admin_id => '123', :message_type => 'comment', :body => 'bar')
 # User (identified by email) replies with a comment and attachment
-intercom.conversations.reply(:id => conversation.id, :type => 'user', :email => '[e-mail]', :message_type => 'comment', :body => 'foo', :attachment => ['http://www.example.com/attachment.jpg'])
+intercom.conversations.reply(:id => conversation.id, :type => 'user', :email => '[e-mail]', :message_type => 'comment', :body => 'foo', :attachment_urls => ['http://www.example.com/attachment.jpg'])
 
 # Open
 intercom.conversations.open(id: conversation.id, admin_id: '123')
 
 # Close
@@ -437,10 +437,10 @@
 
 ### Errors
 
 There are different styles for error handling - some people prefer exceptions; some prefer nil and check; some prefer error objects/codes. Balancing these preferences alongside our wish to provide an idiomatic gem has brought us to use the current mechanism of throwing specific exceptions. Our approach in the client is to propagate errors and signal our failure loudly so that erroneous data does not get propagated through our customers' systems - in other words, if you see a `Intercom::ServiceUnavailableError` you know where the problem is.
 
-You do not need to deal with the HTTP response from an API call directly. If there is an unsuccessful response then an error that is a subclass of Intercom:Error will be raised. If desired, you can get at the http_code of an Intercom::Error via its `http_code` method.
+You do not need to deal with the HTTP response from an API call directly. If there is an unsuccessful response then an error that is a subclass of `Intercom::Error` will be raised. If desired, you can get at the http_code of an `Intercom::Error` via its `http_code` method.
 
 The list of different error subclasses are listed below. As they all inherit off Intercom::IntercomError you can choose to rescue Intercom::IntercomError or
 else rescue the more specific error subclass.
 
 ```ruby