diff --git a/astro.config.mjs b/astro.config.mjs
index dbff7e4a3..4012a132c 100644
--- a/astro.config.mjs
+++ b/astro.config.mjs
@@ -132,6 +132,8 @@ export default defineConfig({
     // Build section subfolder redirects
     "/build/applications/":
       "/build/applications/about-applications/",
+    "/build/applications/add-and-manage-applications/":
+      "/build/applications/about-applications/",
     "/build/domains/":
       "/build/domains/pointing-your-domain/",
     "/build/env-variables/":
diff --git a/src/content/docs/authenticate/device-authorization-flow/overview.mdx b/src/content/docs/authenticate/device-authorization-flow/overview.mdx
index e3ed7fc77..6d5f5a557 100644
--- a/src/content/docs/authenticate/device-authorization-flow/overview.mdx
+++ b/src/content/docs/authenticate/device-authorization-flow/overview.mdx
@@ -90,7 +90,7 @@ The device must poll the token endpoint at regular intervals until the user comp
 
 - **Initial interval**: Use the `interval` value from the device authorization response (typically 5 seconds).
 - **Slow down**: If you receive a `slow_down` error, increase the polling interval by 5 seconds.
-- **Maximum time**: Stop polling after the `expires_in` time (typically 30 minutes).
+- **Maximum time**: Stop polling after the `expires_in` time (typically 10 minutes).
 
 ## Device authorization flow error codes
 
diff --git a/src/content/docs/authenticate/device-authorization-flow/troubleshooting.mdx b/src/content/docs/authenticate/device-authorization-flow/troubleshooting.mdx
index 3ce107227..f00ee857b 100644
--- a/src/content/docs/authenticate/device-authorization-flow/troubleshooting.mdx
+++ b/src/content/docs/authenticate/device-authorization-flow/troubleshooting.mdx
@@ -74,7 +74,7 @@ if (error === "access_denied") {
 ### expired_token
 
 **Error**: `expired_token`
-**Description**: The device code has expired (typically after 30 minutes).
+**Description**: The device code has expired (typically after 10 minutes).
 
 **Solution**: Request a new device code.
 
diff --git a/src/content/docs/authenticate/manage-authentication/manage-authentication-applications.mdx b/src/content/docs/authenticate/manage-authentication/manage-authentication-applications.mdx
index 2848a0f0c..80b9230a2 100644
--- a/src/content/docs/authenticate/manage-authentication/manage-authentication-applications.mdx
+++ b/src/content/docs/authenticate/manage-authentication/manage-authentication-applications.mdx
@@ -30,7 +30,7 @@ updated: 2025-01-16
 
 If you want, you can select different authentication methods for different applications. You might want to do this, for example, so users sign in with Google for your Android app and Apple for your iOS app.
 
-You first need to [set up all your auth methods](/authenticate/authentication-methods/set-up-user-authentication/) and [set up each application](/build/applications/add-and-manage-applications/).
+You first need to [set up all your auth methods](/authenticate/authentication-methods/set-up-user-authentication/) and [set up each application](/build/applications/about-applications/).
 
 1. Go to **Settings > Environment > Applications**.
 2. Select **View details** on the application you want to edit.
diff --git a/src/content/docs/build/applications/about-applications.mdx b/src/content/docs/build/applications/about-applications.mdx
index 33db848d8..1b4612b05 100644
--- a/src/content/docs/build/applications/about-applications.mdx
+++ b/src/content/docs/build/applications/about-applications.mdx
@@ -1,17 +1,24 @@
 ---
 page_id: 4a46eba1-598a-4804-b669-dc96f31d2205
-title: Applications in Kinde
-description: Comprehensive overview of Kinde applications including backend, frontend, and machine-to-machine applications with OAuth 2.0 flows and security considerations.
+title: About applications in Kinde
+description: Overview of Kinde application types—back-end web, front-end and mobile, M2M, and Device and IoT—including OAuth 2.0 flows, configuration, and management in the dashboard.
 sidebar:
   order: 1
+  label: About applications
+tableOfContents:
+  maxHeadingLevel: 3
 relatedArticles:
-  - 6c70b7ae-1b1b-43bb-bea1-9b3ec88dd082
   - 38d2394f-f064-47a1-89d0-078597b78412
   - 6bf993fc-a195-4836-8eaf-133812be8876
+  - 7e861737-04c6-4f69-bf83-84b5f40f1962
+app_context:
+  - m: settings
+    s: applications
 topics:
   - applications
   - oauth
   - authentication
+  - authorization
 sdk: []
 languages: []
 audience: developers
@@ -19,83 +26,218 @@ complexity: intermediate
 keywords:
   - applications
   - OAuth 2.0
-  - authorization flows
-  - backend apps
-  - frontend apps
-  - M2M apps
+  - authorization code flow
+  - PKCE
   - client credentials
-updated: 2024-01-15
+  - machine to machine
+  - device authorization flow
+  - back-end web apps
+  - front-end apps
+  - mobile apps
+  - IoT applications
+updated: 2026-06-10
 featured: false
 deprecated: false
-ai_summary: Comprehensive overview of Kinde applications including backend, frontend, and machine-to-machine applications with OAuth 2.0 flows and security considerations.
+ai_summary: "This page explains what Kinde applications are and how they connect products and services to Kinde for authentication and authorization. It covers four application types: Back-end web apps using the Authorization Code Flow with a client secret for server-rendered applications; Front-end and mobile apps using Authorization Code Flow with PKCE for SPAs, web browsers, and native mobile clients in untrusted environments; Machine to machine (M2M) apps using the Client Credentials grant for backend services, APIs, CLIs, and the Kinde Management API with scope-based access; and Device and IoT apps using the OAuth 2.0 Device Authorization Grant (RFC 8628) for input-limited devices like smart TVs and gaming consoles. The page lists compatible SDKs for each type, notes that Kinde does not support the Implicit Flow, and explains M2M token properties and device flow polling, audiences, and default app settings. It also walks through adding, configuring, and deleting applications in the Kinde dashboard, including app keys, callback URLs, authentication methods, tokens, sessions, and permanent deletion requirements."
 ---
 
-Applications in Kinde facilitate the receipt of access tokens in your application’s code. Kinde applications use OAuth 2.0 flows to securely pass tokens.
+In Kinde, an application represents a product or service that connects to Kinde for authentication and authorization—such as a website, mobile app, or backend API. Each application type uses OAuth 2.0 flows to securely obtain access tokens (and, where applicable, ID tokens) that your code can use to identify users or call protected APIs.
 
-See [Section 4 of the OAuth 2.0 Authorization Framework](https://datatracker.ietf.org/doc/html/rfc6749#section-4) for details on Authorization flows.
+Kinde supports the following application types:
 
-We support the following applications and flows.
+1. **Back-end web**: For server-rendered web applications
+2. **Front-end and mobile**: For client-side web and native mobile applications, including JavaScript-based single page applications (SPAs)
+3. **Machine to machine (M2M)**: For trusted back-end services, APIs, and other systems that act on their own behalf
+4. **Device and IoT**: For devices with limited input capabilities, such as smart TVs, gaming consoles, and IoT applications
 
-## Back-end / server-side apps
+    ![kinde application types](https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/297a6959-eefe-496d-463a-6da163997300/socialsharingimage)
 
-Use for server-rendered web applications. Suitable for confidential applications (such as Regular Web Applications) because the application's authentication methods are included in the exchange and must be kept secure.
+## Supported app types
 
-### Secured with Authorization Code Flow
+### Back-end web
+
+Use for server-rendered web applications. Suitable for confidential applications (such as Regular Web Applications) because credentials like the client secret can be stored securely on the server.
+
+#### Secured with Authorization Code Flow
 
 This application uses the Authorization Code Flow to exchange an authorization code for a token.
 
-For security, a client secret is required to request an access token. The client secret is known only to the application and the authorization server. So when the application makes a request for an access token, it includes the client secret as a form of authentication. This ensures that the authorization server can verify the identity of the client application.
+For security, a client secret is required to request an access token. The client secret is known only to the application and the authorization server. When the application makes a request for an access token, it includes the client secret as a form of authentication. This ensures that the authorization server can verify the identity of the client application.
 
 The use of client secrets protects sensitive data from being accessed by unauthorized users and systems.
 
 <Aside>
 
-If the Client secret field is empty in your Kinde app it’s because client secrets are only available for back-end/server-side apps. You may have created a front-end/client-server app (that has no client secret) by mistake.
+If the Client secret field is unavailable in your Kinde app this means you may have created a front-end/client-side app (that has no client secret) by mistake.
 
 </Aside>
 
-### SDKs and compatible frameworks
+#### Compatible back-end SDKs
 
-Apollo GraphQL, Elixir, ExpressJS, Express GraphQL, Java, .NET, Next.js, NodeJS, Nuxt, PHP, Python, Ruby, TypeScript.
+- [NextJS App Router](/developer-tools/sdks/backend/nextjs-sdk/) and [NextJS Pages Router](/developer-tools/sdks/backend/nextjs-prev-sdk/)
+- [TanStack Start React](/developer-tools/sdks/backend/tsr-sdk/)
+- [Go SDK](/developer-tools/sdks/backend/go-sdk/)
+- [Python SDK](/developer-tools/sdks/backend/python-sdk/)
 
-[View Kinde SDKs](/developer-tools/about/our-sdks/)
+See the full list of [Kinde back-end SDKs](/developer-tools/about/our-sdks/#back-end).
 
-## Front-end / client-side apps
+### Front-end and mobile
 
-Use for client-side web applications, single page web applications, and mobile applications. Authentication methods are different for these apps because they run in unsecured systems, such as web browsers.
+Use for client-side web applications, single page web applications, and mobile applications. Authentication methods are different for these apps because they run in untrusted environments, such as web browsers and mobile devices.
 
-### Secured with Authorization Code Flow and PKCE
+#### Secured with Authorization Code Flow and PKCE
 
 This application uses the Authorization Code Flow with Proof Key for Code Exchange (PKCE).
 
-Client-side applications, such as single-page web apps, are typically unable to securely store a client secret due to the inherent exposure of client-side code. That’s why OAuth 2.0 recommends the Implicit Flow or PKCE (Proof Key for Code Exchange) to provide security without relying on a client secret.
-
-<Aside>
-
-**Kinde does not support the Implicit Flow** method for front-end apps as it has some security vulnerabilities. We support Authorization Code Flow with PKCE instead.
+Client-side applications, such as single-page web apps, are typically unable to securely store a client secret due to the inherent exposure of client-side code. That’s why OAuth 2.0 recommends the Authorization Code Flow with PKCE (Proof Key for Code Exchange) for public clients that cannot use a client secret.
 
+<Aside type="warning" title="About Implicit Flows">
+Kinde does not support the Implicit Flow method for front-end apps as it has some security vulnerabilities. We support Authorization Code Flow with PKCE instead.
 </Aside>
 
-### SDKs and compatible frameworks
+#### Compatible front-end SDKs
 
-JavaScript, React, TypeScript, Android, iOS, React Native, Expo, Flutter, Node/Apollo GraphQL, Node/Express GraphQL.
+- [React SDK](/developer-tools/sdks/frontend/react-sdk/)
+- [Android SDK](/developer-tools/sdks/native/android-sdk/)
+- [iOS SDK](/developer-tools/sdks/native/ios-sdk/)
+- [Flutter SDK](/developer-tools/sdks/native/flutter-sdk/)
 
-[View Kinde SDKs](/developer-tools/about/our-sdks/)
+See the full list of [Kinde front-end and native SDKs](/developer-tools/about/our-sdks/#front-end).
 
-## Machine to machine (M2M) apps
+### Machine to machine (M2M)
 
-Use for your backend services that require access to an API. This includes accessing the Kinde management API. Other use cases include CLIs, daemons and IoT devices. You can create as many M2M apps as you require. See [Add a machine to machine application for API access](/developer-tools/kinde-api/connect-to-kinde-api/).
+Use for your backend services that require access to an API. This includes accessing the Kinde management API. Other use cases include CLIs and background daemons. You can create as many M2M apps as you require. See [Add a machine to machine application for API access](/developer-tools/kinde-api/connect-to-kinde-api/).
 
-### Secured with Client Credentials
+#### Secured with Client Credentials
 
 M2M applications are secured through an initial exchange of each application’s Client ID and Client Secret. This identifies each application as authorized for token exchange.
 
 Each access token request must include the `Client Credentials` grant type. Typically, a request includes scopes, which define the type of information that can be requested in the exchange.
 
-### Access to Kinde's Management API is managed via scopes
+#### Access to Kinde's Management API is managed via scopes
 
 When you set up an M2M application that you will use with Kinde's Management API, you need to select the scopes that your application will need to access. For example, you'll select `read`, `create`, `update`, and `delete` actions.
 
-### Add properties to M2M tokens
+#### Add properties to M2M tokens
 
 If you want, you can [add custom properties to an M2M application](/properties/work-with-properties/manage-properties/) and then [include these properties in M2M tokens](/properties/work-with-properties/properties-in-tokens/). This is helpful if you want to include special information when you pass M2M tokens between systems.
+
+### Device and IoT
+
+Use for devices with limited input capabilities, such as smart TVs, gaming consoles, and IoT devices. Users authenticate on a secondary device (like a phone or computer) while the primary device receives the access token.
+
+#### Secured with Device Authorization Flow
+
+This application uses the OAuth 2.0 Device Authorization Grant ([RFC 8628](https://datatracker.ietf.org/doc/html/rfc8628)). The flow works as follows:
+
+1. The device requests a device code and user code from Kinde.
+2. The user visits a verification URI on another device and enters the user code, or scans the QR code included in the response.
+3. The device polls the token endpoint at the interval returned in the response until authorization is complete.
+4. The device receives an access token and can call protected APIs.
+
+Device and IoT applications do not use a client secret. They are identified by Client ID only.
+
+The device must poll the token endpoint at regular intervals until the user completes authentication. Use the `interval` value from the device authorization response (typically 5 seconds). If you receive a `slow_down` error, increase the polling interval by 5 seconds. Stop polling after the `expires_in` time (typically 10 minutes).
+
+#### Audiences and scopes
+
+If you specify an `audience` in the device authorization request, the access token includes the audience in the `aud` claim. Any scopes belonging to that audience that are granted to the user by their role are shown on the consent screen and included in the access token when the user consents. The API must be authorized for the device authorization application.
+
+#### Default app for device flows
+
+You can set a Device and IoT application as the default for device flows. If no Client ID is specified in a device authorization request, Kinde uses the default application.
+
+See [About the device authorization flow](/authenticate/device-authorization-flow/overview/) and the [quick start guide](/authenticate/device-authorization-flow/quick-start/) to implement this flow in your application.
+
+## Manage applications
+
+### Add an application
+
+1. Sign in to your Kinde dashboard, and select **Add application**.
+2. Alternatively, go to **Settings > Environment > Applications**. Select **Add application**.
+3. Enter a **Name** and select the **Type** of application (e.g., Back-end web). Select **Save**.
+4. Select the SDK (e.g., NextJS), select **Save**.
+5. Configure the application by selecting **View details** on the application tile. See below for more details.
+
+### Configure an application
+
+**Get application keys**:
+
+You will need the application keys to connect your codebase to Kinde.
+1. Go to your application > **Details > App keys**.
+2. Copy the **Domain** (or [Custom domain](/build/domains/pointing-your-domain/)), **Client ID**, and **Client secret** (if applicable).
+
+    Learn more about [application keys](/get-started/connect/getting-app-keys/).
+
+**Set callback URLs**:
+
+1. Go to your application > **Details > Callback URLs**.
+2. Enter the callback URLs for your application generated by the [relevant SDK](/developer-tools/about/our-sdks/).
+3. Select **Save**.
+
+    Learn more about [callback URLs](/get-started/connect/callback-urls/).
+
+**Set up authentication**:
+
+Configure how your users authenticate to your application (e.g., email, phone, username, social, enterprise).
+
+1. Go to your application > **Authentication**.
+2. Enable the authentication methods you want to use for your application (e.g., Google, Facebook, Microsoft Entra ID, etc.).
+3. Select **Save**.
+
+    Learn more about [authentication methods](/authenticate/authentication-methods/set-up-user-authentication/).
+
+    <Aside>
+    For production applications, enter the credentials provided by third-party providers in Kinde. [Learn more here](/authenticate/social-sign-in/add-social-sign-in/).
+    </Aside>
+
+**Configure tokens and sessions**:
+
+1. Go to your application > **Tokens**.
+2. Configure the token expiry, client-specific refresh token cookies, and customize token fields.
+3. Go to **Sessions** to configure session policy and the session inactivity timeout.
+
+    Learn more about [tokens](/build/tokens/configure-tokens/) and [session management](/authenticate/manage-authentication/session-management/).
+
+### Delete an application
+
+<Aside type="danger" title="Deleting an application is permanent">
+Deleting an application is a destructive action which cannot be reversed. All application-related authentication settings, token settings, session information, and API links are also deleted. We recommend backing up all configuration before deleting an application. See [Manage Kinde configuration as code](/developer-tools/guides/manage-kinde-configuration/) for more information.
+</Aside>
+
+<Aside title="Notes on deleting an application">
+- You need **Owner** or **Admin** permissions to delete an application.
+- Deleting an application doesn't delete the users in the business.
+</Aside>
+
+To delete an application:
+
+1. Go to **Settings > Environment > Applications**.
+2. Select the three dots next to the application you want to delete and select **Delete application**.
+3. Follow the prompts in the window and select **Delete application**.
+
+## Application FAQs
+
+Common questions about creating and managing applications in Kinde.
+
+### How many applications can I create in Kinde?
+
+You can create as many applications as you need within an environment. Each application gets its own Client ID and, where applicable, its own client secret.
+
+Users who sign in through any application in the same environment share the same user pool—they are not duplicated per application. If you need fully separate user bases, use separate [environments](/build/environments/environments/) or [businesses](/build/set-up-options/run-multiple-businesses/).
+
+Learn more about [application keys](/get-started/connect/getting-app-keys/).
+
+### Why do I need to create multiple applications?
+
+Most products need more than one application. Common reasons include:
+
+- **Different platforms or architectures** — for example, a Back-end web app for a server-rendered site, a Front-end and mobile app for an SPA or native client, and an M2M app for API access.
+- **Different authentication methods** — configure sign-in options per application, such as Google for Android and Apple for iOS. See [Change authentication for an application](/authenticate/manage-authentication/manage-authentication-applications/).
+- **Separate callback URLs, tokens, and sessions** — each application has its own redirect URLs, token lifetimes, and session settings.
+- **Organization routing for multi-tenancy** — direct users to a specific organization at sign-in by passing an `org_code` in the auth request. See [About organizations](/build/organizations/multi-tenancy-using-organizations/).
+- **Different audiences** — use separate applications for production users and internal testers, each with its own auth methods and configuration.
+
+## Resources
+
+- [Section 4 of the OAuth 2.0 Authorization Framework](https://datatracker.ietf.org/doc/html/rfc6749#section-4).
diff --git a/src/content/docs/build/applications/add-and-manage-applications.mdx b/src/content/docs/build/applications/add-and-manage-applications.mdx
deleted file mode 100644
index d29c20956..000000000
--- a/src/content/docs/build/applications/add-and-manage-applications.mdx
+++ /dev/null
@@ -1,69 +0,0 @@
----
-page_id: 6c70b7ae-1b1b-43bb-bea1-9b3ec88dd082
-title: Add and manage applications
-description: Step-by-step guide for adding and managing applications in Kinde including configuration tasks, application deletion, and integration setup requirements.
-sidebar:
-  order: 2
-relatedArticles:
-  - 4a46eba1-598a-4804-b669-dc96f31d2205
-  - 6bf993fc-a195-4836-8eaf-133812be8876
-  - 7e861737-04c6-4f69-bf83-84b5f40f1962
-app_context:
-  - m: settings
-    s: applications
-topics:
-  - applications
-  - configuration
-sdk: []
-languages: []
-audience: developers
-complexity: beginner
-keywords:
-  - add applications
-  - manage applications
-  - application configuration
-  - delete applications
-  - application keys
-  - callback URLs
-updated: 2024-01-15
-featured: false
-deprecated: false
-ai_summary: Step-by-step guide for adding and managing applications in Kinde including configuration tasks, application deletion, and integration setup requirements.
----
-
-Applications are how you make your product or service available to your users, such as through a mobile app, a web app, or a website.
-
-If you plan to manage authentication for each of your applications using Kinde, you will need to add and configure each application.
-
-[Kinde provides several application types](/build/applications/about-applications/), including a regular web app (for execution on a server), single page web app (for browsers and mobile), and machine to machine applications (for backend services that require access to an API, including the [Kinde management API](/developer-tools/kinde-api/connect-to-kinde-api/)).
-
-## Add an application
-
-1. Go to **Settings > Environment >** **Applications**.
-2. Select **Add application**.
-3. Enter a name and select the type of application.
-4. Select **Save**. A tile appears for the application.
-5. Configure the application by selecting **View details** on the application tile. Some of the main tasks are listed below.
-
-## Application configuration tasks
-
-- [Get application keys](/get-started/connect/getting-app-keys/) to connect your apps
-- Set callback URLs using the [relevant SDK](/developer-tools/about/our-sdks/)
-- [Set up authentication](/authenticate/authentication-methods/set-up-user-authentication/)
-- [Configure tokens](/build/tokens/configure-tokens/)
-
-## Delete an application
-
-You can now delete applications in Kinde. You need to be an owner or an admin to do this.
-
-<Aside type="danger">
-
-Deleting an application is a destructive action which cannot be reversed. We recommend backing up all relevant data and checking for application dependencies.
-
-</Aside>
-
-When an application is deleted, all application-related authentication settings, token settings, session information, and API links are also deleted.
-
-1. Go to **Settings > Environment >** **Applications**.
-2. Select the three dots next to the application you want to delete and select **Delete application**. A confirmation window appears.
-3. Follow the prompts in the window and select **Delete application**.
diff --git a/src/content/docs/build/applications/rotate-client-secret.mdx b/src/content/docs/build/applications/rotate-client-secret.mdx
index 61c7c595e..7ed687761 100644
--- a/src/content/docs/build/applications/rotate-client-secret.mdx
+++ b/src/content/docs/build/applications/rotate-client-secret.mdx
@@ -5,7 +5,7 @@ description: Security guide for rotating client secrets in backend and machine-t
 sidebar:
   order: 4
 relatedArticles:
-  - 6c70b7ae-1b1b-43bb-bea1-9b3ec88dd082
+  - 4a46eba1-598a-4804-b669-dc96f31d2205
   - 38d2394f-f064-47a1-89d0-078597b78412
 topics:
   - applications
diff --git a/src/content/docs/design/brand/link-to-homepage.mdx b/src/content/docs/design/brand/link-to-homepage.mdx
index 3da5dea07..a06db7bda 100644
--- a/src/content/docs/design/brand/link-to-homepage.mdx
+++ b/src/content/docs/design/brand/link-to-homepage.mdx
@@ -6,7 +6,7 @@ sidebar:
   order: 4
 relatedArticles:
   - b3081ca1-2aa1-45e3-a42f-5295aac49bc3
-  - 6c70b7ae-1b1b-43bb-bea1-9b3ec88dd082
+  - 4a46eba1-598a-4804-b669-dc96f31d2205
 topics:
   - design
   - brand
diff --git a/src/content/docs/developer-tools/guides/deploy-on-vercel.mdx b/src/content/docs/developer-tools/guides/deploy-on-vercel.mdx
index 6b4288430..3c5266d2d 100644
--- a/src/content/docs/developer-tools/guides/deploy-on-vercel.mdx
+++ b/src/content/docs/developer-tools/guides/deploy-on-vercel.mdx
@@ -72,7 +72,7 @@ If you don’t have an existing project, create a project with a starter kit fro
 
 1. Sign in to your [Kinde](kinde.com) business and go to **Settings.**
 2. Select **Applications.**
-3. If you do not have any applications yet, create one. [Follow this guide](https://docs.kinde.com/build/applications/add-and-manage-applications/).
+3. If you do not have any applications yet, create one. [Follow this guide](/build/applications/about-applications/).
 4. If you have already created your app, select **View details** on the application tile. 
 5. Scroll to the **App keys** section and copy the **Domain, Client ID, and Client secret** somewhere you can access it again.
     
diff --git a/src/content/docs/developer-tools/sdks/backend/remix-sdk.mdx b/src/content/docs/developer-tools/sdks/backend/remix-sdk.mdx
index 50da17958..acef2bdd6 100644
--- a/src/content/docs/developer-tools/sdks/backend/remix-sdk.mdx
+++ b/src/content/docs/developer-tools/sdks/backend/remix-sdk.mdx
@@ -42,7 +42,7 @@ New to Kinde? [Get started here](/get-started/guides/first-things-first/).
 
 ## Create a back end application in Kinde
 
-The Remix SDK works with back end applications. Create one in Kinde. See [Add and manage applications](/build/applications/add-and-manage-applications/).
+The Remix SDK works with back end applications. Create one in Kinde. See [About applications](/build/applications/about-applications/).
 
 ## Install the Kinde Remix SDK into your Remix project
 
diff --git a/src/content/docs/get-started/connect/callback-urls.mdx b/src/content/docs/get-started/connect/callback-urls.mdx
index d8e4494ee..4dcf85181 100644
--- a/src/content/docs/get-started/connect/callback-urls.mdx
+++ b/src/content/docs/get-started/connect/callback-urls.mdx
@@ -6,7 +6,7 @@ sidebar:
 description: Guide to setting up callback and redirect URLs for Kinde authentication including troubleshooting, wildcard usage, and security considerations.
 relatedArticles:
   - 684fc526-a338-4a67-9af6-742a39b66aff
-  - 6c70b7ae-1b1b-43bb-bea1-9b3ec88dd082
+  - 4a46eba1-598a-4804-b669-dc96f31d2205
   - 6bf993fc-a195-4836-8eaf-133812be8876
 tableOfContents:
   maxHeadingLevel: 3
diff --git a/src/content/docs/get-started/connect/getting-app-keys.mdx b/src/content/docs/get-started/connect/getting-app-keys.mdx
index 090e02d41..eb9fe4e64 100644
--- a/src/content/docs/get-started/connect/getting-app-keys.mdx
+++ b/src/content/docs/get-started/connect/getting-app-keys.mdx
@@ -6,7 +6,7 @@ sidebar:
 description: Guide to obtaining and managing Kinde application keys including client ID, client secret, and security best practices for credential management.
 relatedArticles:
   - 684fc526-a338-4a67-9af6-742a39b66aff
-  - 6c70b7ae-1b1b-43bb-bea1-9b3ec88dd082
+  - 4a46eba1-598a-4804-b669-dc96f31d2205
   - b3081ca1-2aa1-45e3-a42f-5295aac49bc3
   - 6bf993fc-a195-4836-8eaf-133812be8876
 app_context:
diff --git a/src/content/docs/get-started/guides/byo-code.mdx b/src/content/docs/get-started/guides/byo-code.mdx
index 413688298..c39cb1ec9 100644
--- a/src/content/docs/get-started/guides/byo-code.mdx
+++ b/src/content/docs/get-started/guides/byo-code.mdx
@@ -53,7 +53,7 @@ If we don’t have the language or framework you’re looking for, and you’re
 
 Next, you’ll want to connect your code base to the application you set up in Kinde.
 
-Follow these steps to [add a new application to Kinde](/build/applications/add-and-manage-applications/). Kinde also comes with a couple of pre-built applications and you can use those ones if they suit.
+Follow these steps to [add a new application to Kinde](/build/applications/about-applications/). Kinde also comes with a couple of pre-built applications and you can use those ones if they suit.
 
 Sign in to Kinde and go to **Settings > Applications**.
 
diff --git a/src/content/docs/get-started/guides/start-with-starter-kit.mdx b/src/content/docs/get-started/guides/start-with-starter-kit.mdx
index 529b050cc..760352013 100644
--- a/src/content/docs/get-started/guides/start-with-starter-kit.mdx
+++ b/src/content/docs/get-started/guides/start-with-starter-kit.mdx
@@ -54,7 +54,7 @@ Open the README file in the starter kit for instructions on how to use it to con
 
 Kinde works by linking the application you set up in Kinde, with the app you’re creating yourself - or in this case, it will probably be an app that comes with the starter kit you chose.
 
-If you know what type of application you’re building, [add it to Kinde](/build/applications/add-and-manage-applications/). Kinde also comes with a couple of pre-built applications and you can use those ones if they suit. Go to **Settings > Applications**.
+If you know what type of application you’re building, [add it to Kinde](/build/applications/about-applications/). Kinde also comes with a couple of pre-built applications and you can use those ones if they suit. Go to **Settings > Applications**.
 
   ![kinde add application](https://imagedelivery.net/skPPZTHzSlcslvHjesZQcQ/494d739b-f60d-4f47-36f2-9e9f27f8c800/public)
 
diff --git a/src/content/docs/get-started/switch-to-kinde/auth0-to-kinde.mdx b/src/content/docs/get-started/switch-to-kinde/auth0-to-kinde.mdx
index 330a0b65d..2d7ae7ec1 100644
--- a/src/content/docs/get-started/switch-to-kinde/auth0-to-kinde.mdx
+++ b/src/content/docs/get-started/switch-to-kinde/auth0-to-kinde.mdx
@@ -162,7 +162,7 @@ Before you migrate, however, be aware that the functionality of these objects ma
 - Auth0 has the concept of [Tenants](https://auth0.com/docs/get-started/learn-the-basics) which group other objects such as users and applications together. Kinde calls these [Businesses](/build/set-up-options/run-multiple-businesses/) and is set up to allow you to run multiple businesses with a single Kinde account.
 - Both Kinde and Auth0 have [Organizations](/build/organizations/multi-tenancy-using-organizations/) to allow you to build multi-tenant applications. The main difference being that Kinde treats organizations as a first class citizen.
 - Each business Kinde allows you to have multiple [Environments](/build/environments/environments/) and these contain organizations, users and applications.
-- In Auth0, [Applications](https://auth0.com/docs/applications/set-up-an-application) are what your users can sign in to. They are also called [Applications](/build/applications/add-and-manage-applications/) in Kinde and work in essentially the same way.
+- In Auth0, [Applications](https://auth0.com/docs/applications/set-up-an-application) are what your users can sign in to. They are also called [Applications](/build/applications/about-applications/) in Kinde and work in essentially the same way.
 - In Auth0, [Identity Providers](https://auth0.com/docs/identityproviders) are a source of data for users. Kinde calls these connections or authentication providers.
 - In Auth0, [Roles and Permissions](https://auth0.com/docs/authorization/rbac/roles) provide information about what your users can do in your applications. Kinde also has [Roles](/manage-users/roles-and-permissions/user-roles/) and [Permissions](/manage-users/roles-and-permissions/user-permissions/) and they are assigned on a per user, per organization basis, meaning the same user can have different permissions in different organizations. For the Auth0 equivalent of user-level roles/permissions, use the [default organization](/build/organizations/orgs-for-developers/).
 - Kinde’s hosted sign-up pages are a very similar concept to [Auth0’s Universal Login](https://auth0.com/docs/authenticate/login/auth0-universal-login).
diff --git a/src/content/docs/integrate/third-party-tools/cloudflare-zero-trust.mdx b/src/content/docs/integrate/third-party-tools/cloudflare-zero-trust.mdx
index 8e3e9915b..b1ab87342 100644
--- a/src/content/docs/integrate/third-party-tools/cloudflare-zero-trust.mdx
+++ b/src/content/docs/integrate/third-party-tools/cloudflare-zero-trust.mdx
@@ -35,7 +35,7 @@ If you use Cloudflare to manage authentication across your systems, you can use
 
 This topic explains how to set up Cloudflare Zero Trust to use Kinde as an auth identity provider through OpenID Connect.
 
-You need to already have a backend [web application set up](/build/applications/add-and-manage-applications/) in Kinde to follow this procedure.
+You need to already have a backend [web application set up](/build/applications/about-applications/) in Kinde to follow this procedure.
 
 ## Get your Cloudflare team domain