README.md in lhm-2.0.0 vs README.md in lhm-2.1.0

@@ -180,27 +180,35 @@
 during the run will happen on the new table as well.
 
 ## Cleaning up after an interrupted Lhm run
 
 If an Lhm migration is interrupted, it may leave behind the temporary tables
-used in the migration. If the migration is re-started, the unexpected presence
-of these tables will cause an error. In this case, `Lhm.cleanup` can be used
-to drop any orphaned Lhm temporary tables.
+and/or triggers used in the migration. If the migration is re-started, the
+unexpected presence of these tables will cause an error.
 
-To see what Lhm tables are found:
+In this case, `Lhm.cleanup` can be used to drop any orphaned Lhm temporary tables or triggers.
 
+To see what Lhm tables/triggers are found:
+
 ```ruby
 Lhm.cleanup
 ```
 
-To remove any Lhm tables found:
+To remove any Lhm tables/triggers found:
 ```ruby
 Lhm.cleanup(true)
 ```
 
 ## Contributing
 
+First, get set up for local development:
+
+    git clone git://github.com/soundcloud/lhm.git
+    cd lhm
+
+To run the tests, follow the instructions on [spec/README](https://github.com/soundcloud/lhm/blob/master/spec/README.md).
+
 We'll check out your contribution if you:
 
   * Provide a comprehensive suite of tests for your fork.
   * Have a clear and documented rationale for your changes.
   * Package these up in a pull request.
@@ -221,6 +229,6 @@
 [0]: http://openarkkit.googlecode.com
 [1]: http://www.facebook.com/note.php?note\_id=430801045932
 [2]: https://github.com/freels/table_migrator
 [3]: http://www.percona.com/doc/percona-toolkit/2.1/pt-online-schema-change.html
 [4]: https://travis-ci.org/soundcloud/lhm
-[5]: https://travis-ci.org/soundcloud/lhm.png?branch=master
+[5]: https://travis-ci.org/soundcloud/lhm.svg?branch=master