From 71b481ba4045b208b347c235e081fd2b37e90875 Mon Sep 17 00:00:00 2001 From: Stig Lindqvist Date: Wed, 6 Jul 2016 17:57:22 +1200 Subject: [PATCH] Correcting grammar --- website/source/docs/config/index.html.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/config/index.html.md b/website/source/docs/config/index.html.md index 0e576675f..efe129c0c 100644 --- a/website/source/docs/config/index.html.md +++ b/website/source/docs/config/index.html.md @@ -75,7 +75,7 @@ Disabling `mlock` is not recommended unless the systems running Vault only use encrypted swap or do not use swap at all. Vault only supports memory locking on UNIX-like systems (Linux, FreeBSD, Darwin, etc). Non-UNIX like systems (e.g. Windows, NaCL, Android) lack the primitives to keep a process's -entire memory address space from spilling disk and is therefore automatically +entire memory address space from spilling to disk and is therefore automatically disabled on unsupported platforms. On Linux, to give the Vault executable the ability to use the `mlock` syscall