DOCS-15029 :pipeline: -> :group: (#291)

Author: ianf-mongodb

source/reference/operator/aggregation/maxN.txt

@@ -90,7 +90,7 @@ In this example:
   example has only one ``gameId``, ``G1``.
 - ``PlayerD`` has a missing score and ``PlayerE`` has a
   null ``score``. These values are both considered as null.
-- The ``maximumThreeScores`` field is specified as :pipeline:`$maxN` 
+- The ``maximumThreeScores`` field is specified as :group:`$maxN` 
   with ``input : "$score"`` and returned as an array.
 - Since there are only 3 documents with ``scores`` ``maxN`` returns the
   maximum 3  ``score`` fields even though ``n = 4``.
@@ -108,19 +108,19 @@ In this example:
 Comparison of ``$maxN`` and ``$topN`` Accumulators
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Both :pipeline:`$maxN` and :pipeline:`$topN` accumulators can accomplish similar 
+Both :group:`$maxN` and :group:`$topN` accumulators can accomplish similar 
 results.
 
 In general:
 
-- :pipeline:`$maxN` has the advantage of finding maximum values 
+- :group:`$maxN` has the advantage of finding maximum values 
   in no particular sort order. If you want to know the 
-  maximum values for ``n`` documents use :pipeline:`$maxN`.
+  maximum values for ``n`` documents use :group:`$maxN`.
 
 - If guaranteing a particular sort order is a requirement 
-  use :pipeline:`$topN`. 
+  use :group:`$topN`. 
 
-- Use :pipeline:`$topN` if you don't intend on sorting on the output 
+- Use :group:`$topN` if you don't intend on sorting on the output 
   values.
 
 Restrictions
@@ -129,12 +129,12 @@ Restrictions
 Window Function and Aggregation Expression Support
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-You can use :pipeline:`$maxN` as an accumulator.
+You can use :group:`$maxN` as an accumulator.
 
-:pipeline:`$maxN` is supported as an
+:group:`$maxN` is supported as an
 :ref:`aggregation expression <aggregation-expressions>`.
 
-:pipeline:`$maxN` is supported as a 
+:group:`$maxN` is supported as a 
 :pipeline:`window operator <$setWindowFields>`.
 
 Memory Limit Considerations

source/reference/operator/aggregation/minN.txt

@@ -90,7 +90,7 @@ In this example:
   example has only one ``gameId``, ``G1``.
 - ``PlayerD`` has a missing score and ``PlayerE`` has a
   null ``score``. These values are both ignored.
-- The ``minimumThreeScores`` field is specified as :pipeline:`$minN` 
+- The ``minimumThreeScores`` field is specified as :group:`$minN` 
   with ``input : "$score"`` and returned as an array.
 - Since there are only 3 documents with ``scores`` ``minN`` returns 
   the minimum 3  ``score`` fields even though ``n = 4``.
@@ -108,19 +108,19 @@ In this example:
 Comparison of ``$minN`` and ``$bottomN`` Accumulators
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Both :pipeline:`$minN` and :pipeline:`$bottomN` accumulators can accomplish 
+Both :group:`$minN` and :group:`$bottomN` accumulators can accomplish 
 similar results.
 
 In general:
 
-- :pipeline:`$minN` has the advantage of finding minimum values 
+- :group:`$minN` has the advantage of finding minimum values 
   in no particular sort order. If you want to know the 
-  minimum values for ``n`` documents use :pipeline:`$minN`.
+  minimum values for ``n`` documents use :group:`$minN`.
 
 - If guaranteing a particular sort order is a requirement 
-  use :pipeline:`$bottonN`. 
+  use :group:`$bottomN`. 
 
-- Use :pipeline:`$bottomN` if you don't intend on sorting on the output 
+- Use :group:`$bottomN` if you don't intend on sorting on the output 
   values.
 
 Restrictions
@@ -129,12 +129,12 @@ Restrictions
 Window Function and Aggregation Expression Support
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-You can use :pipeline:`$minN` as an accumulator.
+You can use :group:`$minN` as an accumulator.
 
-:pipeline:`$minN` is supported as an
+:group:`$minN` is supported as an
 :ref:`aggregation expression <aggregation-expressions>`.
 
-:pipeline:`$minN` is supported as a 
+:group:`$minN` is supported as a 
 :pipeline:`window operator <$setWindowFields>`.
 
 Memory Limit Considerations