anchor.diff:  ----------------------
   <1> This setting could also be specified in the `elasticsearch.yml` config file.
   
  -Now, we need to setup _shard allocation awareness_  by telling Elasticsearch
  +Now, we need to set up _shard allocation awareness_  by telling Elasticsearch
   which attributes to use.  This can be configured in the `elasticsearch.yml`
   file on *all* master-eligible nodes, or it can be set (and changed) with the
   <<cluster-update-settings,cluster-update-settings>> API.
  
positive.code: === Shard Allocation Awareness
  
  When running nodes on multiple VMs on the same physical server, on multiple
  racks, or across multiple awareness zones, it is more likely that two nodes on
  the same physical server, in the same rack, or in the same awareness zone will
  crash at the same time, rather than two unrelated nodes crashing
  simultaneously.
  
  
negative.code: -------------------------------------------------------------------
  <1> We must list all possible values that the `zone` attribute can have.
  
  Now, if we start 2 nodes with `node.attr.zone` set to `zone1` and create an
  index with 5 shards and 1 replica. The index will be created, but only the 5
  primary shards will be allocated (with no replicas). Only when we start more
  nodes with `node.attr.zone` set to `zone2` will the replicas be allocated.
  
  The `cluster.routing.allocation.awareness.*` settings can all be updated
  dynamically on a live cluster with the
  