anchor.diff:  --------------------------------------------------
   // CONSOLE
   
  -Reset settings will not be included in the cluster response. So
  -the response for the last example will be:
  +The response does not include settings that have been reset:
   
   [source,js]
   --------------------------------------------------
  
positive.code: --------------------------------------------------
  // CONSOLE
  
  Cluster wide settings can be returned using:
  
  [source,js]
  --------------------------------------------------
  GET /_cluster/settings
  --------------------------------------------------
  // CONSOLE
  
  [float]
  === Precedence of settings
  
  Transient cluster settings take precedence over persistent cluster settings,
  which take precedence over settings configured in the `elasticsearch.yml`
  config file.
  
  For this reason it is preferrable to  use the `elasticsearch.yml` file only
  for local configurations, and set all cluster-wider settings with the
  `settings` API.
  
  A list of dynamically updatable settings can be found in the
  <<modules,Modules>> documentation.
  
  
negative.code: [[cluster-update-settings]]
  == Cluster Update Settings
  
  Use this API to review and change cluster-wide settings. 
  
  To review cluster settings:
  
  [source,js]
  --------------------------------------------------
  GET /_cluster/settings
  --------------------------------------------------
  // CONSOLE
  
  Updates to settings can be persistent, meaning they apply across restarts, or transient, where they don't 
  survive a full cluster restart. Here is an example of a persistent update:
  
  [source,js]
  --------------------------------------------------
  