README.md in polymer-1.0.0.beta.6 vs README.md in polymer-1.0.0.beta.7

@@ -24,20 +24,15 @@
 
 The recommended way to install Polymer is with Rubygems:
 
     $ [sudo] gem install polymer
 
-Polymer currently uses RMagick/ImageMagick in order to read and write
-images. Eventually, I want to offer support for ChunkyPNG also, which
-should substantially ease installation.
+Polymer uses ChunkyPNG to read source files, and write the final
+sprites; as a pure-Ruby library it is much easier to install than
+RMagick, while not being so much slower as to pose a problem
+(optimisation with PNGOut takes far longer than creating the sprite).
 
-Most Linux and BSD distributions include ImageMagick in their packaging
-system; while Mac OS X users can install it with [Homebrew][homebrew]:
-
-    $ brew install ghostscript
-    $ brew install imagemagick
-
 If you wish to install Polymer from source:
 
     $ git clone http://github.com/antw/polymer.git && cd polymer
     $ gem build polymer.gemspec
     $ [sudo] gem install --local polymer-VERSION.gem
@@ -58,10 +53,10 @@
    directory. Prior to running the command, you may want to glance at
    the [polymer-init(1)][polymer-init] manpage to get an overview of the
    supported options. `polymer init` also places some example source
    images into your project.
 
-2. Run `polymer bond`: this is the main task which converts the source
+2. Run `polymer bon)`: this is the main task which converts the source
    images into the final sprites. If you have PNGOUT, OptiPNG, or
    PNGCrush installed, Polymer will also optimise the generates sprites
    to reduce them to the smallest possible filesize.
 
 3. Run `polymer bond` again. Nothing happens! Polymer maintains a cache