From db10a974f63d3b8bc07d2da5b255edc2a71712a9 Mon Sep 17 00:00:00 2001 From: Leo Cassarani Date: Thu, 7 May 2015 11:06:46 +0000 Subject: [PATCH] Fix typo in docs: "it's" -> "its" [ci skip] --- website/source/docs/internals/architecture.html.md | 2 +- website/source/docs/internals/index.html.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/internals/architecture.html.md b/website/source/docs/internals/architecture.html.md index 1160c51f3..9bedd36a5 100644 --- a/website/source/docs/internals/architecture.html.md +++ b/website/source/docs/internals/architecture.html.md @@ -63,7 +63,7 @@ clarify what is being discussed: Secrets always have an associated lease. This means clients cannot assume that the secret contents can be used indefinitely. Vault will revoke a secret at the end of the lease, and an operator may intervene to revoke the secret before the lease is over. This contract - between Vault and it's clients is critical, as it allows for changes in keys and policies + between Vault and its clients is critical, as it allows for changes in keys and policies without manual intervention. * **Server** - Vault depends on a long-running instance which operates as a server. diff --git a/website/source/docs/internals/index.html.md b/website/source/docs/internals/index.html.md index c15aedaf4..f2defdf66 100644 --- a/website/source/docs/internals/index.html.md +++ b/website/source/docs/internals/index.html.md @@ -9,7 +9,7 @@ description: |- # Vault Internals This section covers the internals of Vault and explains the technical -details of how Vault functions, it's architecture and security properties. +details of how Vault functions, its architecture and security properties. -> **Note:** Knowledge of Vault internals is not required to use Vault. If you aren't interested in the internals