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

@@ -6,10 +6,11 @@
 
 The Symbiont gem is designed to provide an open framework for running automated tests against a browser using popular web testing interfaces.
 
 Right now the best information on the purpose of this project and how it works can be found on [my Symbiont-tagged blog posts](http://testerstories.com/?cat=16).
 
+
 Installation
 ------------
 
 Add this line to your application's Gemfile:
 
@@ -21,27 +22,44 @@
 
 Or install it yourself as:
 
     $ gem install symbiont
 
-Meaning
--------
 
+Using Symbiont
+--------------
+
+Check out the [Symbiont Wiki](https://github.com/jnyman/symbiont/wiki) for details on how to use Symbiont.
+
+
+Why call it Symbiont?
+---------------------
+
 A "symbiont" is an organism in a symbiotic (mutually beneficial) relationship. Some of these relationships are called _obligate_, which means that both organisms need each other in order to survive. Other such relationships are called _facultative_, meaning that both organisms don't strictly need each other to survive, but they stand a better chance if they do.
 
 Symbiotic relationships include associations in which one organism lives on another organism -- _ectosymbiosis_ -- or where one organism lives inside the other -- _endosymbiosis_.
 
 So, with that bit of context, think of this gem as a facultative, endosymbiotic organism that lives within your test logic, giving it strength and sustenance.
 
+
 Contributing
 ------------
 
 1. Fork it
 2. Create your feature branch (`git checkout -b my-new-feature`)
 3. Commit your changes (`git commit -am 'Added some feature'`)
 4. Push to the branch (`git push origin my-new-feature`)
 5. Create new Pull Request
 
+
+Credits
+-------
+
+Thanks to Jeff Morgan (http://www.cheezyworld.com/) for his page-object gem, Alister Scott (http://watirmelon.com) for his watir-page-helper gem, and Nat Ritmeyer (http://www.natontesting.com/) for his SitePrism gem. I learned a lot from analyzing their code and working to craft my own solution around theirs. Rather than fork their projects, my changes were systemic enough to warrant creating a new project.
+
+
 Copyright
 ---------
 
 See the LICENSE file for details.
+
+In short, Lucid is under an MIT license. Since I'm borrowing from many other people, just as they borrowed from many other people before them, I'm just establishing I wrote _this_ particular version. (If nothing else, this means you know who to blame.)