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 @@
- database queries don't repeat themselves again and again
- you never write insert/update/delete statements, or work out constraint order yourself
- - 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
- explicitly clearing the cache is less complex than explicitly managing the caching of data
@@ -128,7 +128,6 @@
- the cache grows until you explicitly clear it, or allow the Context to prune 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
- - Joins must be pre-declared through the class definition system
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