README.md in access-2.0.20 vs README.md in access-2.0.21

@@ -23,19 +23,20 @@
 ###Config setup
 
 You can configure the following options:
 
   - `access_token` **Required**
-  - `api_environment`: Set as `'demo'` or `'production'`. Default is `'demo'`
+  - `api_environment`: Set as `'demo'` or `'production'`. Default is `'demo'`.
   - `return_json`: Set as `'true'` or `'false'`. Default is `'false'` return ruby objects.
-  - `hashify`: Set as `'true'` or `'false'`. Default is `'false'` return a hashed version of the json response if `return_json` is set to 'true'
+  - `hashify`: Set as `'true'` or `'false'`. Default is `'false'` return a hashed version of the json response if `return_json` is set to 'true'.
+  - `access_timeout`: Set as a number. Default to `'10'`.
 
 #### Config via Environment Variables
 
 You can set config settings by creating environment variables called:
 
-`ENV['ACCESS_TOKEN']`, `ENV['ACCESS_ENVIRONMENT']`, `ENV['ACCESS_RETURN_JSON']`, `ENV['ACCESS_HASHIFY']`
+`ENV['ACCESS_TOKEN']`, `ENV['ACCESS_ENVIRONMENT']`, `ENV['ACCESS_RETURN_JSON']`, `ENV['ACCESS_HASHIFY']`, `ENV['ACCESS_TIMEOUT']`
 
 #### Config via Initializer
 
 You can also create an initializer file to set up a config
 
@@ -52,9 +53,11 @@
 ### Config via Params
 
 `return_json` can be overwritten by passing in by passing the param `return_json` to the end of any call that accepts options.
 
 `hashify` can be overwritten by passing in by passing the param `hashify` to the end of any call that accepts options.
+
+`access_token` can be overwritten by passing in by passing the param `access_token` to the end of any call that accepts options.
 
 ###Making Calls
 
 ####Offer