Revert "DOCSP-16317 doc max query capacity when running currentOp queries (#159)" (#160)

This reverts commit a22c565.

Author: kanchana-mongodb

source/admin/determine-query-status.txt

@@ -13,17 +13,13 @@ Determine Status of {+data-lake-short+} Queries
    :class: singlecol
 
 You can determine the status of a running query using  
-:manual:`$currentOp </reference/operator/aggregation/currentOp/>` 
-(aggregation). To run :manual:`$currentOp 
+:manual:`$currentOp </reference/operator/aggregation/currentOp/>` (aggregation). 
+To run :manual:`$currentOp 
 </reference/operator/aggregation/currentOp/index.html#pipe._S_currentOp>`, use 
 the :manual:`db.aggregate 
 </reference/method/db.aggregate/#db.aggregate>` helper. 
-:manual:`$currentOp </reference/operator/aggregation/currentOp/>` must 
-be run against the ``admin`` database. 
-
-.. note:: 
-
-   .. include:: /includes/fact-currentop-query-caveat.rst
+:manual:`$currentOp </reference/operator/aggregation/currentOp/>` must be 
+run against the ``admin`` database. 
 
 .. _adl-currentop-syntax: 
 

source/includes/fact-currentop-query-caveat.rst

@@ -41,7 +41,3 @@ regions only:
 * Having more than 60 *guaranteed* simultaneous connections per region 
   to a {+dl+} 
 * Running more than 30 simultaneous queries on your {+dl+}
-
-  .. note:: 
-
-     .. include:: /includes/fact-currentop-query-caveat.rst