anchor.diff:  <<cluster-nodes-info,nodes info API>> For more
   information about any of these settings, see <<security-settings>>.
   
  -* {es} monitors all files such as certificates, keys, keystores, or truststores 
  -that are configured as values of TLS-related node settings. If you update any of 
  -these files (for example, when your hostnames change or your certificates are 
  -due to expire), {es} reloads them. The files are polled for changes at 
  -a frequency determined by the global {es} `resource.reload.interval.high` 
  +* {es} monitors all files such as certificates, keys, keystores, or truststores
  +that are configured as values of TLS-related node settings. If you update any of
  +these files (for example, when your hostnames change or your certificates are
  +due to expire), {es} reloads them. The files are polled for changes at
  +a frequency determined by the global {es} `resource.reload.interval.high`
   setting, which defaults to 5 seconds.
   ===============================
  
positive.code:     must be a location within the {es} configuration directory.
  --
  
  .. If you secured the keystore or the private key with a password, add that password to a secure 
  setting in {es}.
  +
  --
  
negative.code: Enabling TLS on the HTTP layer is strongly recommended, but is not required.
  
  IMPORTANT: In a <<dev-vs-prod-mode,production environment>>, some {es} features
  such as tokens will be disabled unless you enable TLS on the HTTP
  layer.
  
  If you enable TLS on the HTTP layer in {es}, you might need to make
  