minor fixes

Author: danciaclara

mint.json

@@ -83,7 +83,7 @@
         {
           "group": "Airgapped Edition",
           "pages": [
-              "self-hosting/methods/airgapped-considerations",
+              "self-hosting/methods/airgapped-requirements",
               "self-hosting/methods/airgapped-edition",
               "self-hosting/methods/airgapped-edition-kubernetes",
               "self-hosting/methods/clone-docker-images"

self-hosting/methods/airgapped-edition-kubernetes.mdx

@@ -3,6 +3,11 @@ title: Deploy Plane Commercial in an Airgapped Kubernetes Environment
 sidebarTitle: For Kubernetes
 ---
 
+<Note>
+**IMPORTANT**  
+Airgapped deployments are available exclusively for Business plan customers. Contact our [sales team](mailto:[email protected]) for pricing and licensing information.
+</Note>
+
 This guide walks you through deploying Plane Enterprise in an airgapped Kubernetes environment using Helm charts and pre-packaged Docker images.
 
 ## What you'll need

self-hosting/methods/airgapped-edition.mdx

@@ -3,11 +3,12 @@ title:  Deploy Plane Commercial in an Airgapped Docker Environment
 sidebarTitle: For Docker
 ---
 
-This guide walks you through setting up the Commercial Airgapped Edition in an offline environment using our pre-packaged installation bundle.
-<Warning>
+<Note>
 **IMPORTANT**  
-These instructions are for new installations only. If you're migrating from an existing Community Edition to an air-gapped setup, follow [this guide](/self-hosting/manage/community-to-airgapped).
-</Warning>
+Airgapped deployments are available exclusively for Business plan customers. Contact our [sales team](mailto:[email protected]) for pricing and licensing information.
+</Note>
+
+This guide walks you through setting up the Commercial Airgapped Edition in an offline environment using our pre-packaged installation bundle.
 
 ## Prerequisites
 Before we get started, make sure your air-gapped machine has:

…ing/methods/airgapped-considerations.mdx …sting/methods/airgapped-requirements.mdxself-hosting/methods/airgapped-considerations.mdx renamed to self-hosting/methods/airgapped-requirements.mdx self-hosting/methods/airgapped-considerations.mdx renamed to self-hosting/methods/airgapped-requirements.mdx

@@ -3,15 +3,18 @@ title: Airgapped deployment architecture
 sidebarTitle: Overview
 ---
 
+<Note>
+**IMPORTANT**  
+Airgapped deployments are available exclusively for Business plan customers. Contact our [sales team](mailto:[email protected]) for pricing and licensing information.
+</Note>
+
 This document explains Plane's architecture and specific requirements for airgapped deployments. Review this before beginning your airgapped installation on [Docker](/self-hosting/methods/airgapped-edition) or [Kubernetes](/self-hosting/methods/airgapped-edition-kubernetes).
 
 ## What is an airgapped deployment?
 
 An airgapped deployment operates in a completely isolated network environment with no external internet connectivity. This isolation is common in highly regulated industries, government facilities, and organizations with strict security requirements.
 
-Plane supports fully airgapped deployments where all components—application services, databases, storage, and integrations—operate entirely within your isolated network perimeter.
-
-See [Plane architecture](/self-hosting/plane-architecture)
+Plane supports fully airgapped deployments where all components - application services, databases, storage, and integrations - operate entirely within your isolated network perimeter.
 
 ## Airgapped cluster architecture
 
@@ -21,7 +24,7 @@ Here's how Plane operates in an airgapped environment with internal enterprise a
 
 This diagram illustrates a critical principle: **all OAuth flows and API communication remain internal to the airgapped cluster**. When integrating with self-hosted GitHub Enterprise, GitLab, or other internal services, the entire authentication and data exchange happens within your isolated network — no internet access required.
 
-## Connectivity and telemetry
+For a detailed breakdown of Plane's services and infrastructure dependencies, see [Plane self-hosted architecture](/self-hosting/plane-architecture).
 
 **Critical guarantees for airgapped environments**