README.md in carrierwave-base64-2.8.1 vs README.md in carrierwave-base64-2.9.0

@@ -1,11 +1,10 @@
 # Carrierwave::Base64
 
 [![Gem Version](https://badge.fury.io/rb/carrierwave-base64.svg)](http://badge.fury.io/rb/carrierwave-base64)
 [![Build Status](https://travis-ci.org/y9v/carrierwave-base64.svg?branch=master)](https://travis-ci.org/y9v/carrierwave-base64)
 [![Code Climate](https://codeclimate.com/github/y9v/carrierwave-base64/badges/gpa.svg)](https://codeclimate.com/github/y9v/carrierwave-base64)
-[![Inch CI](https://inch-ci.org/github/y9v/carrierwave-base64.svg?branch=master)](https://inch-ci.org/github/y9v/carrierwave-base64)
 
 Upload files encoded as base64 to carrierwave.
 
 This small gem can be useful for API's that interact with mobile devices.
 
@@ -31,10 +30,10 @@
 
 ```ruby
 mount_base64_uploader :image, ImageUploader
 ```
 
-Now you can also upload files by passing an encoded base64 string to the attribute.
+Now you can also upload files by passing an encoded base64 string to the attribute. This also works for normal file uploads from file fields inside an HTML form, so you can safely replace `mount_uploader` with `mount_base64_uploader` to support both file input and base64 encoded input
 
 ## Upload file extension
 
 The file extension for the uploaded base64 string is identified automatically using the [mime-types](https://github.com/mime-types/ruby-mime-types/) gem and `content_type` from the uploaded string.