README in third_base-1.0.0 vs README in third_base-1.0.1

@@ -16,24 +16,24 @@
 applications.  If we decide not to care about the Date of Calendar Reform
 and the fact that the Astronomical Julian Date differs from the Julian
 Date, much of the complexity of Ruby's standard Date/DateTime class can
 be removed, and there can be significant improvements in speed.
 
-== Installation
+== Resources
 
-  sudo gem install third_base
+* {RDoc}[http://third-base.rubyforge.org]
+* {Source code}[http://github.com/jeremyevans/third_base]
+* {Bug tracking}[http://rubyforge.org/projects/third-base/]
 
-== Source
+To check out the source code:
+  
+    git clone git://github.com/jeremyevans/third_base.git
 
-Source is available via github:
+== Installation
 
-  http://github.com/jeremyevans/third_base
+  sudo gem install third_base
 
-You can check it out with git:
-
-  git clone git://github.com/jeremyevans/third_base.git
-
 == Usage and Compatibility
 
 There are three ways that ThirdBase can be used:
 
 === Alongside the standard Date/DateTime class
@@ -218,10 +218,10 @@
   DateTime.strptime            10.860000   0.380000  11.240000 ( 11.243913)
   ThirdBase::DateTime.strptime  3.410000   0.160000   3.570000 (  3.574491)
 
 === Real World Example
 
-ThirdBase was written to solve a real world problem, slow retreval of records
+ThirdBase was written to solve a real world problem, slow retrieval of records
 from a database because they contained many date fields. The table in
 question (employees), has 23 fields, 5 of which are date fields.  Here are
 the results of selecting all records for the database via Sequel, both with
 and without third_base: