mirror of
https://github.com/hashicorp/vault.git
synced 2026-06-11 01:42:06 -04:00
Fix typos in architecture page (#16978)
Some minor typos fix after I read the whole page.
This commit is contained in:
parent
b67778dfe0
commit
cfe3c61dce
1 changed files with 2 additions and 2 deletions
|
|
@ -6,7 +6,7 @@ description: Learn about the internal architecture of Vault.
|
|||
|
||||
# Architecture
|
||||
|
||||
Vault is an intricate system with numerous distinct components. This page details the system architecture and hopes to assist Vault users and developers to build a mental model while understanding the theory of operaton.
|
||||
Vault is an intricate system with numerous distinct components. This page details the system architecture and hopes to assist Vault users and developers to build a mental model while understanding the theory of operation.
|
||||
|
||||
~> **Note:** This page covers the technical details of Vault. The descriptions and elements contained within are for users that wish to learn about Vault without having to reference the source code. Although not required, we encourage all users and operators to review the provided information before using Vault due to its significance in an environment.
|
||||
|
||||
|
|
@ -78,7 +78,7 @@ policies are used to authorize the client request. The request is then routed to
|
|||
secret. The expiration manager automatically revokes the secret if a client allows the lease to expire.
|
||||
|
||||
The core logs requests and responses to the audit broker, distributing the requests to all configured audit devices. Outside of the request
|
||||
flow, the core performs specific background activities. Lease management is critical, allowig expired client tokens or secrets to be revoked automatically. Additionally, Vault handles specific partial-failure cases by using write-ahead logging with a rollback manager. This is managed transparently within the core and is not user-visible.
|
||||
flow, the core performs specific background activities. Lease management is critical, allowing expired client tokens or secrets to be revoked automatically. Additionally, Vault handles specific partial-failure cases by using write-ahead logging with a rollback manager. This is managed transparently within the core and is not user-visible.
|
||||
|
||||
# Resources
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue