Improved grammar etc. in docs/tool-comparation.txt and renamed it to tool-comparisons.

Question: should it be .rst and thus be included in the docs? I think the answer is yes.

docs/tool-comparation.txt

-.. _tool-comparation:
-
-This is not the first time I write a tool for
-behaviour-driven development. I worked on Pyccuracy_ which is a
-awesome tool for testing websites.
-
-And as expected I am a hard user of Pyccuracy_, but since I met
-Cucumber_, I fell in love for Scenario Outlines, global variables and
-tables.  Although Pyccuracy_ does not aim to do the same that Cucumber_
-does, sometimes it sucks, because Cucumber has very handy features, that
-avoid code duplicity and so on.
-
-Thus, Lettuce does not aim on website automated testing, Lettuce is a
-multi-purpose testing tool.
-
-.. _Agile: http://agilemanifesto.org/
-.. _Cucumber: http://cukes.info
-.. _Pyccuracy: http://github.com/heynemann/pyccuracy

docs/tool-comparisons.txt

+.. _tool-comparisons:
+
+This is not the first time I have written a tool for
+behaviour-driven development. I worked on Pyccuracy_ which is an
+awesome tool for testing websites.
+
+As expected I am a hard user of Pyccuracy_, but since I met
+Cucumber_, I fell in love with Scenario Outlines, global variables and
+tables.  Although Pyccuracy_ does not aim to do the same as Cucumber_
+does, sometimes it sucks, because Cucumber has very handy features that
+avoid code duplication and so on.
+
+Thus, Lettuce does not aim solely at automated website testing. Lettuce
+is a multi-purpose testing tool.