README.md in pair_see-0.1.3 vs README.md in pair_see-0.1.4

@@ -1,21 +1,21 @@
 # PairSee
 
 [![Code Climate](https://codeclimate.com/github/compwron/pairSee/badges/gpa.svg)](https://codeclimate.com/github/compwron/pairSee)
 [![Test Coverage](https://codeclimate.com/github/compwron/pairSee/badges/coverage.svg)](https://codeclimate.com/github/compwron/pairSee)
 [![Build Status](https://travis-ci.org/compwron/pairSee.svg)](https://travis-ci.org/compwron/pairSee)
-[![Dependency Status](https://gemnasium.com/compwron/pairSee.png)](https://gemnasium.com/compwron/pairSee)
+[![Dependency Status](https://gemnasium.com/badges/github.com/compwron/pairSee.svg)](https://gemnasium.com/github.com/compwron/pairSee)
 [![Gem Version](https://img.shields.io/gem/v/pair_see.svg)](https://rubygems.org/gems/pair_see)
 [![License](http://img.shields.io/:license-mit-blue.svg)](http://doge.mit-license.org)
 
 
 Usage cases:
 * See commit count for all devs and solo devs (in order by # of commits): $ pairsee --after 2012-10-01
 * See what cards have been in play and for how long since given date: $ pairsee --cards --after 2012-10-01
 * See all devs and what cards they have worked on since given date: $ pairsee --after 2013-11-01 -s
 
-Example usage: 
+Example usage:
 ```
 $ pairsee --root ../../my_code --after 2012-07-10 --config ../../foo/config/config.yml
 $ pairsee --extras --root ../../my_code
 $ pairsee --latest --after 2012-09-01 # this outputs pairings by most recent by all devs who have committed since given date (purpose of this is to exclude people who are no longer committers)
 ```
@@ -51,10 +51,10 @@
 ```
 names: Person1 Person2 Person3
 card_prefix: FOO-
 ```
 
-So if your commit log looks like 
+So if your commit log looks like
 ```
 "Bob/Alice [FOO-1] wrote code"
 "Alice [FOO-1] stuff"
 "Sarah|Alice [FOO-2] code and stuff"
 ```