Documentation edits made through Mintlify web editor

Author: mintlify[bot]

settings/authentication-personalization/authentication.mdx

@@ -28,4 +28,4 @@ Authentication is similar to our [Personalization](./personalization) offering,
 to securing your documentation content, all features that are available via
 Personalization are also available via Authentication.
 
-Check out our docs for more info on [choosing Authentication vs Personalization](./authentication-vs-personalization).
+Check out our docs for more info on [choosing Authentication vs Personalization](./authentication-vs-personalization).

settings/authentication-personalization/partial-authentication.mdx

@@ -22,4 +22,4 @@ By default, all pages are protected. You can specify which pages should be publi
 title: "My Page"
 public: true
 ---
-```
+```

settings/authentication-personalization/personalization-setup/oauth.mdx

@@ -33,7 +33,7 @@ If you have an existing OAuth server that supports the PKCE flow, you can integr
 
 I have an existing OAuth server that supports the PKCE flow. I want to set up authentication for my docs hosted at `foo.com/docs`.
 
-To set up authentication with Mintlify, I create an endpoint `api.foo.com/docs/user-info` which requires an OAuth access token with the `docs-user-info` scope, and responds with the user's custom data according to Mintlify’s specification.
+To set up authentication with Mintlify, I create an endpoint `api.foo.com/docs/user-info` which requires an OAuth access token with the `docs-user-info` scope, and responds with the user's custom data according to Mintlify's specification.
 
 I then go to the dashboard settings, navigate to the Personalization settings, select OAuth, and enter the relevant values for the OAuth flow and Info API endpoint:
 - **Authorization URL**: `https://auth.foo.com/authorization`
@@ -42,4 +42,4 @@ I then go to the dashboard settings, navigate to the Personalization settings, s
 - **Token URL**: `https://auth.foo.com/exchange`
 - **Info API URL**: `https://api.foo.com/docs/user-info`
 
-Finally, I copy the Redirect URL displayed in the dashboard settings and add it as an authorized redirect URL in my OAuth client configuration settings.
+Finally, I copy the Redirect URL displayed in the dashboard settings and add it as an authorized redirect URL in my OAuth client configuration settings.

settings/authentication-personalization/personalization-setup/shared-session.mdx

@@ -7,7 +7,7 @@ description: 'Seamlessly share user sessions between your dashboard and your doc
   This is the documentation for the Shared Session **Personalization** Handshake. The Shared Session Handshake is not available for Authentication.
 </Info>
 
-This method utilizes the session authentication info already stored in your user’s browser to create a seamless documentation experience.
+This method utilizes the session authentication info already stored in your user's browser to create a seamless documentation experience.
 
 ## Implementation
 
@@ -17,7 +17,7 @@ This method utilizes the session authentication info already stored in your user
 
     If the API domain does not *exactly match* the docs domain:
       - Add the docs domain to your API's `Access-Control-Allow-Origin` header (must not be `*`)
-      - Ensure your API’s `Access-Control-Allow-Credentials` header is `true`
+      - Ensure your API's `Access-Control-Allow-Credentials` header is `true`
       <Warning>
         These CORS options only need to be enabled on the *single endpoint* responsible for returning user information. We do not recommend enabling these options on all dashboard endpoints.
       </Warning>
@@ -33,22 +33,22 @@ This method utilizes the session authentication info already stored in your user
 
 I have a dashboard at `dash.foo.com`, which uses cookie-based session authentication. My dashboard API routes are hosted at `dash.foo.com/api`. I want to set up authentication for my docs hosted at `docs.foo.com`.
 
-To set up authentication with Mintlify, I create another dashboard endpoint `dash.foo.com/api/docs/user-info` which identifies the user using session auth, and responds with their custom data according to Mintlify’s specification. I then add `https://docs.foo.com` to the `Access-Control-Allow-Origin` allow-list **for this route only**, and ensure my `Access-Control-Allow-Credentials` configuration is set to `true` **for this route only**.
+To set up authentication with Mintlify, I create another dashboard endpoint `dash.foo.com/api/docs/user-info` which identifies the user using session auth, and responds with their custom data according to Mintlify's specification. I then add `https://docs.foo.com` to the `Access-Control-Allow-Origin` allow-list **for this route only**, and ensure my `Access-Control-Allow-Credentials` configuration is set to `true` **for this route only**.
 
 I then go to the dashboard settings and enter `https://dash.foo.com/api/docs/user-info` for the API URL field.
 
 ### Dashboard at subdomain, docs at root
 
 I have a dashboard at `dash.foo.com`, which uses cookie-based session authentication. My dashboard API routes are hosted at `dash.foo.com/api`. I want to set up authentication for my docs hosted at `foo.com/docs`.
 
