From eb30e9c1ad0449067a8fd2d8dd182e2698d2b267 Mon Sep 17 00:00:00 2001
From: Anthony Brummett <abrummet@genome.wustl.edu>
Date: Fri, 28 Oct 2011 13:06:23 -0500
Subject: [PATCH] Update documentation

It's no longer true that all joins must be pre-declared.  You can use the
dot-syntax for ad-hoc joins
---
 gmt-web/content/documentation.html | 3 +--
 lib/UR/Manual/Overview.pod         | 8 ++------
 2 files changed, 3 insertions(+), 8 deletions(-)

diff --git a/gmt-web/content/documentation.html b/gmt-web/content/documentation.html
index e16296f3..0c95f811 100644
--- a/gmt-web/content/documentation.html
+++ b/gmt-web/content/documentation.html
@@ -120,7 +120,7 @@ <h2><a name="benefits">Benefits</a></h2>
 <ul>
   <li>database queries don't repeat themselves again and again</li>
   <li>you never write insert/update/delete statements, or work out constraint order yourself</li>
-  <li>allows you to write methods which address an object individually, with some ways to avoid tons of individual database queries</li>
+  <li>allows you to write methods which address an object individually, with ways to avoid many individual database queries</li>
   <li>explicitly clearing the cache is less complex than explicitly managing the caching of data</li>
 </ul>
 
@@ -128,7 +128,6 @@ <h2><a name="issues">Issues</a></h2>
 <ul>
   <li>the cache grows until you explicitly clear it, or allow the Context to prune the cache by setting object count limits explicitly</li>
   <li>there is CPU overhead checking the cache if you really are always going directly to the database</li>
-  <li>Joins must be pre-declared through the class definition system</li>
 </ul>
 
 <hr />
diff --git a/lib/UR/Manual/Overview.pod b/lib/UR/Manual/Overview.pod
index f4ec8876..a1ffe4d6 100644
--- a/lib/UR/Manual/Overview.pod
+++ b/lib/UR/Manual/Overview.pod
@@ -174,8 +174,8 @@ order yourself
 
 =item *
 
-allows you to write methods which address an object individually, with some
-ways to avoid tons of individual database queries
+allows you to write methods which address an object individually, with
+ways to avoid many individual database queries
 
 =item *
 
@@ -198,10 +198,6 @@ the cache by setting object count limits explicitly
 there is CPU overhead checking the cache if you really are always going
 directly to the database
 
-=item *
-
-Joins must be pre-declared through the class definition system
-
 =back
 
 =head1 Class Definitions