Edited Readme to reflect current repo

README.md

@@ -1,12 +1,12 @@
 # IPFS API
 
-> Official spec of the APIs that ipfs implementations must conform to, as well as test suites to ensure they do.
+> IPFS HTTP API code used in doc engines
 
-> **WARNING** This is a work in *progress*. There be dragons.
+[![](https://img.shields.io/badge/made%20by-Protocol%20Labs-blue.svg?style=flat-square)](http://ipn.io)
+[![](https://img.shields.io/badge/project-IPFS-blue.svg?style=flat-square)](http://ipfs.io/)
+[![](https://img.shields.io/badge/freejs-%23ipfs-blue.svg?style=flat-square)](http://webchat.freenode.net/?channels=%23ipfs)
 
-The IPFS API has two levels. The first level is a general description based on function signatures and the second one is the transport specific description.
+![](https://cdn.rawgit.com/jbenet/contribute-ipfs-gif/master/img/contribute.gif)
+
+**WARNING** This is a work in *progress*. There be dragons.
 
-* [Level 1 Spec - Transport Agnostic](level1.md)
-* Level 2 Spec - Transport Specific
-  * [Level 2 CLI Spec](level2/cli.md)
-  * [Level 2 HTTP(S) Spec](level2/http.md)