From 4b2a72c61683182a85d082ccc265aa1e358d221f Mon Sep 17 00:00:00 2001
From: Jason O'Donnell <2160810+jasonodonnell@users.noreply.github.com>
Date: Thu, 21 May 2020 10:11:32 -0400
Subject: [PATCH] doc: clarify token helper intro (#9058)

---
 website/pages/docs/commands/token-helper.mdx | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/website/pages/docs/commands/token-helper.mdx b/website/pages/docs/commands/token-helper.mdx
index f66d18a4e..588983154 100644
--- a/website/pages/docs/commands/token-helper.mdx
+++ b/website/pages/docs/commands/token-helper.mdx
@@ -9,7 +9,15 @@ description: >-
 
 # Token Helpers
 
-The Vault CLI provides a built in tool for authenticating to any of the enabled auth backends. By default the Vault CLI will take the generated token after a successful authentication and store it on disk in the `~/.vault-token` file. This functionality can change in Vault via the use of a token helper. A token helper is an external program that Vault calls to save, retrieve or erase a saved token. The token helper could be a very simple script or a more complex program depending on your needs. The interface to the external token helper is extremely simple.
+A token helper is an external program that Vault calls to save, retrieve or erase 
+a saved token. The token helper could be a very simple script or a more complex 
+program depending on your needs. The interface to the external token helper is 
+extremely simple.
+
+By default the Vault CLI provides a built in tool for authenticating with any 
+of the enabled authentication backends. Once authenticated, the CLI will store 
+the generated token on disk in the `~/.vault-token` file. By using a token helper, 
+this default functionality can be changed.
 
 ## Configuration