-To set up authentication with Mintlify, I create another dashboard endpoint `dash.foo.com/api/docs/user-info` which identifies the user using session auth, and responds with their custom data according to Mintlify’s specification. I then add `https://foo.com` to the `Access-Control-Allow-Origin` allow-list **for this route only**, and ensure my `Access-Control-Allow-Credentials` configuration is set to `true` **for this route only**.
+To set up authentication with Mintlify, I create another dashboard endpoint `dash.foo.com/api/docs/user-info` which identifies the user using session auth, and responds with their custom data according to Mintlify's specification. I then add `https://foo.com` to the `Access-Control-Allow-Origin` allow-list **for this route only**, and ensure my `Access-Control-Allow-Credentials` configuration is set to `true` **for this route only**.
 
 I then go to the dashboard settings and enter `https://dash.foo.com/api/docs/user-info` for the API URL field.
 
 ### Dashboard at root, docs at root
 
 I have a dashboard at `foo.com/dashboard`, which uses cookie-based session authentication. My dashboard API routes are hosted at `foo.com/api`. I want to set up authentication for my docs hosted at `foo.com/docs`.
 
-To set up authentication with Mintlify, I create another dashboard endpoint `foo.com/api/docs/user-info` which identifies the user using session auth, and responds with their custom data according to Mintlify’s specification.
+To set up authentication with Mintlify, I create another dashboard endpoint `foo.com/api/docs/user-info` which identifies the user using session auth, and responds with their custom data according to Mintlify's specification.
 
 I then go to the dashboard settings and enter `https://foo.com/api/docs/user-info` for the API URL field.

settings/authentication-personalization/personalization.mdx

@@ -30,7 +30,7 @@ This feature becomes even more powerful when paired with custom data about the u
 
 Personalization is an enterprise feature. {
 user.org === undefined
-? <>To access this feature, first create an account at the <a href="https://dashboard.mintlify.com/login">Mintlify dashboard</a>.</>
+? <>To access this feature, first create an account.</>
 : user.org.plan !== 'enterprise'
 ? <>You are currently on the ${user.org.plan ?? 'free'} plan. To speak to our team about upgrading, <a href="mailto:[email protected]">contact our sales team</a>.</>
 : <>To request this feature for your enterprise org, <a href="mailto:[email protected]">contact our team</a>.</>
@@ -39,7 +39,7 @@ user.org === undefined
 ```jsx
 Personalization is an enterprise feature. {
   user.org === undefined
-    ? <>To access this feature, first create an account at the <a href="https://dashboard.mintlify.com/login">Mintlify dashboard</a>.</>
+    ? <>To access this feature, first create an account.</>
     : user.org.plan !== 'enterprise'
       ? <>You are currently on the ${user.org.plan ?? 'free'} plan. To speak to our team about upgrading, <a href="mailto:[email protected]">contact our sales team</a>.</>
       : <>To request this feature for your enterprise org, <a href="mailto:[email protected]">contact our team</a>.</>
@@ -82,4 +82,4 @@ Here's a table that displays whether a page is shown for different combinations
 <Note>
   Note that an empty array in the page metadata is interpreted as "No groups
   should see this page."
-</Note>
+</Note>

settings/authentication-personalization/sending-data.mdx

@@ -31,7 +31,7 @@ type User = {
   path="groups"
   type="string[]"
 >
-  A list of groups that the user belongs to. This will determine which pages should be shown to this user. If any of these groups is listed in the `groups` field of a page’s metadata, that page will be shown.
+  A list of groups that the user belongs to. This will determine which pages should be shown to this user. If any of these groups is listed in the `groups` field of a page's metadata, that page will be shown.
 </ParamField>
 <ParamField
   path="content"
@@ -46,6 +46,4 @@ type User = {
   User-specific values that will be prefilled in the API playground if supplied. For example, if each of my customers makes requests at a specific subdomain, I can send `{ server: { subdomain: 'foo' } }` as my `apiPlaygroundInputs` field, and this value will be prefilled on any API page with this `subdomain` value.
 
   <Note>The`header`, `query`, and `cookie` fields will only be prefilled if they are part of your [security scheme](https://swagger.io/docs/specification/authentication/). Creating a standard header parameter named `Authorization` is not sufficient to enable this feature. To know if a field will be prefilled, navigate to your existing docs and check if the field is in either the `Authorization` or `Server` section.</Note>
-</ParamField>
-
-    
+</ParamField>