update links

Author: ethanpalm

guides/hidden-page-example.mdx

@@ -11,7 +11,7 @@ See [Hidden pages](/guides/hidden-pages) for more information.
 ## Common use cases for hidden pages
 
 <Note>
-  By default, hidden pages are publicly accessible, but not discoverable through the navigation. If you want to restrict access to a hidden page, you must configure [authentication](/authentication-personalization/authentication-setup).
+  By default, hidden pages are publicly accessible, but not discoverable through the navigation. If you want to restrict access to a hidden page, you must configure [protected pages](/protected-pages/setup).
 </Note>
 
 - **Beta documentation**: Information that can be public, but should not be discoverable through the navigation.

guides/hidden-pages.mdx

@@ -8,9 +8,9 @@ Hidden pages are removed from your site's navigation but remain publicly accessi
 
 Use hidden pages for content that you want to be accessible on your site or referenced as context for AI tools, but not discoverable through the navigation.
 
-For content requiring strict access control, you must configure [authentication](/authentication-personalization/authentication-setup).
+For content requiring strict access control, you must configure [protected pages](/protected-pages/overview).
 
-If you want to hide pages for specific groups of users, use personalization to control [page visibility](/authentication-personalization/overview#page-visibility).
+If you want to hide pages for specific groups of users, use protected pages to control [page visibility](/protected-pages/overview#page-visibility).
 
 ## Hiding a page
 

protected-pages/overview.mdx

@@ -75,7 +75,7 @@ When users are authenticated to your docs, you can customize their experience wi
 
 Display dynamic content based on user information like name, plan, or organization.
 
-The `user` variable contains information sent to your docs from logged in users. See [Sending data](/authentication-personalization/sending-data) for more information.
+The `user` variable contains information sent to your docs from logged in users. See [Sending data](/protected-pages/sending-data) for more information.
 
 **Example**: Hello, {user.name ?? 'reader'}!
 

protected-pages/sending-data.mdx

@@ -4,7 +4,7 @@ description: "User data format for personalizing your documentation"
 icon: "send"
 ---
 
-When implementing authentication or personalization, your system returns user data in a specific format that enables content customization. This data can be sent as either a raw JSON object or within a signed JWT, depending on your handshake method. The shape of the data is the same for both.
+When implementing protected pages, your system returns user data in a specific format that enables content customization. This data can be sent as either a raw JSON object or within a signed JWT, depending on your handshake method. The shape of the data is the same for both.
 
 ## User data format
 

settings/preview-deployments.mdx

@@ -51,4 +51,4 @@ Preview deployments can be publicly accessible or restricted to authenticated us
 
 **Public access**: Preview URLs are publicly viewable by default. Share a preview link with anyone who needs to review your changes.
 
-**Restricted access**: Enable preview deployment authentication to limit preview access to authenticated Mintlify users only. See [Authentication Setup](/authentication-personalization/authentication-setup) for more information.
+**Restricted access**: Enable preview deployment authentication to limit preview access to authenticated Mintlify users only. See [Protected pages setup](/protected-pages/setup) for more information.