upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-05-28 04:10:44 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Merge pull request #154 from leocassarani/patch-3

Browse source 
Fix typo in docs: "it's" -> "its"
This commit is contained in:
Seth Vargo 2015-05-07 13:31:03 -04:00
commit 1697cf2a8c
2 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
website/source/docs/internals/architecture.html.md
View file

@ -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.

2
website/source/docs/internals/index.html.md
View file

@ -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