README.md in shellplay-0.1.5 vs README.md in shellplay-0.1.6

@@ -1,14 +1,14 @@
 Shellplay
 ==================
 
 [![Gem Version](https://img.shields.io/gem/v/shellplay.svg)](https://rubygems.org/gems/shellplay)
+[![Downloads](http://img.shields.io/gem/dt/shellplay.svg)](https://rubygems.org/gems/shellplay)
 [![Build Status](https://img.shields.io/travis/mose/shellplay.svg)](https://travis-ci.org/mose/shellplay)
 [![Coverage Status](https://img.shields.io/coveralls/mose/shellplay.svg)](https://coveralls.io/r/mose/shellplay?branch=master)
 [![Dependency Status](https://img.shields.io/gemnasium/mose/shellplay.svg)](https://gemnasium.com/mose/shellplay)
 [![Code Climate](https://img.shields.io/codeclimate/github/mose/shellplay.svg)](https://codeclimate.com/github/mose/shellplay)
-[![Code Climate](http://img.shields.io/gem/dt/shellplay.svg)](https://rubygems.org/gems/shellplay)
 
 ----
 
 This is a CLI tool for recording and presenting step by step operations from the console. It is targeted at presentations that would simulate live coding, without the random murphy factor of it.
 
@@ -100,9 +100,11 @@
 
     shellexport <session_file_name>
     shellplay <remote session url>
 
 It will save the html in a dir in `.shellplay` under the name of the session. The dir contains index.html, css, and js files, ready to be played from your laptop or uploaded to your server.
+
+Note, the `shellexport` command will not override `shellplay.css`, `shellplay.js` and `colors.css` if they exist. So you can apply changes on those files after the first export, then work on your session and re-export. If you want to rest those files, you can just delete them and re-export.
 
 Navigation on the html version is
 
 - `p`, `left` for previous screen,
 - `n`, `enter` or `right` for next screen