overview copyedits

Author: ethanpalm

authentication-personalization/overview.mdx

@@ -33,16 +33,16 @@ Authentication and personalization offer multiple handshake methods for controll
   * No restrictions on API URLs.
 * Cons of JWT:
   * Must be compatible with your existing login flow.
-  * Dashboard sessions and docs authentication are decoupled, so your team will log in to your dashboard and your docs separately.
-  * When you refresh user data, users must login to your docs again. If your users' data changes frequently, they must log in frequently or risk having stale data in your docs.
+  * Dashboard sessions and docs authentication are decoupled, so your team will log into your dashboard and your docs separately.
+  * When you refresh user data, users must log into your docs again. If your users' data changes frequently, they must log in frequently or risk having stale data in your docs.
 
 **OAuth 2.0**: Third-party login integration like Google, GitHub, or other OAuth providers.
 * Pros of OAuth 2.0:
   * Heightened security standard.
   * No restrictions on API URLs.
 * Cons of OAuth 2.0:
   * Requires significant work if setting up an OAuth server for the first time.
-  * Dashboard sessions and docs authentication are decoupled, so your team will log in to your dashboard and your docs separately.
+  * Dashboard sessions and docs authentication are decoupled, so your team will log into your dashboard and your docs separately.
 
 ### Available for authentication and partial authentication 
 
@@ -74,13 +74,13 @@ Authentication and personalization offer multiple handshake methods for controll
 
 ## Content customization
 
-All three methods allow you to customize content with these personalization features.
+All three methods allow you to customize content with these features.
 
-### Dynamic content
+### Dynamic `MDX` content
 
 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.
+The `user` variable contains information sent to your docs from logged in users. See [Sending data](/authentication-personalization/sending-data) for more information.
 
 **Example**: Hello, {user.name ?? 'reader'}!
 
@@ -121,7 +121,7 @@ Automatically populate API playground fields with user-specific values by return
 
 ### Page visibility
 
-Restrict which pages are visible to your users by adding `groups` fields to your pages' frontmatter.
+Restrict which pages are visible to your users by adding `groups` fields to your pages' frontmatter. By default, every page is visible to every user.
 
 Users will only see pages for `groups` that they are in.