anchor.diff:      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 
  +.. If you secured the keystore or the private key with a password, add that password to a secure
   setting in {es}.
   +
   --
  
positive.code: <<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` 
  setting, which defaults to 5 seconds.
  ===============================
  
negative.code: --
  
  . Verify that you've copied the output files to the appropriate locations, as
  specified in the readme files.
  +
  --
  For example, copy the `http.p12` file from the `elasticsearch` folder into a
  directory within the {es} configuration directory on each node. If you chose to
  generate one certificate per node, copy the appropriate `http.p12` file to each
  node. If you want to use {kib} to access this cluster, copy the
  `elasticsearch-ca.pem` file from the `kibana` folder into the {kib}
  