gravitational · ptgott · Nov 9, 2023 · Nov 9, 2023
diff --git a/docs/pages/ai-assist.mdx b/docs/pages/ai-assist.mdx
@@ -11,17 +11,6 @@ This guide will help you understand how to set up and use Teleport Assist, an
 AI-powered assistant that helps you run commands, debug issues and navigate your
 infrastructure.
 
-<Details
-  title="Version warning"
-  opened={true}
-  min="12.0"
->
-
-Teleport Assist is available starting from Teleport `v12.4` for Teleport
-Community Edition.
-
-</Details>
-
 ### Architecture diagram
 
 ![Teleport Assist Architecture](../img/assist/architecture-diagram.png)
@@ -34,8 +23,8 @@ Community Edition.
 
 Before you get started with Teleport Assist, make sure you have the following:
 
-- A running Teleport Community Edition cluster. For details on how to set this
-  up, see our [Getting Started](./index.mdx) guide.
+- A running Teleport Community Edition cluster, v12.4 or higher. For details on
+  how to set this up, see our [Getting Started](./index.mdx) guide.
 - **OpenAI Account**: You will need an active OpenAI account with GPT-4 API
   access as Teleport Assist relies on OpenAI services.
 

diff --git a/docs/pages/architecture/tls-routing.mdx b/docs/pages/architecture/tls-routing.mdx
@@ -3,17 +3,6 @@ title: TLS Routing
 description: How Teleport implements a single-port setup with TLS routing
 ---
 
-<Details
-  title="Version warning"
-  opened={true}
-  scope={["oss", "enterprise"]}
-  scopeOnly={true}
-  min="13.0"
->
-  Support for TLS Routing behind layer 7 (HTTP/HTTPS) load balancers and reverse
-  proxies is available starting from Teleport `13.0`.
-</Details>
-
 In TLS routing mode [Teleport proxy](./proxy.mdx) multiplexes all client
 connections on a single TLS port.
 
