anchor.diff:  // CONSOLE
   
   If you see that `mlockall` is `false`, then it means that the `mlockall`
  -request has failed.  You will also see a line with more information in the
  -logs with the words `Unable to lock JVM Memory`.
  +request has failed.  You will also see a line with more information in the logs
  +with the words `Unable to lock JVM Memory`.
   
   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 as follows:
  +Elasticsearch doesn't have permission to lock memory.  This can be granted as
  +follows:
   
   `.zip` and `.tar.gz`::
   
  
positive.code: RPM and Debian::
  
    Set `MAX_LOCKED_MEMORY` to `unlimited` in the
    <<sysconfig,system configuration file>> (or see below for systems using `systemd`).
  
  Systems using `systemd`::
  
    Set `LimitMEMLOCK` to `infinity` in the <<systemd,systemd configuration>>.
  
  
  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
  
negative.code: --------------
  
  or setting this JVM flag in the jvm.options configuration file.
  