diff --git a/source/core/indexes.txt b/source/core/indexes.txt
index 420532cba31..be262d10e4f 100644
--- a/source/core/indexes.txt
+++ b/source/core/indexes.txt
@@ -796,6 +796,9 @@ the supported languages.
 ``text`` indexes have the following storage requirements and
 performance costs:
 
+- Text indexes change the space allocation method for the documents in
+  the collection to :collflag:`usePowerOf2Sizes`.
+
 - Text indexes can be large. They contain one index entry for each
   unique post-stemmed word in each indexed field for each document
   inserted.
diff --git a/source/reference/aggregation/match.txt b/source/reference/aggregation/match.txt
index 57a8c44f275..88a5629f3b3 100644
--- a/source/reference/aggregation/match.txt
+++ b/source/reference/aggregation/match.txt
@@ -87,7 +87,7 @@ $match (aggregation)
 
    .. versionadded:: 2.4
       :pipeline:`$match` queries can support the
-      geospatial :mongodb:operator:`$within` operations.
+      geospatial :mongodb:operator:`$geoWithin` operations.
 
    .. warning::
 
diff --git a/source/reference/operator/geoWithin.txt b/source/reference/operator/geoWithin.txt
index 3d1917966e5..ae88411f513 100644
--- a/source/reference/operator/geoWithin.txt
+++ b/source/reference/operator/geoWithin.txt
@@ -93,5 +93,8 @@ $geoWithin
 .. operator:: $within
 
    .. deprecated:: 2.4
-      In 2.4, :operator:`$geoWithin` replaces :operator:`$within`.
+      :operator:`$geoWithin` replaces :operator:`$within` in MongoDB 2.4.
+      Additionally, :operator:`$within` no longer require a geospatial
+      index. However, geospatial indexes support much faster queries
+      than the unindexed equivalents.
  
\ No newline at end of file
diff --git a/source/release-notes/2.4.txt b/source/release-notes/2.4.txt
index 83bafb191ec..e18584952ef 100644
--- a/source/release-notes/2.4.txt
+++ b/source/release-notes/2.4.txt
@@ -91,6 +91,12 @@ query operator for queries on GeoJSON data:
 
 The operators use the new :operator:`$geometry` parameter.
 
+The :operator:`$within` operator has been deprecated. Use
+:operator:`$geoWithin` instead. Additionally, if using
+:operator:`$within`, applications can use the :operator:`$within`
+operator without a geospatial index. However, geospatial indexes
+support much faster queries.
+
 For more information, see:
 
 - :doc:`/applications/geospatial-indexes`
@@ -466,9 +472,12 @@ MongoDB 2.4 introduces a number of additional functionality and
 improved performance for the :doc:`Aggregation Framework
 </applications/aggregation>`. Consider the following additions in 2.4:
 
-- :agg:pipeline:`$match` queries now support the :operator:`$within`
+- :agg:pipeline:`$match` queries now support the :operator:`$geoWithin`
   operator for bounded geospatial queries.
 
+- The new :agg:pipeline:`$geoNear` pipeline stage to support
+  geospatial queries.
+
 - :agg:group:`$min` operator only considers non-null and existing field
   values. If all the values for a field are ``null`` or are missing,
   the operator returns ``null`` for the minimum value.
@@ -482,6 +491,3 @@ improved performance for the :doc:`Aggregation Framework
   portion of a date.
 
 - The new :agg:expression:`$concat` operator concatenates array of strings.
-
-- The new :agg:pipeline:`$geoNear` pipeline stage to supports
-  geospatial queries.