From b47a9e72942719f217f7750df18be36ec21dfc0e Mon Sep 17 00:00:00 2001 From: hc-github-team-secure-vault-core <82990506+hc-github-team-secure-vault-core@users.noreply.github.com> Date: Fri, 23 Sep 2022 09:01:14 -0400 Subject: [PATCH] backport of commit 7f22056686b5a8e71c66e73eeaab4403809b791c (#17039) Co-authored-by: Troy Ready --- website/content/docs/internals/integrated-storage.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/internals/integrated-storage.mdx b/website/content/docs/internals/integrated-storage.mdx index 6361d67fab307..e6ac6c542b622 100644 --- a/website/content/docs/internals/integrated-storage.mdx +++ b/website/content/docs/internals/integrated-storage.mdx @@ -73,7 +73,7 @@ attempts to replicate to a quorum of followers. Once the log entry is considered _committed_, it can be _applied_ to a finite state machine. The finite state machine is application specific; in Vault's case, we use [BoltDB](https://github.com/etcd-io/bbolt) to maintain a cluster state. Vault's writes -are block until they are _committed_ and _applied_. +are blocked until they are _committed_ and _applied_. It would be undesirable to allow a replicated log to grow in an unbounded fashion. Raft provides a mechanism by which the current state is snapshotted and the