mirrors/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-05-05 12:26:34 +02:00
Code Issues Projects Releases Wiki Activity

typo corrections - spelling and grammar (#24625)

Browse Source 
* typo corrections - spelling

* spelling and grammar
This commit is contained in:
Andy Assareh 2024-01-04 09:50:42 -08:00 committed by GitHub
parent cf07c3d497
commit ab2e0e5a28
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/content/api-docs/secret/transit.mdx
View File

@ -589,9 +589,9 @@ $ curl \
## Securely export key
This endpoint returns a wrapped copy of the `source` key, protected by the
`destination` key using BYOK method accepted by the
`destination` key using the BYOK method accepted by the
`/transit/keys/:name/import` API. This allows an operator using two separate
Vault instances to secure established shared key material, withing exposing
Vault instances to secure established shared key material, without exposing
either key in plaintext and needing to run a manual BYOK import using the
CLI helper utility.

2
website/content/api-docs/system/auth.mdx
View File

@ -136,7 +136,7 @@ For example, enable the "foo" auth method will make it accessible at
- `plugin_version` `(string: "")` – Specifies the semantic version of the plugin
to use, e.g. "v1.0.0". If unspecified, the server will select any matching
unversioned plugin that may have been registered, the latest versioned plugin
registered, or a built-in plugin in that order of precendence.
registered, or a built-in plugin in that order of precedence.
Additionally, the following options are allowed in Vault open-source, but
relevant functionality is only supported in Vault Enterprise:

2
website/content/api-docs/system/mounts.mdx
View File

@ -169,7 +169,7 @@ This endpoint enables a new secrets engine at the given path.
- `plugin_version` `(string: "")` – Specifies the semantic version of the plugin
to use, e.g. "v1.0.0". If unspecified, the server will select any matching
unversioned plugin that may have been registered, the latest versioned plugin
registered, or a built-in plugin in that order of precendence.
registered, or a built-in plugin in that order of precedence.
- `allowed_managed_keys` `(array: [])` - List of managed key registry entry names
that the mount in question is allowed to access.

2
website/content/docs/concepts/user-lockout.mdx
View File

@ -11,7 +11,7 @@ description: >-
@include 'user-lockout.mdx'
## Precendence
## Precedence
The precedence for user lockout configuration is as follows:

2
website/content/docs/platform/k8s/csi/configurations.mdx
View File

@ -48,7 +48,7 @@ If installing via the helm chart, they can be set using e.g.
requests. Can also be specified via the `VAULT_NAMESPACE` environment variable.
- `-vault-tls-ca-cert` `(string: "")` - (v1.1.0+) Path on disk to a single
PEM-encoded CA certificate to trust for Vault. Takes precendence over
PEM-encoded CA certificate to trust for Vault. Takes precedence over
`-vault-tls-ca-directory`. Can also be specified via the `VAULT_CACERT`
environment variable.