From f2916808571c58d14d75eaf80235cdc513bb8a0a Mon Sep 17 00:00:00 2001
From: Steven Soroka <149692779+ssoroka-tc@users.noreply.github.com>
Date: Wed, 4 Dec 2024 23:35:51 -0500
Subject: [PATCH] fix oauth2-jwt.md mermaid rendering issue

---
 docs/docs/how-to/oauth2-jwt.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/docs/how-to/oauth2-jwt.md b/docs/docs/how-to/oauth2-jwt.md
index 4273ff46..015d5163 100644
--- a/docs/docs/how-to/oauth2-jwt.md
+++ b/docs/docs/how-to/oauth2-jwt.md
@@ -18,13 +18,13 @@ Huma does not provide any built-in access token issuing functionality. Instead,
 
 ```mermaid
 graph LR
-	User -->|1. Login| Auth0
-	Auth0 -->|2. Issue access token| User
+	User -->|1: Login| Auth0
+	Auth0 -->|2: Issue access token| User
 	Auth0 -.->|Refresh JWKS| API
-	User --->|3. Make request| API
-	API -->|4. Verify access token & roles| Validate
-	Validate -->|5. Accept/reject| API
-	API --->|6. Success| Handler
+	User --->|3: Make request| API
+	API -->|4: Verify access token & roles| Validate
+	Validate -->|5: Accept/reject| API
+	API --->|6: Success| Handler
 ```
 
 The access token may be issued in different flavors & formats, but for the remainder of this document we will assume they are [JWTs](https://jwt.io/).