Description

The current description for[ rolling indexes |https://docs.atlas.mongodb.com/data-explorer/indexes/#optional-enable-building-indexes-in-a-rolling-fashion] does not clearly explain the behavior, since one node is removed at a time but multiple nodes can be down at once. 
 
Original text 

Building indexes in a rolling fashion reduces the performance impact of building indexes on replica sets and sharded clusters. To maintain cluster availability, Atlas removes one node from the cluster at a time starting with a secondary.

Please update the description to be something to the effect of:

Building indexes in a rolling fashion reduces the performance impact of building indexes on replica sets and sharded clusters. To maintain cluster availability, Atlas removes one node from the cluster at a time starting with a secondary and maintaining a majority of nodes online at all times.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)