DOCSP-40094: Clarify MongoClient.close() behavior (#898)

* DOCSP-40094: Clarify MongoClient.close() behavior

* RR feedback

* RR feedback 2

(cherry picked from commit b9bccea)

source/faq.txt

@@ -102,9 +102,11 @@ during a load spike than it is to complete every operation.
 When ``MongoClient.close()`` is called by any request, the driver
 closes all idle sockets and closes all sockets that are in
 use as they are returned to the pool. Calling ``MongoClient.close()``
-closes only inactive sockets, so you cannot interrupt or terminate
-any ongoing operations by using this method. The driver closes these
-sockets only when the process completes.
+closes only inactive sockets and does not directly terminate
+any ongoing operations. The driver closes any in-use sockets only when
+the associated operations complete. However, the ``MongoClient.close()``
+method does close existing sessions and transactions, which might indirectly
+affect the behavior of ongoing operations and open cursors.
 
 What Is the Difference Between "connectTimeoutMS", "socketTimeoutMS" and "maxTimeMS"?
 -------------------------------------------------------------------------------------