From b314c13882c5295d64b3fb1adefd35ccc2b555b5 Mon Sep 17 00:00:00 2001 From: Alex Dadgar Date: Thu, 28 Sep 2017 04:54:40 -0700 Subject: [PATCH] Fix spelling errors (#3390) --- website/source/api/auth/aws/index.html.md | 4 ++-- website/source/api/secret/aws/index.html.md | 2 +- website/source/api/secret/ssh/index.html.md | 2 +- website/source/api/system/replication-dr.html.md | 2 +- website/source/docs/secrets/aws/index.html.md | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/website/source/api/auth/aws/index.html.md b/website/source/api/auth/aws/index.html.md index 1856835aeb..fb7147a680 100644 --- a/website/source/api/auth/aws/index.html.md +++ b/website/source/api/auth/aws/index.html.md @@ -406,7 +406,7 @@ Returns the previously configured periodic whitelist tidying settings. | Method | Path | Produces | | :------- | :--------------------------- | :--------------------- | -| `GET` | `/auth/aws/config/tidy/identity-whitelist` | `200 applicaiton/json` | +| `GET` | `/auth/aws/config/tidy/identity-whitelist` | `200 application/json` | ### Sample Request @@ -484,7 +484,7 @@ Returns the previously configured periodic blacklist tidying settings. | Method | Path | Produces | | :------- | :--------------------------- | :--------------------- | -| `GET` | `/auth/aws/config/tidy/roletag-blacklist` | `200 applicaiton/json` | +| `GET` | `/auth/aws/config/tidy/roletag-blacklist` | `200 application/json` | ### Sample Request diff --git a/website/source/api/secret/aws/index.html.md b/website/source/api/secret/aws/index.html.md index 5e9236c493..825604bc58 100644 --- a/website/source/api/secret/aws/index.html.md +++ b/website/source/api/secret/aws/index.html.md @@ -294,7 +294,7 @@ role must be created before queried. ### Parameters - `name` `(string: )` – Specifies the name of the role to generate - credentials againts. This is part of the request URL. + credentials against. This is part of the request URL. ### Sample Request diff --git a/website/source/api/secret/ssh/index.html.md b/website/source/api/secret/ssh/index.html.md index 37da8a4a0d..2adc4d6562 100644 --- a/website/source/api/secret/ssh/index.html.md +++ b/website/source/api/secret/ssh/index.html.md @@ -197,7 +197,7 @@ This endpoint creates or updates a named role. - `key_id_format` `(string: "")` – When supplied, this value specifies a custom format for the key id of a signed certificate. The following variables are - availble for use: '{{token_display_name}}' - The display name of the token used + available for use: '{{token_display_name}}' - The display name of the token used to make the request. '{{role_name}}' - The name of the role signing the request. '{{public_key_hash}}' - A SHA256 checksum of the public key that is being signed. e.g. "custom-keyid-{{token_display_name}}", diff --git a/website/source/api/system/replication-dr.html.md b/website/source/api/system/replication-dr.html.md index 46e0ef59c6..3fef71747b 100644 --- a/website/source/api/system/replication-dr.html.md +++ b/website/source/api/system/replication-dr.html.md @@ -263,7 +263,7 @@ This endpoint promotes the DR secondary cluster to DR primary. For data safety a security reasons, new secondary tokens will need to be issued to other secondaries, and there should never be more than one primary at a time. -If the DR secondary's primary cluster is also in a performace replication set, +If the DR secondary's primary cluster is also in a performance replication set, the DR secondary will be promoted into that replication set. Care should be taken when promoting to ensure multiple performance primary clusters are not activate at the same time. diff --git a/website/source/docs/secrets/aws/index.html.md b/website/source/docs/secrets/aws/index.html.md index 972d203892..c525daccac 100644 --- a/website/source/docs/secrets/aws/index.html.md +++ b/website/source/docs/secrets/aws/index.html.md @@ -38,7 +38,7 @@ $ vault write aws/config/root \ ``` *Note that `root` does not mean it needs to be your AWS account's root credentials, and it -probably should not be. It is also unnecessary in many cases as Vault will use normal AWS credential mechanisms (instance profile, env vars, etc.) when possible. If you need to use static credentails, create an IAM user with permissions to manage IAM and STS. +probably should not be. It is also unnecessary in many cases as Vault will use normal AWS credential mechanisms (instance profile, env vars, etc.) when possible. If you need to use static credentials, create an IAM user with permissions to manage IAM and STS. See below for the specific actions required.* The following parameters are required: