Update README.md

README.md

@@ -13,11 +13,6 @@ There is nothing faster.  There is nothing more correct.  HikariCP is a "zero-ov
         <scope>compile</scope>
     </dependency>
 ```
-----------------------------------------------------
-***Thank you!***<br/>
-We just wanted to say "Thank you!" for all of your support. As you can see, you have all helped HikariCP off to a great start over the past few months. The momentum is here.
-
-![](https://github.com/brettwooldridge/HikariCP/wiki/Downloads.png)
 
 ----------------------------------------------------
 ***JMH Benchmarks***<br/>
@@ -35,6 +30,14 @@ Using the excellent [JMH microbenchmark framework](http://openjdk.java.net/proje
 <sup>2</sup> Tomcat fails to complete *Statement Cycle* benchmark when "StatementFinalizer" feature is enabled.<br/>
 <sup>3</sup> Benchmark results run against 1.3.3<br/>
 
+----------------------------------------------------
+***User Testimonial***<br/>
+The guys over at [Edulify](https://edulify.com) were experiencing connection leaks and other issues using BoneCP in their Play Framework application.  They creating a [HikariCP plugin for Play Framework](http://edulify.github.io/play-hikaricp.edulify.com/) to give HikariCP a try.  In their own words, "Here is a cool graph that shows connections opened to PostgreSQL.  As you can see, the pool is way more stable. Also it is keeping its size at the minimum since we deploy it."
+
+![](https://github.com/brettwooldridge/HikariCP/wiki/HikariVsBone.png)
+
+----------------------------------------------------
+
 #### What's up with other pools?
 
 Not all pools are created equal.  Read our [pool analysis](https://github.com/brettwooldridge/HikariCP/wiki/Pool-Analysis) here if you care to know the good, bad, and ugly.