README.md in pessimize-0.1.0 vs README.md in pessimize-0.2.0

@@ -1,7 +1,8 @@
 # Pessimize
 
+[![Gem Version](https://badge.fury.io/rb/pessimize.png)](http://badge.fury.io/rb/pessimize)
 [![Build Status](https://travis-ci.org/joonty/pessimize.png?branch=master)](https://travis-ci.org/joonty/pessimize)
 
 ### Who is this for?
 Anyone who works with a Gemfile, i.e. a project that uses [bundler][1].
 
@@ -62,12 +63,12 @@
 
 Also, by default, the Gemfile and Gemfile.lock are copied as a form of backup. To skip this backup (for instance, if you're confident that your Gemfile is committed into version control) then add the `--no-backup` option.
 
 ## Known issues
 
-Pessimize evaluates the Gemfile as executable ruby code. That means that anything method-like will be retained in the output (e.g. `gem "nokogiri"`, or `source "https://rubygems.org"`), but anything else such as conditional statements will not.
+Pessimize parses the Gemfile as tokens, and does some tricky stuff to replace or insert version numbers. However, this is fairly experimental and there are plans to use a proper ruby parser, which should be more reliable and cut out the edge cases. It *should* currently work for the majority of cases, but there are no guarantees.
 
-There are plans to fix this: [see this issue][3] for tracking the progress.
+[See this issue][3] for tracking the progress.
 
 ## Why `bundle update` can be dangerous
 
 If you add gems to your Gemfile without specifying a version, bundler will attempt to get the latest stable version for that gem. When you first run `bundle install`, bundler will get and install the latest versions, then create a `Gemfile.lock` which specifies the versions used.