README.md in humidifier-0.6.1 vs README.md in humidifier-0.7.0

@@ -41,10 +41,18 @@
 
 #### SDK version
 
 Humidifier assumes you have an `aws-sdk` gem installed when you call these operations. It detects the version of the gem you have installed and uses the appropriate API depending on what is available. If Humidifier cannot find any way to use the AWS SDK, it will warn you on every API call and simply return false.
 
+You can also manually specify the version of the SDK that you want to use, in the case that you have both gems in your load path. In that case, you would specify it on the Humidifier configuration object:
+
+```ruby
+Humidifier.configure do |config|
+  config.sdk_version = 1
+end
+```
+
 #### CloudFormation functions
 
 You can use CFN intrinsic functions and references using `Humidifier.fn.[name]` and `Humidifier.ref`. Those will build appropriate structures that know how to be dumped to CFN syntax appropriately.
 
 #### Change Sets
@@ -59,10 +67,10 @@
 
 Resources have an `aws_name` method to see how AWS references them. They also contain a `props` method that contains a hash of the name that Humidifier uses to reference the prop pointing to the appropriate prop object.
 
 ### Large templates
 
-When templates are especially large (larger than 51,200 bytes), they cannot be uploaded directly through the AWS SDK. You can configure Humidifier to seemlessly upload the templates to S3 and reference them using an S3 URL instead by:
+When templates are especially large (larger than 51,200 bytes), they cannot be uploaded directly through the AWS SDK. You can configure Humidifier to seamlessly upload the templates to S3 and reference them using an S3 URL instead by:
 
 ```ruby
 Humidifier.configure do |config|
   config.s3_bucket = 'my.s3.bucket'
   config.s3_prefix = 'my-prefix/' # optional