anchor.diff:  
   This is the process where a node uses the discovery mechanisms to find
   other nodes. There is support for both multicast and unicast based
  -discovery (can be used in conjunction as well).
  +discovery (these mechanisms can be used in conjunction as well).
   
   [float]
   [[multicast]]
   ===== Multicast
   
   Multicast ping discovery of other nodes is done by sending one or more
  -multicast requests where existing nodes that exists will receive and
  +multicast requests which existing nodes will receive and
   respond to. It provides the following settings with the
   `discovery.zen.ping.multicast` prefix:
   
  
positive.code: 
  As part of the initial ping process a master of the cluster is either
  elected or joined to. This is done automatically. The
  `discovery.zen.ping_timeout` (which defaults to `3s`) allows to
  configure the election to handle cases of slow or congested networks
  (higher values assure less chance of failure). Once a node joins, it
  will send a join request to the master (`discovery.zen.join_timeout`)
  with a timeout defaulting at 20 times the ping timeout.
  
negative.code: `true`), it will not be allowed to become a master (`node.master` is
  automatically set to `false`).
  
  The `discovery.zen.minimum_master_nodes` sets the minimum
  number of master eligible nodes a node should "see" in order to operate
  within the cluster. Its recommended to set it to (N/2)+1, rounding down to
  the nearest integer, when running more than 2 nodes in the cluster (where N is 
  