From fbd6e15499cf080182992b6e2ba6f4d1acff8ee1 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Thu, 27 Apr 2023 08:43:19 -0400
Subject: [PATCH] spelling: use case

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---
 docs/enhancements/token-exchange-2023-02-03-#2812.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/enhancements/token-exchange-2023-02-03-#2812.md b/docs/enhancements/token-exchange-2023-02-03-#2812.md
index 97075052..f9f556d2 100644
--- a/docs/enhancements/token-exchange-2023-02-03-#2812.md
+++ b/docs/enhancements/token-exchange-2023-02-03-#2812.md
@@ -166,7 +166,7 @@ Additionally, a new `allowedGrantTypes` would allow for disabling exchanges if t
 - The password connector could be switch to support this new endpoint, submitting passwords as access tokens,
   allowing for multiple password connectors to be configured
 - The `audience` field could be made optional if there is a single connector or the id token is inspected for issuer url
-- The `actor_token` and `actor_token_type` can be checked / validated if a suitable usecase is determined.
+- The `actor_token` and `actor_token_type` can be checked / validated if a suitable use case is determined.
 - A policy language like [cel] or [rego] as mentioned on [#1635 Connector Middleware] 
   would allow for stronger assertions of the provided identity against requested resource access.
 
-- 
GitLab