anchor.diff:  [float]
   ==== Using the file-based discovery plugin
   
  -The file-based discovery plugin provides the ability to specify the 
  +The file-based discovery plugin provides the ability to specify the
   unicast hosts list through a simple `unicast_hosts.txt` file that can
   be dynamically updated at any time. To enable, add the following in `elasticsearch.yml`:
   
  
positive.code: [float]
  ==== unicast_hosts.txt file format
  
  The format of the file is to specify one unicast host entry per line.  
  Each unicast host entry consists of the host (host name or IP address) and
  an optional transport port number.  If the port number is specified, is must 
  come immediately after the host (on the same line) separated by a `:`. 
  If the port number is not specified, a default value of 9300 is used.  
  
  For example, this is an example of `unicast_hosts.txt` for a cluster with
  four nodes that participate in unicast discovery, some of which are not
  
negative.code: ----
  
  This plugin simply provides a facility to supply the unicast hosts list for
  zen discovery through an external file that can be updated at any time by a side process.
  
  For example, this gives a convenient mechanism for an Elasticsearch instance
  that is  run in docker containers to be dynamically supplied a list of IP
  addresses to connect to for zen discovery when those IP addresses may not be
  known at node startup.
  
  Note that the file-based discovery plugin is meant to augment the unicast
  hosts list in `elasticsearch.yml` (if specified), not replace it.  Therefore,
  