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

* DOCSP-16317 doc max query capacity when running currentOp queries

* DOCSP-16317 updates for feedback

Author: kanchana-mongodb

source/admin/determine-query-status.txt

@@ -13,13 +13,17 @@ 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. 
+:manual:`$currentOp </reference/operator/aggregation/currentOp/>` must 
+be run against the ``admin`` database. 
+
+.. note:: 
+
+   .. include:: /includes/fact-currentop-query-caveat.rst
 
 .. _adl-currentop-syntax: 
 

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

@@ -0,0 +1,5 @@
+If your aggregation pipeline only contains the :ref:`$currentOp 
+<determine-query-status>` stage, {+adl+} doesn't enforce the limit on 
+the maximum number of simultaneous queries. You can run queries that 
+only contain the :ref:`$currentOp <determine-query-status>` stage even 
+after you reach the maximum number of simultaneous queries.

source/supported-unsupported/limitations.txt

@@ -41,3 +41,7 @@ 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