setup copyedits

Author: ethanpalm

authentication-personalization/authentication-setup.mdx

@@ -47,7 +47,7 @@ Select the handshake method that you want to configure.
 
 Your documentation is hosted at `docs.foo.com` with an existing authentication system at `foo.com`. You want to extend your login flow to grant access to the docs while keeping your docs separate from your dashboard (or you don't have a dashboard).
 
-To do this, create a login endpoint at `https://foo.com/docs-login` that extends your existing authentication.
+Create a login endpoint at `https://foo.com/docs-login` that extends your existing authentication.
 
 After verifying user credentials:
 * Generate a JWT with user data in Mintlify's format.
@@ -153,7 +153,7 @@ When an unauthenticated user tries to access a protected page, their intended de
   </Step>
 </Steps>
 
-## Example
+### Example
 
 Your documentation is hosted at `foo.com/docs` and you have an existing OAuth server at `auth.foo.com` that supports the Authorization Code Flow.
 
@@ -214,7 +214,7 @@ Password authentication provides access control only and does **not** support co
 
 ### Prerequisites
 
-* Your security requirements allow password sharing among your users.
+* Your security requirements allow sharing passwords among users.
 
 ### Implementation
 

authentication-personalization/partial-authentication-setup.mdx

@@ -10,11 +10,11 @@ Partial authentication shares all the same features as authentication, but with
 
 ## Setup
 
-Follow the [Authentication setup](/authentication-personalization/authentication-setup) guide and select **Partial Authentication**  when configuring your chosen handshake method.
+Follow the [Authentication Setup](/authentication-personalization/authentication-setup) guide and select **Partial Authentication** when configuring your chosen handshake method.
 
 ## Making pages public
 
-By default, all pages are protected. Add the `public` property to the page's frontmatter to make it viewable without authentication.
+By default, all pages are protected. Add the `public` property to the page's frontmatter to make it viewable without authentication:
 
 ```mdx
 ---

authentication-personalization/personalization-setup.mdx

@@ -16,7 +16,7 @@ Select the handshake method that you want to configure.
   <Tab title="JWT">
 ### Prerequisites
 
-* An login system that can generate and sign JWTs.
+* A login system that can generate and sign JWTs.
 * A backend service that can create redirect URLs.
 
 ### Implementation
@@ -81,14 +81,14 @@ export async function handleRequest(req: Request, res: Response) {
 To redirect users to specific sections after login, use this URL format: `https://docs.foo.com/page#jwt={SIGNED_JWT}&anchor={ANCHOR}`.
 
 **Example**:
-- Original URL: `https://docs.foo.com/quickstart#step-one`
-- Redirect URL: `https://docs.foo.com/quickstart#jwt={SIGNED_JWT}&anchor=step-one`
+* Original URL: `https://docs.foo.com/quickstart#step-one`
+* Redirect URL: `https://docs.foo.com/quickstart#jwt={SIGNED_JWT}&anchor=step-one`
 
 </Tab>
 <Tab title="OAuth 2.0">
 ### Prerequisites
 * An OAuth server that supports the PKCE Flow.
-* Ability to create an API endpoint accessible by OAuth access tokens 
+* Ability to create an API endpoint accessible by OAuth access tokens.
 
 ### Implementation
 <Steps>
@@ -132,11 +132,11 @@ Your documentation is hosted at `foo.com/docs` and you have an existing OAuth se
 ```
 
 **Configure your OAuth server details** in your dashboard:
-- **Authorization URL**: `https://auth.foo.com/authorization`
-- **Client ID**: `ydybo4SD8PR73vzWWd6S0ObH`
-- **Scopes**: `['docs-user-info']`
-- **Token URL**: `https://auth.foo.com/exchange`
-- **Info API URL**: `https://api.foo.com/docs/user-info`
+* **Authorization URL**: `https://auth.foo.com/authorization`
+* **Client ID**: `ydybo4SD8PR73vzWWd6S0ObH`
+* **Scopes**: `['docs-user-info']`
+* **Token URL**: `https://auth.foo.com/exchange`
+* **Info API URL**: `https://api.foo.com/docs/user-info`
 
 **Configure your OAuth server** to allow redirects to your callback URL.
   </Tab>
@@ -159,21 +159,20 @@ Your documentation is hosted at `foo.com/docs` and you have an existing OAuth se
     * Uses your existing session authentication to identify users
     * Returns user data in the `User` format (see [Sending Data](/authentication-personalization/sending-data))
     * If the API domain and the docs domain **do not exactly match**:
-      - Add the docs domain to your API's `Access-Control-Allow-Origin` header (must not be `*`).
-      - Set your API's `Access-Control-Allow-Credentials` header to `true`.
+      * Add the docs domain to your API's `Access-Control-Allow-Origin` header (must not be `*`).
+      * Set your API's `Access-Control-Allow-Credentials` header to `true`.
 
       <Warning>
         Only enable CORS headers on this specific endpoint, not your entire dashboard API.
       </Warning>
   </Step>
   <Step title="Configure your personalization settings">
-    Go to your [dashboard settings](https://dashboard.mintlify.com/products/authentication) and add the API URL and your Login URL to your Personalization settings.
     1. In your dashboard, go to [Authentication](https://dashboard.mintlify.com/settings/deployment/authentication).
     2. Select **Personalization**.
     3. Select **Shared Session**.
     4. Enter your **Info API URL**, which is the endpoint from the first step.
-    5. Enter your **Login URL**, where users log in to your dashboard.
-    6. Select **Save changes**
+    5. Enter your **Login URL**, where users log into your dashboard.
+    6. Select **Save changes**.
   </Step>
 </Steps>
 
@@ -190,18 +189,18 @@ You have a dashboard at `dash.foo.com`, which uses cookie-based session authenti
    * `Access-Control-Allow-Credentials`: `true`
 3. **Configure API URL** in authentication settings: `https://dash.foo.com/api/docs/user-info`.
 
-### Dashboard at subdomain, docs at root
+#### Dashboard at subdomain, docs at root
 
 You have a dashboard at `dash.foo.com`, which uses cookie-based session authentication. Your dashboard API routes are hosted at `dash.foo.com/api`. You want to set up personalization for your docs hosted at `foo.com/docs`.
 
 **Setup process**:
 1. **Create endpoint** `dash.foo.com/api/docs/user-info` that identifies users via session authentication and responds with their user data.
 2. **Add CORS headers** for this route only:
-   - `Access-Control-Allow-Origin`: `https://foo.com`
-   - `Access-Control-Allow-Credentials`: `true`
+   * `Access-Control-Allow-Origin`: `https://foo.com`
+   * `Access-Control-Allow-Credentials`: `true`
 3. **Configure API URL** in authentication settings: `https://dash.foo.com/api/docs/user-info`.
 
-### Dashboard at root, docs at root
+#### Dashboard at root, docs at root
 
 You have a dashboard at `foo.com/dashboard`, which uses cookie-based session authentication. Your dashboard API routes are hosted at `foo.com/api`. You want to set up personalization for your docs hosted at `foo.com/docs`.