diff --git a/docs/releases/1.3-alpha-1.txt b/docs/releases/1.3-alpha-1.txt
index 8cad6c2c33..550c329c66 100644
--- a/docs/releases/1.3-alpha-1.txt
+++ b/docs/releases/1.3-alpha-1.txt
@@ -31,10 +31,12 @@ Class-based views
 
 Django 1.3 adds a framework that allows you to use a class as a view.
 This means you can compose a view out of a collection of methods that
-can be subclassed and overridden to provide analogs of all the old
-function-based generic views have been provided, along with a completely
-generic view base class that can be used as the basis for reusable
-applications that can be easily extended.
+can be subclassed and overridden to provide common views of data without
+having to write too much code.
+
+Analogs of all the old function-based generic views have been provided,
+along with a completely generic view base class that can be used as
+the basis for reusable applications that can be easily extended.
 
 See :doc:`the documentation on Class-based Generic Views
 </topics/class-based-views>` for more details. There is also a document to
diff --git a/docs/releases/1.3.txt b/docs/releases/1.3.txt
index addf849fbd..118d4e1e36 100644
--- a/docs/releases/1.3.txt
+++ b/docs/releases/1.3.txt
@@ -22,7 +22,8 @@ Class-based views
 
 Django 1.3 adds a framework that allows you to use a class as a view.
 This means you can compose a view out of a collection of methods that
-can be subclassed and overridden to provide
+can be subclassed and overridden to provide common views of data without
+having to write too much code.
 
 Analogs of all the old function-based generic views have been
 provided, along with a completely generic view base class that can be