anchor.diff:  [[setup-configuration-memory]]
   ==== Memory Settings
   
  -The Linux kernel tries to use as much memory as possible for file system
  -caches and eagerly swaps out unused application memory, possibly resulting
  +Most operating systems try to use as much memory as possible for file system
  +caches and eagerly swap out unused application memory, possibly resulting
   in the elasticsearch process being swapped. Swapping is very bad for
   performance and for node stability, so it should be avoided at all costs.
   
  
positive.code: The simplest option is to completely disable swap. Usually Elasticsearch
  is the only service running on a box, and its memory usage is controlled
  by the `ES_HEAP_SIZE` environment variable.  There should be no need
  to have swap enabled.  On Linux systems, you can disable swap temporarily
  by running: `sudo swapoff -a`. To disable it permanently, you will need
  to edit the `/etc/fstab` file and comment out any lines that contain the
  word `swap`.
  --
  
  * **Configure `swappiness`**
  
negative.code: --------------
  
  If you see that `mlockall` is `false`, then it means that the the `mlockall`
  request has failed.  The most probable reason, on Linux/Unix systems, is that
  the user running Elasticsearch doesn't have permission to lock memory.  This can 
  be granted by running `ulimit -l unlimited` as `root` before starting Elasticsearch.
  
  Another possible reason why `mlockall` can fail is that the temporary directory
  (usually `/tmp`) is mounted with the `noexec` option. This can be solved by
  