README.rdoc in qed-2.4.0 vs README.rdoc in qed-2.5.0
- old
+ new
@@ -1,12 +1,8 @@
= Ruby Q.E.D.
- homepage: http://proutils.github.com/qed
- mailing list: http://groups.google.com/group/proutils
- development: http://github.com/proutils/qed
-
== Introduction
Q.E.D. is an abbreviation for the well known Latin phrase "Quod Erat Demonstrandum",
literally "which was to be demonstrated", which is oft written in its abbreviated
form at the end of a mathematical proof or philosophical argument to signify the
@@ -28,10 +24,17 @@
* Uses the excellent Assertive Expressive library for assertions.
* Table macro allows large sets of data to be run by the same code.
* Documentation tool provides nice output with jQuery-based TOC.
+== Resources
+
+* homepage: http://rubyworks.github.com/qed
+* mailing list: http://groups.google.com/group/rubyworks
+* development: http://github.com/rubyworks/qed
+
+
== Synopsis
=== Assertion Syntax
QED uses the AE (Assertive Expressive) library to provide an elegant means to
@@ -41,10 +44,10 @@
In this example, because 4 != 5, this expression will raise an Assertion
exception. QED's Runner class is thus just a means of running and capturing
code blocks containing these assertions.
-You can learn more about AE at http://proutils.github.com/ae.
+You can learn more about AE at http://rubyworks.github.com/ae.
=== Document Structure
QED documents are simply text files called *demonstrandum*. Because they
largely consist of free-form descriptive text, they are a practice pure