From e0c08e20fde2a8fb02db6eb505d295e67d7bd96b Mon Sep 17 00:00:00 2001
From: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
Date: Tue, 12 Aug 2025 11:06:47 -0700
Subject: [PATCH] update links to user data format

---
 authentication-personalization/authentication-setup.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/authentication-personalization/authentication-setup.mdx b/authentication-personalization/authentication-setup.mdx
index 51687e695..8693e5e40 100644
--- a/authentication-personalization/authentication-setup.mdx
+++ b/authentication-personalization/authentication-setup.mdx
@@ -116,7 +116,7 @@ Your documentation is hosted at `docs.foo.com` and your team uses the dashboard
   <Step title="Create your user info endpoint (optional).">
     To enable personalization features, create an API endpoint that:
     * Accepts OAuth access tokens for authentication.
-    * Returns user data in the `User` format. See [Sending Data](/authentication-personalization/sending-data) for more information.
+    * Returns user data in the `User` format. See [User data format](/authentication-personalization/personalization-setup#user-data-format) for more information.
     
     Add this endpoint URL to the **Info API URL** field in your [authentication settings](https://dashboard.mintlify.com/settings/deployment/authentication).
   </Step>
@@ -168,7 +168,7 @@ Your documentation is hosted at `foo.com/docs` and you have an existing OAuth se
   <Step title="Integrate Mintlify authentication into your login flow.">
     Modify your existing login flow to include these steps after user authentication:
     
-    * Create a JWT containing the authenticated user's info in the `User` format. See [Sending Data](/authentication-personalization/sending-data) for more information.
+    * Create a JWT containing the authenticated user's info in the `User` format. See [User data format](/authentication-personalization/personalization-setup#user-data-format) for more information.
     * Sign the JWT with your secret key, using the EdDSA algorithm.
     * Create a redirect URL back to the `/login/jwt-callback` path of your docs, including the JWT as the hash.
   </Step>