@@ -26,6 +15,9 @@ To implement TLS routing, Teleport uses SNI ([Server Name Indication](https://en
 and ALPN ([Application-Level Protocol Negotiation](https://en.wikipedia.org/wiki/Application-Layer_Protocol_Negotiation))
 TLS extensions.
 
+Support for TLS Routing behind layer 7 (HTTP/HTTPS) load balancers and reverse
+proxies is available starting from Teleport `13.0`.
+
 ## How it works
 
 The Teleport Proxy Service listens for all client connections on its `web_listen_addr` by default:

diff --git a/docs/pages/choose-an-edition/teleport-enterprise/gcp-kms.mdx b/docs/pages/choose-an-edition/teleport-enterprise/gcp-kms.mdx
@@ -8,18 +8,6 @@ This guide will show you how to set up your Teleport Cluster to use the Google
 Cloud Key Management Service (KMS) to store and handle the CA private key
 material used to sign all certificates issued by your Teleport cluster.
 
-<Details
-  title="Version warning"
-  opened={true}
-  scope={["enterprise"]}
-  scopeOnly={true}
-  min="11.1.0"
->
-
-The features documented on this page are available in Teleport `11.1.0` and higher.
-
-</Details>
-
 Teleport generates private key material for its internal Certificate Authorities
 (CAs) during the first Auth Server's initial startup.
 These CAs are used to sign all certificates issued to clients and hosts in the
@@ -42,6 +30,9 @@ learn more.
 
 ## Prerequisites
 
+The features documented on this page are available in Teleport `11.1.0` and
+higher.
+
 (!docs/pages/includes/commercial-prereqs-tabs.mdx!)
 
 - (!docs/pages/includes/tctl.mdx!)

diff --git a/docs/pages/database-access/auto-user-provisioning/aws-redshift.mdx b/docs/pages/database-access/auto-user-provisioning/aws-redshift.mdx
@@ -3,22 +3,12 @@ title: AWS Redshift Automatic User Provisioning
 description: Configure automatic user provisioning for AWS Redshift.
 ---
 
-<Details
-  title="Version warning"
-  opened={true}
-  scope={["oss", "enterprise"]}
-  scopeOnly={true}
-  min="14.2"
->
-  Automatic user provisioning for AWS Redshift is available starting from
-  Teleport 14.2.
-</Details>
-
 (!docs/pages/includes/database-access/auto-user-provisioning/intro.mdx!)
 
 ## Prerequisites
 
-- Teleport cluster with a configured [AWS Redshift](../guides/postgres-redshift.mdx) database.
+- Teleport cluster v14.2 or higher with a configured [AWS
+  Redshift](../guides/postgres-redshift.mdx) database.
 - Ability to connect to and create user accounts in the target database.
 
 <Admonition type="note" title="Supported services">

diff --git a/docs/pages/database-access/auto-user-provisioning/mariadb.mdx b/docs/pages/database-access/auto-user-provisioning/mariadb.mdx
@@ -3,23 +3,13 @@ title: MariaDB Automatic User Provisioning
 description: Configure automatic user provisioning for MariaDB.
 ---
 
-<Details
-  title="Version warning"
-  opened={true}
-  scope={["oss", "enterprise"]}
-  scopeOnly={true}
-  min="14.2"
->
-  Automatic user provisioning for MariaDB is available starting from Teleport
-  14.2.
-</Details>
-
 (!docs/pages/includes/database-access/auto-user-provisioning/intro.mdx!)
 
 ## Prerequisites
 
-- Teleport cluster with a configured [self-hosted MariaDB](../guides/mysql-self-hosted.mdx)
-  or [RDS MariaDB](../guides/rds.mdx) database.
+- Teleport cluster v14.2 or higher with a configured [self-hosted
+  MariaDB](../guides/mysql-self-hosted.mdx) or [RDS MariaDB](../guides/rds.mdx)
+  database.
 - Ability to connect to and create user accounts in the target database.
 
 <Admonition type="note" title="Supported versions">

diff --git a/docs/pages/database-access/auto-user-provisioning/mysql.mdx b/docs/pages/database-access/auto-user-provisioning/mysql.mdx
@@ -3,21 +3,11 @@ title: MySQL Automatic User Provisioning
 description: Configure automatic user provisioning for MySQL.
 ---
 
-<Details
-  title="Version warning"
-  opened={true}
-  scope={["oss", "enterprise"]}
-  scopeOnly={true}
-  min="14.1"
->
-  Automatic user provisioning for MySQL is available starting from Teleport
-  14.1.
-</Details>
-
 ## Prerequisites
 
-- Teleport cluster with a configured [self-hosted MySQL](../guides/mysql-self-hosted.mdx)
-  or [RDS MySQL](../guides/rds.mdx) database.
+- Teleport cluster v14.1 or higher with a configured [self-hosted
+  MySQL](../guides/mysql-self-hosted.mdx) or [RDS MySQL](../guides/rds.mdx)
+  database.
 - Ability to connect to and create user accounts in the target database.
 
 <Admonition type="note" title="Supported versions">

diff --git a/docs/pages/database-access/auto-user-provisioning/postgres.mdx b/docs/pages/database-access/auto-user-provisioning/postgres.mdx
@@ -3,23 +3,13 @@ title: PostgreSQL Automatic User Provisioning
 description: Configure automatic user provisioning for PostgreSQL.
 ---
 
-<Details
-  title="Version warning"
-  opened={true}
-  scope={["oss", "enterprise"]}
-  scopeOnly={true}
-  min="13.1"
->
-  Automatic user provisioning for PostgreSQL is available starting from
-  Teleport 13.1.
-</Details>
-
 (!docs/pages/includes/database-access/auto-user-provisioning/intro.mdx!)
 
 ## Prerequisites
 
-- Teleport cluster with a configured [self-hosted PostgreSQL](../guides/postgres-self-hosted.mdx)
-  or [RDS PostgreSQL](../guides/rds.mdx) database.
+- Teleport cluster v13.1 or above with a configured [self-hosted
+  PostgreSQL](../guides/postgres-self-hosted.mdx) or [RDS
+  PostgreSQL](../guides/rds.mdx) database.
 - Ability to connect to and create user accounts in the target database.
 
 ## Step 1/3. Configure database admin

diff --git a/docs/pages/database-access/guides/aws-cassandra-keyspaces.mdx b/docs/pages/database-access/guides/aws-cassandra-keyspaces.mdx
@@ -3,16 +3,6 @@ title: Database Access with AWS Keyspaces (Apache Cassandra)
 description: How to configure Teleport database access with AWS Keyspaces (Apache Cassandra)
 ---
 
-<Details
-  title="Version warning"
-  opened={true}
-  scope={["oss", "enterprise"]}
-  scopeOnly={true}
-  min="11.0"
->
-  Database access for AWS Keyspaces (Apache Cassandra) is available starting from Teleport `v11.0`.
-</Details>
-
 (!docs/pages/includes/database-access/db-introduction.mdx  dbType="AWS Keyspaces (Apache Cassandra)" dbConfigure="AWS Keyspaces database with IAM authentication" dbName="AWS Keyspaces" !)
 
 <Tabs>
@@ -27,6 +17,9 @@ description: How to configure Teleport database access with AWS Keyspaces (Apach
 
 ## Prerequisites
 
+Database access for AWS Keyspaces (Apache Cassandra) is available starting from
+Teleport `v11.0`.
+
 (!docs/pages/includes/edition-prereqs-tabs.mdx!)
 
 - AWS Account with AWS Keyspaces database and permissions to create and attach IAM policies

diff --git a/docs/pages/database-access/guides/aws-cross-account.mdx b/docs/pages/database-access/guides/aws-cross-account.mdx
@@ -3,20 +3,12 @@ title: AWS Cross-Account Database Access
 description: How to connect AWS databases in external AWS accounts to Teleport.
 ---
 
-<Details
-  title="Version warning"
-  opened={true}
-  scope={["oss", "enterprise"]}
-  scopeOnly={true}
-  min="13.0"
->
-  AWS cross-account database access is available starting from Teleport `13.0`.
-</Details>
-
 You can deploy the Teleport Database Service with AWS IAM credentials in one
 AWS account and use an AWS IAM role to grant Teleport access to databases in
 another AWS account.
 
+AWS cross-account database access is available starting from Teleport `13.0`.
+
 When the Teleport Database Service needs to discover, configure, or retrieve
 short-lived authentication tokens for AWS databases, it uses credentials for an
 AWS IAM identity to make requests to the AWS API.

diff --git a/docs/pages/database-access/guides/azure-sql-server-ad.mdx b/docs/pages/database-access/guides/azure-sql-server-ad.mdx
@@ -3,17 +3,6 @@ title: Database Access with SQL Server on Azure
 description: How to configure Teleport database access with Azure SQL Server using Azure Active Directory authentication.
 ---
 
-<Details
-  title="Version warning"
-  opened={true}
-  scope={["oss", "enterprise"]}
-  scopeOnly={true}
-  min="11.0"
->
-  Database access for Azure SQL Server with Azure Active Directory authentication
-  is available starting from Teleport `11.0`.
-</Details>
-
 (!docs/pages/includes/database-access/db-introduction.mdx  dbType="Azure SQL Server" dbConfigure="Azure SQL Server using Azure Active Directory authentication" dbName="Azure SQL Server" !)
 
 <Tabs>
@@ -28,6 +17,9 @@ description: How to configure Teleport database access with Azure SQL Server usi
 
 ## Prerequisites
 
+Database access for Azure SQL Server with Azure Active Directory authentication
+is available starting from Teleport `11.0`.
+
 (!docs/pages/includes/edition-prereqs-tabs.mdx!)
 
 - SQL Server running on Azure.

diff --git a/docs/pages/database-access/guides/cassandra-self-hosted.mdx b/docs/pages/database-access/guides/cassandra-self-hosted.mdx
@@ -3,16 +3,6 @@ title: Database Access with Cassandra and ScyllaDB
 description: How to configure Teleport database access with Cassandra and ScyllaDB.
 ---
 
-<Details
-  title="Version warning"
-  opened={true}
-  scope={["oss", "enterprise"]}
-  scopeOnly={true}
-  min="11.0"
->
-  Database access for Cassandra & ScyllaDB is available starting from Teleport `v11.0`.
-</Details>
-
 (!docs/pages/includes/database-access/db-introduction.mdx  dbType="Cassandra or ScyllaDB" dbConfigure="Cassandra or ScyllaDB with mutual TLS authentication" dbName="Cassandra or ScyllaDB" !)
 
 <Tabs>
@@ -27,6 +17,9 @@ description: How to configure Teleport database access with Cassandra and Scylla
 
 ## Prerequisites
 
+Database access for Cassandra & ScyllaDB is available starting from Teleport
+`v11.0`.
+
 (!docs/pages/includes/edition-prereqs-tabs.mdx!)
 
 - Self-hosted Cassandra or ScyllaDB instance.

diff --git a/docs/pages/includes/machine-id/v2-config-warning.mdx b/docs/pages/includes/machine-id/v2-config-warning.mdx
@@ -1,9 +1,3 @@
-<Details
-  title="Version warning"
-  opened={true}
-  min="14.0"
->
-  This version of the guide uses the v2 `tbot` configuration. This version is only
-  supported by Teleport 14 and beyond. Change the selected version of the
-  documentation to view the guide for previous Teleport versions.
-</Details>
+This version of the guide uses the v2 `tbot` configuration. This version is only
+supported by Teleport 14 and beyond. Change the selected version of the
+documentation to view the guide for previous Teleport versions.
diff --git a/docs/pages/machine-id/deployment/gitlab.mdx b/docs/pages/machine-id/deployment/gitlab.mdx
@@ -3,16 +3,6 @@ title: Deploying Machine ID on GitLab CI
 description: How to install and configure Machine ID on GitLab CI
 ---
 
-<Details
-  title="Version warning"
-  opened={true}
-  scope={["oss", "enterprise"]}
-  scopeOnly={true}
-  min="12.2"
->
-  Machine ID for GitLab is available starting from Teleport `v12.2`.
-</Details>
-
 In this guide, you will use Teleport Machine ID to allow a GitLab pipeline to
 securely connect to a Teleport SSH node without the need for long-lived secrets.
 
@@ -27,6 +17,8 @@ control.
 
 ## Prerequisites
 
+Machine ID for GitLab is available starting from Teleport `v12.2`.
+
 (!docs/pages/includes/edition-prereqs-tabs.mdx!)
 
 - (!docs/pages/includes/tctl.mdx!)

diff --git a/docs/pages/management/operations/enroll-agent-into-automatic-updates.mdx b/docs/pages/management/operations/enroll-agent-into-automatic-updates.mdx
@@ -3,14 +3,6 @@ title: Enroll an agent into automatic updates
 description: How to enroll an agent into automatic updates
 ---
 
-<Details
-  title="Version warning"
-  opened={true}
-  min="13.0"
->
-  Automatic agent update is available starting from Teleport `13.0`.
-</Details>
-
 Teleport supports automatic agent updates for
 systemd-based Linux distributions using `apt`, `yum`, or `zypper` package
 managers, and Kubernetes clusters. The [automatic updates architecture
@@ -22,6 +14,8 @@ updates.
 
 ## Requirements
 
+Automatic agent update is available starting from Teleport `13.0`.
+
 <Tabs>
 <TabItem label="Self-hosted" scope="enterprise">
 - A Teleport Enterprise agent, either:

diff --git a/docs/pages/management/operations/self-hosted-automatic-agent-updates.mdx b/docs/pages/management/operations/self-hosted-automatic-agent-updates.mdx
@@ -3,16 +3,6 @@ title: Setting up self-hosted automatic agent updates
 description: How to setup automatic agent update for self-hosted Teleport
 ---
 
-<Details
-  title="Version warning"
-  opened={true}
-  scope={["enterprise"]}
-  scopeOnly={true}
-  min="13.0"
->
-  Automatic agent update is available starting from Teleport `13.0`.
-</Details>
-
 Teleport supports automatic agent updates for
 systemd-based Linux distributions using `apt`, `yum`, and `zypper` package managers,
 and Kubernetes clusters. The [automatic updates architecture 
@@ -35,7 +25,7 @@ Teleport v13.3.2 forward, including future major releases.
 
 ## Requirements
 
-- Self-hosted Teleport cluster running.
+- Self-hosted Teleport cluster v13.0 or higher.
 - `tctl` execution on the auth machine or a role allowing verbs `create`, `read`,
   `update`, `delete` on the resource `cluster_maintenance_config`.
 - Either: