rm feedback

Author: stephmarie17

source/aggregation.txt

@@ -134,22 +134,22 @@ following stages:
     .. output::
        :visible: false
 
-       {"_id"=>"Missing", "count"=>51}
-       {"_id"=>"Queens", "count"=>5656}
-       {"_id"=>"Staten Island", "count"=>969}
-       {"_id"=>"Brooklyn", "count"=>6086}
-       {"_id"=>"Manhattan", "count"=>10259}
-       {"_id"=>"Bronx", "count"=>2338}
+       {"_id"=>"Bronx", "count"=>71}
+       {"_id"=>"Manhattan", "count"=>221}
+       {"_id"=>"Queens", "count"=>204}
+       {"_id"=>"Missing", "count"=>2}
+       {"_id"=>"Staten Island", "count"=>20}
+       {"_id"=>"Brooklyn", "count"=>173}
 
 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 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 by default.
+the MongoDB :manual:`query planner </core/query-plans>` to **explain** it. When
+MongoDB explains an operation, it returns **execution plans** and performance
+statistics. 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 by default.
 
 To explain an aggregation operation, chain the ``explain`` method to the
 ``aggregate`` method.
@@ -181,7 +181,7 @@ from the preceding :ref:`ruby-aggregation-example`:
 Run an Atlas Full-Text Search
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-.. tip:: Only Available on Atlas for MongoDB v4.2 and later
+.. note:: Only Available on Atlas for MongoDB v4.2 and later
 
    This aggregation pipeline operator is only available for collections hosted
    on :atlas:`MongoDB Atlas </>` clusters running v4.2 or later that are
@@ -190,6 +190,14 @@ Run an Atlas Full-Text Search
 To specify a full-text search of one or more fields, you can create a
 ``$search`` pipeline stage.
 
+.. important::
+
+    To run the following example, you must create an Atlas Search index on the ``restaurants``
+    collection that covers the ``name`` field. Then, replace the ``"<your_search_index_name>"``
+    placeholder with the name of the index. 
+
+.. TODO: Add a link in the callout to the Atlas Search index creation guide.
+
 This example creates pipeline stages to perform the following actions:
 
 - Search the ``name`` field for the term ``"Salt"``
@@ -214,14 +222,6 @@ This example creates pipeline stages to perform the following actions:
        {"_id"=>  {"$oid"=> "..."}, "name"=>  "Salt And Fat"}
        {"_id"=>  {"$oid"=>  "..."}, "name"=>  "Salt And Pepper Diner"}
 
-.. important::
-
-    To run the preceding example, you must create an Atlas Search index on the ``restaurants``
-    collection that covers the ``name`` field. Then, replace the ``"<search index name>"``
-    placeholder with the name of the index. 
-
-.. TODO: Add a link in the callout to the Atlas Search index creation guide.
-
 Additional Information
 ----------------------
 

source/includes/aggregation.rb

@@ -4,14 +4,15 @@
   gem 'mongo'
 end
 
-uri = "<connection string URI>"
+uri = '<connection string URI>'
 
 Mongo::Client.new(uri) do |client|
   #start-aggregation
   database = client.use('sample_restaurants')
   restaurants_collection = database[:restaurants]
 
   pipeline = [
+    { '$match' => { 'cuisine' => 'Bakery' } },
     { '$group' => {
       '_id' => '$borough',
       'count' => { '$sum' => 1 }
@@ -36,7 +37,7 @@
   search_pipeline = [
     {
       '$search' => {
-        'index' => 'your_search_index_name',
+        'index' => '<your_search_index_name>',
         'text' => {
           'query' => 'Salt',
           'path' => 'name'