DOCS-12247: terminate-running-operations

Author: Kay Kim

source/reference/command/killOp.txt

@@ -62,7 +62,8 @@ that span shards in a cluster. The :dbcommand:`killOp` command from the
 operation to be killed is a write operation.
 
 For information on how to list sharding operations that are active on a
-mongos, see the ``localOps`` parameter in :pipeline:`$currentOp`.
+:binary:`~bin.mongos`, see the ``localOps`` parameter in
+:pipeline:`$currentOp`.
 
 For more information and examples on killing operations on a sharded
 cluster, see:

source/tutorial/terminate-running-operations.txt

@@ -87,5 +87,22 @@ the target operation by operation ID.
 
 .. include:: /includes/extracts/warning-terminating-ops-method.rst
 
-.. related:: To return a list of running operations see
-   :method:`db.currentOp()`.
+Sharded Cluster
+````````````````
+
+Starting in MongoDB 4.0, the :dbcommand:`killOp` command can be run on
+a :binary:`~bin.mongos` and can kill queries (i.e. read operations)
+that span shards in a cluster. The :dbcommand:`killOp` command from the
+:binary:`~bin.mongos` does not propagate to the shards when the
+operation to be killed is a write operation.
+
+For more information on killing operations on a sharded cluster, see:
+
+- :ref:`kill-read-ops-sharded-cluster`
+
+- :ref:`kill-write-ops-sharded-cluster`
+
+For information on how to list sharding operations that are active on a
+:binary:`~bin.mongos`, see the ``localOps`` parameter in
+:pipeline:`$currentOp`.
+