JS feedback

Author: norareidy

source/aggregation.txt

@@ -67,7 +67,7 @@ You can use aggregation operations to perform the following actions:
 Limitations
 ~~~~~~~~~~~
 
-Keep the following limitations in mind when using aggregation operations:
+Consider the following limitations when performing aggregation operations:
 
 - Returned documents cannot violate the
   :manual:`BSON document size limit </reference/limits/#mongodb-limit-BSON-Document-Size>`
@@ -76,11 +76,11 @@ Keep the following limitations in mind when using aggregation operations:
   limit by creating an options array that sets the ``allowDiskUse`` option to ``true``
   and passing the array to the ``MongoDB\Collection::aggregate()`` method.
 
-.. important:: $graphLookup Exception
+  .. important:: $graphLookup Exception
 
-   The :manual:`$graphLookup
-   </reference/operator/aggregation/graphLookup/>` stage has a strict
-   memory limit of 100 megabytes and ignores the ``allowDiskUse`` option.
+     The :manual:`$graphLookup
+     </reference/operator/aggregation/graphLookup/>` stage has a strict
+     memory limit of 100 megabytes and ignores the ``allowDiskUse`` option.
 
 .. _php-aggregation-example:
 
@@ -118,7 +118,7 @@ of New York. To do so, it uses an aggregation pipeline that contains the followi
 
    .. output:: 
       :visible: false
-      
+
       {"_id":"Brooklyn","count":173}
       {"_id":"Queens","count":204}
       {"_id":"Bronx","count":71}
@@ -132,13 +132,13 @@ Explain an Aggregation
 To view information about how MongoDB executes your operation, you can
 instruct the MongoDB query planner to **explain** it. When MongoDB explains
 an operation, it returns **execution plans** and performance statistics.
-An execution plan is a potential way MongoDB can complete an operation.
+An execution plan is a potential way in which MongoDB can complete an operation.
 When you instruct MongoDB to explain an operation, it returns both the
 plan MongoDB executed and any rejected execution plans.
 
 To explain an aggregation operation, run the ``explain`` database command by passing
-the command information to the ``MongoDB\Database::command()`` method. You must set the
-``aggregate``, ``pipeline``, and ``cursor`` fields of the ``explain`` command document
+the command information to the ``MongoDB\Database::command()`` method. You must specify the
+``aggregate``, ``pipeline``, and ``cursor`` fields in the ``explain`` command document
 to explain the aggregation.
 
 The following example instructs MongoDB to explain the aggregation operation from the
@@ -169,18 +169,21 @@ Additional Information
 MongoDB Server Manual
 ~~~~~~~~~~~~~~~~~~~~~
 
-To view a full list of expression operators, see :manual:`Aggregation
-Operators. </reference/operator/aggregation/>`
+To learn more about the topics discussed in this guide, see the following
+pages in the {+mdb-server+} manual:
+
+- To view a full list of expression operators, see :manual:`Aggregation
+  Operators </reference/operator/aggregation/>`.
 
-To learn about assembling an aggregation pipeline and view examples, see
-:manual:`Aggregation Pipeline. </core/aggregation-pipeline/>`
+- To learn about assembling an aggregation pipeline and to view examples, see
+  :manual:`Aggregation Pipeline </core/aggregation-pipeline/>`.
 
-To learn more about creating pipeline stages, see :manual:`Aggregation
-Stages. </reference/operator/aggregation-pipeline/>`
+- To learn more about creating pipeline stages, see :manual:`Aggregation
+  Stages </reference/operator/aggregation-pipeline/>`.
 
-To learn more about explaining MongoDB operations, see
-:manual:`Explain Output </reference/explain-results/>` and
-:manual:`Query Plans. </core/query-plans/>`
+- To learn more about explaining MongoDB operations, see
+  :manual:`Explain Output </reference/explain-results/>` and
+  :manual:`Query Plans </core/query-plans/>`.
 
 .. TODO:
  Aggregation Tutorials