From 76e78605a994e8bd31cb168b25d26e16818cedfe Mon Sep 17 00:00:00 2001 From: Rob Taylor Date: Mon, 8 Jun 2020 16:17:26 +0100 Subject: [PATCH] Fixed minor typo in secrets documentation page (#8856) --- website/pages/docs/secrets/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/pages/docs/secrets/index.mdx b/website/pages/docs/secrets/index.mdx index 09b89b324..70b2213e6 100644 --- a/website/pages/docs/secrets/index.mdx +++ b/website/pages/docs/secrets/index.mdx @@ -65,7 +65,7 @@ storage. This is a lot like a [chroot](https://en.wikipedia.org/wiki/Chroot). When a secrets engine is enabled, a random UUID is generated. This becomes the data root for that engine. Whenever that engine writes to the physical storage layer, it is prefixed with that UUID folder. Since the Vault storage layer -doesn't support relative access (such as `../`), this makes it impossible for a +doesn't support relative access (such as `../`), this makes it impossible for an enabled secrets engine to access other data. This is an important security feature in Vault - even a malicious engine