From afc8719407087c67f83a9c46760178a23369e7f5 Mon Sep 17 00:00:00 2001
From: Robert Keyser <39230492+RobertKeyser@users.noreply.github.com>
Date: Mon, 28 Mar 2022 15:42:25 -0500
Subject: [PATCH] authentication.md: a -> an

Changed "Create *a* Access Token" to "Create *an* Access Token"
---
 src/config-api/authentication.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/config-api/authentication.md b/src/config-api/authentication.md
index 1658248d92..d5170b2051 100644
--- a/src/config-api/authentication.md
+++ b/src/config-api/authentication.md
@@ -11,7 +11,7 @@ As a workspace owner, you can create access tokens from the Access Management pa
 > warning "Secret Token"
 > You can not retrieve the plain-text `token` later, so you should save it in a secret manager. If you lose the `token` you can generate a new one.
 
-## Use a Access Token
+## Use an Access Token
 
 Now that you have an access token, you can use this token to access the Config API by setting it in the `Authorization` header of your requests, for example: