Skip to content

Commit

Permalink
Update KV Secrets Engine index (#10933)
Browse files Browse the repository at this point in the history
Just a suggestion on how to perhaps improve the language as I found myself re-reading the sentences due to the missing "either ... or ..." having been _told_ that it `can be run in two modes`.
  • Loading branch information
onematchfox authored Feb 17, 2021
1 parent d69a12c commit bc8bdb2
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions website/content/docs/secrets/kv/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,15 +7,15 @@ description: The KV secrets engine can store arbitrary secrets.

# KV Secrets Engine

The `kv` secrets engine is used to store arbitrary secrets within the
configured physical storage for Vault. This backend can be run in one of two
modes. It can be a generic Key-Value store that stores one value for a key.
Versioning can be enabled and a configurable number of versions for each key
will be stored.
The `kv` secrets engine is a generic Key-Value store used to store arbitrary
secrets within the configured physical storage for Vault. This backend can be
run in one of two modes; either it can be configured to store a single value
for a key or, versioning can be enabled and a configurable number of versions
for each key will be stored.

## KV Version 1

When running the `kv` secrets backend non-versioned only the most recently
When running the `kv` secrets backend non-versioned, only the most recently
written value for a key will be preserved. The benefits of non-versioned `kv`
is a reduced storage size for each key since no additional metadata or history
is stored. Additionally, requests going to a backend configured this way will be
Expand Down

0 comments on commit bc8bdb2

Please sign in to comment.