anchor.diff:  -----------------------
   
   TIP: When using the `.zip` or `.tar.gz` distributions, the `path.data` setting
  -should be configured to locate the data directory outside the Elasticsearch
  -home directory, so that the home directory can be deleted without deleting
  -your data! The RPM and Debian distributions do this for you already.
  +should be configured to locate the data directory outside the {es} home
  +directory, so that the home directory can be deleted without deleting your data!
  +The RPM and Debian distributions do this for you already.
   
   
   [float]
  
positive.code: 
  [float]
  [[master-node]]
  === Master Eligible Node
  
  The master node is responsible for lightweight cluster-wide actions such as
  creating or deleting an index, tracking which nodes are part of the cluster,
  
negative.code: [[modules-node]]
  == Node
  
  Any time that you start an instance of Elasticsearch, you are starting a _node_. 
  A collection of connected nodes is called a <<modules-cluster,cluster>>. If you 
  are running a single node of {es}, then you have a cluster of one node.
  
  Every node in the cluster can handle <<modules-http,HTTP>> and
  <<modules-transport,Transport>> traffic by default. The transport layer is used
  exclusively for communication between nodes; the HTTP layer is used by REST
  clients.
  
  All nodes know about all the other nodes in the cluster and can forward client
  requests to the appropriate node. 
  