DOCSP-30478 updated faq indexes to describe new behavior (#3385)

* DOCSP-30478 updated faq indexes to describe new behavior

* fixed wording, added terms and correct format

* simple edits

Author: gmiller-mdb

source/faq/indexes.txt

@@ -54,11 +54,13 @@ operation on a :term:`primary` or standalone :binary:`~bin.mongod`, use
 :method:`db.killOp()`. The partially built index will be
 deleted.
 
-You cannot terminate a *replicated* index build on secondary members of
-a replica set. You must first :method:`drop <db.collection.dropIndex()>`
-the index on the primary. The secondaries will replicate the drop
-operation and drop the indexes *after* the index build completes.
-All further replication blocks behind the index build and drop. 
+You cannot terminate a replicated index build on secondary members of a replica 
+set. You must first drop the index on the primary. Starting in version 4.4, the 
+primary stops the index build and creates an associated ``abortIndexBuild`` 
+:term:`oplog` entry. Secondaries that replicate the ``abortIndexBuild`` oplog 
+entry stop the in-progress index build and discard the build job.
+
+To learn more, see :ref:`dropIndexes-cmd-index-builds`. 
 
 How do I see what indexes exist on a collection?
 ------------------------------------------------