DOCSP-26186: maxTimeMS explanation (#465)

* DOCSP-26186: specify that maxTimeMS applies to operations only

* first pass fixes

* DB suggestion

Author: rustagir

source/faq.txt

@@ -51,9 +51,11 @@ What Is the Difference Between "connectTimeoutMS", "socketTimeoutMS" and "maxTim
 
    * - Setting
      - Description
-   * - connectTimeoutMS
-     - ``connectTimeoutMS`` is a :ref:`connection option <node-connection-options>` that sets the time, in milliseconds,
-       for an individual connection from your connection pool to establish a TCP connection to the MongoDB server before
+   * - **connectTimeoutMS**
+     - ``connectTimeoutMS`` is a :ref:`connection option
+       <node-connection-options>` that sets the time, in milliseconds,
+       for an individual connection from your connection pool to
+       establish a TCP connection to the MongoDB server before
        timing out.
 
        .. tip::
@@ -62,16 +64,18 @@ What Is the Difference Between "connectTimeoutMS", "socketTimeoutMS" and "maxTim
           connection to a MongoDB server, use the ``serverSelectionTimeoutMS`` option instead.
 
        **Default:** 10000
-   * - socketTimeoutMS
+   * - **socketTimeoutMS**
      - ``socketTimeoutMS`` specifies the amount of time the driver waits
        for an inactive socket before closing it. The default value is to
        never time out the socket. This option applies only to sockets that
        have already been connected.
-   * - maxTimeMS
-     - `maxTimeMS <{+api+}/classes/FindCursor.html#maxTimeMS>`__ is the maximum
-       amount of time the server should wait for an operation to complete
-       after it has reached the server. If an operation runs over the
-       specified time limit, it returns a timeout error.
+   * - **maxTimeMS**
+     - `maxTimeMS <{+api+}/classes/FindCursor.html#maxTimeMS>`__
+       specifies the maximum amount of time the server 
+       should wait for an operation to complete after it has reached the
+       server. If an operation runs over the specified time limit, it
+       returns a timeout error. You can pass ``maxTimeMS`` only to an
+       individual operation or to a cursor.
 
 To specify the optional settings for your ``MongoClient``, declare one or
 more available settings in the ``options`` object of the constructor as
@@ -88,6 +92,13 @@ To see all the available settings, see the
 `MongoClientOptions <{+api+}/interfaces/MongoClientOptions.html>`__
 API Documentation.
 
+To specify ``maxTimeMS``, chain the ``maxTimeMS()`` method with a
+timeout specification to an operation that returns a ``Cursor``:
+
+.. code-block:: javascript
+
+   const cursor = collection.find({}).maxTimeMS(50);
+
 How Can I Prevent the Driver From Hanging During Connection or From Spending Too Long Trying to Reach Unreachable Replica Sets?
 -------------------------------------------------------------------------------------------------------------------------------
 
@@ -168,22 +179,8 @@ How Can I Prevent Long-Running Operations From Slowing Down the Server?
 -----------------------------------------------------------------------
 
 You can prevent long-running operations from slowing down the server by
-specifying a timeout value. You can use the ``maxTimeMS`` option setting in
-your ``MongoClient`` constructor to apply this to all the operations
-called by the client, or chain the ``maxTimeMS()`` method to an operation that
-returns a ``Cursor`` to apply to that specific one.
-
-To specify the optional ``maxTimeMS`` setting for your ``MongoClient``,
-declare it in the ``options`` object of the constructor as follows:
-
-.. code-block:: javascript
-
-   const client = new MongoClient(uri, {
-     connectTimeoutMS: <integer value>,
-     socketTimeoutMS: <integer value>,
-     maxTimeMS: <integer value>,
-   });
-
+specifying a timeout value. You can chain the ``maxTimeMS()`` method to
+an operation that returns a ``Cursor`` to set a timeout on a specific action.
 
 The following example shows how you can chain the ``maxTimeMS()`` method
 to an operation that returns a ``Cursor``:
@@ -309,7 +306,6 @@ to reach ``server1``, ``server2``, and ``server3``.
      ]
    }
 
-
 If you are unable to find the answer to your question here, try our forums and
 support channels listed in the :doc:`Issues and Help <issues-and-help>`
 section.