From 462f98673fc757d5797e6ef1b7768fa48417c81b Mon Sep 17 00:00:00 2001 From: emily Date: Thu, 26 Apr 2018 13:54:19 -0700 Subject: [PATCH] fix docs (#4466) --- website/source/docs/secrets/gcp/index.html.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/secrets/gcp/index.html.md b/website/source/docs/secrets/gcp/index.html.md index 01983d5386..4d95842a99 100644 --- a/website/source/docs/secrets/gcp/index.html.md +++ b/website/source/docs/secrets/gcp/index.html.md @@ -59,12 +59,12 @@ Success! Enabled the gcp secrets engine at: gcp/ You will need to set up the secrets engine with: * **[Config](#config)**: General config, including credentials that Vault will need to make calls - to GCP APIs (either explicitly or using Application Default Credentials), lease defaults, etc. Example: + to GCP APIs (either explicitly or using Application Default Credentials), lease defaults, etc. * **[Rolesets](#rolesets)**: Generated credentials will need to be associated with sets of [IAM roles](https://cloud.google.com/iam/docs/understanding-roles) on specific GCP resources. Rolesets have an associated `secret_type` that determines a secret type that can be generated - under this role set. Example: + under this role set. ### Usage - Secret Generation