anchor.diff:  require:
   
   * One <<modules-discovery-quorums,elected master node>> node
  +* At least one node for each <<modules-node,role>>.
   * At least one copy of every <<scalability,shard>>.
   
  -We also recommend adding a new node to the cluster for each
  -<<modules-node,role>>.
  -
  -A resilient cluster requires redundancy for every required cluster component,
  -except the elected master node. For resilient clusters, we recommend:
  -
  -* One elected master node
  +A resilient cluster requires redundancy for every required cluster component.
  +This means a resilient cluster must have:
  +
   * At least three master-eligible nodes
   * At least two nodes of each role
   * At least two copies of each shard (one primary and one or more replicas)
  
positive.code: nodes is the elected master of the cluster. The cluster can tolerate the loss of
  the other master-ineligible node. If you don't set `node.master: false` on one
  node, both nodes are master-eligible. This means both nodes are required for a
  master election. This election will fail if your cluster cannot reliably
  tolerate the loss of either node.
  
  By default, each node is assigned every role. We recommend you assign both nodes
  all other roles except master eligibility. If one node fails, the other node can
  
negative.code: - There are at least two data nodes. 
  - Every index has at least one replica of each shard, in addition to the 
    primary.
  - The cluster has at least three master-eligible nodes, as long as at least two
    of these nodes are not voting-only master-eligible nodes.
  - Clients are configured to send their requests to more than one node or are
    configured to use a load balancer that balances the requests across an
    appropriate set of nodes. The {ess-trial}[Elastic Cloud] service provides such
  