Remove old CTP references

rwestMSFT · rwestMSFT · commit 71affcff33b7 · 2022-10-03T12:25:04.000-06:00
diff --git a/docs/linux/sql-server-linux-migrate-ssis.md b/docs/linux/sql-server-linux-migrate-ssis.md
@@ -83,8 +83,8 @@ For detailed info about the limitations and known issues of SSIS on Linux, see [
 
 For more info about SSIS on Linux, see the following blog posts:
 
--   [SSIS on Linux is available in SQL Server CTP2.1](https://blogs.msdn.microsoft.com/ssis/2017/05/17/ssis-helsinki-is-available-in-sql-server-vnext-ctp2-1/)
--   [ODBC is supported in SSIS on Linux (SQL Server CTP 2.1 refresh)](https://blogs.msdn.microsoft.com/ssis/2017/06/16/odbc-is-supported-in-ssis-on-linux-ssis-helsinki-ctp2-1-refresh/)
+-   [SSIS on Linux is available in SQL Server 2017 CTP 2.1](https://blogs.msdn.microsoft.com/ssis/2017/05/17/ssis-helsinki-is-available-in-sql-server-vnext-ctp2-1/)
+-   [ODBC is supported in SSIS on Linux (SQL Server 2017 CTP 2.1 refresh)](https://blogs.msdn.microsoft.com/ssis/2017/06/16/odbc-is-supported-in-ssis-on-linux-ssis-helsinki-ctp2-1-refresh/)
 
 ## More info about SSIS
 
diff --git a/docs/linux/sql-server-linux-setup-2022.md b/docs/linux/sql-server-linux-setup-2022.md
@@ -74,7 +74,7 @@ If you use **Network File System (NFS)** remote shares in production, note the f
 
 When you install or upgrade [!INCLUDE [sssql22-md](../includes/sssql22-md.md)], you get the latest version of SQL Server from your configured Microsoft repository.
 
-Although the quickstarts refer to the Cumulative Update **CU** repository, you must use the **mssql-server-preview** repository for CTP 2.1.
+Although the quickstarts refer to the Cumulative Update **CU** repository, you must use the `mssql-server-preview` repository for the preview version.
 
 For more information on repositories and how to configure them, see [Configure repositories for SQL Server on Linux](sql-server-linux-change-repo.md).
 
diff --git a/docs/linux/sql-server-linux-setup.md b/docs/linux/sql-server-linux-setup.md
@@ -21,7 +21,7 @@ ms.technology: linux
 This article provides guidance for installing, updating, and uninstalling [!INCLUDE [sssql17-md](../includes/sssql17-md.md)], and [!INCLUDE [sssql19-md](../includes/sssql19-md.md)] on Linux.
 
 > [!TIP]  
-> For installing [!INCLUDE [sssql22-md](../includes/sssql22-md.md)] CTP 2.1 on Linux, see [Installation guidance for SQL Server 2022 (16.x) Preview on Linux](./sql-server-linux-setup-2022.md).
+> For installing [!INCLUDE [sssql22-md](../includes/sssql22-md.md)] on Linux, see [Installation guidance for SQL Server 2022 (16.x) Preview on Linux](./sql-server-linux-setup-2022.md).
 
 For other deployment scenarios, see:
 
diff --git a/docs/relational-databases/security/authentication-access/azure-ad-authentication-sql-server-automation-setup-tutorial.md b/docs/relational-databases/security/authentication-access/azure-ad-authentication-sql-server-automation-setup-tutorial.md
@@ -25,11 +25,11 @@ In this article, we'll go over how to set up the Azure Active Directory (Azure A
 We'll also go over the updated functionality to set up an Azure AD admin for SQL Server in the Azure portal that would allow for automated certificate creation and application registration. Previously, setting up [Azure AD authentication for SQL server required manual setup of Azure AD admin with an Azure certificate and application registration](azure-ad-authentication-sql-server-setup-tutorial.md).
 
 > [!NOTE]
-> This feature is available in [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] CTP 2.1 or later versions, and is only supported for SQL Server on-premises, for Windows and Linux hosts. Azure Virtual Machines aren't supported.
+> This feature is available in [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] or later versions, and is only supported for SQL Server on-premises, for Windows and Linux hosts. Azure Virtual Machines aren't supported.
 
 ## Prerequisites
 
-- [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] CTP 2.1 or later is installed.
+- [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] or later is installed.
 - SQL Server is connected to Azure cloud. For more information, see [Connect your SQL Server to Azure Arc](../../../sql-server/azure-arc/connect.md).
 - Azure extension for SQL Server version 1.1.1795.50 or higher for Windows, or version 1.0.2018.1 or higher for Linux, is installed.
 - Access to Azure Active Directory is available for authentication purpose. For more information, see [Azure Active Directory authentication for SQL Server](azure-ad-authentication-sql-server-overview.md).
diff --git a/docs/relational-databases/security/authentication-access/server-level-roles.md b/docs/relational-databases/security/authentication-access/server-level-roles.md
@@ -66,7 +66,7 @@ The following table shows the fixed server-level roles and their capabilities.
 The following table shows additional fixed server-level roles that are introduced with [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] and their capabilities.
 
 > [!NOTE]
-> These server-level permissions are not available for Azure SQL Managed Instance or Azure Synapse Analytics. **##MS_PerformanceDefinitionReader##**, **##MS_ServerPerformanceStateReader##**, and **##MS_ServerSecurityStateReader##** is introduced in [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] CTP 2.1, and are not available in Azure SQL Database.
+> These server-level permissions are not available for Azure SQL Managed Instance or Azure Synapse Analytics. **##MS_PerformanceDefinitionReader##**, **##MS_ServerPerformanceStateReader##**, and **##MS_ServerSecurityStateReader##** is introduced in [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)], and are not available in Azure SQL Database.
 
 |Fixed server-level role |Description |
 |------------------------------|-----------------|  
diff --git a/docs/relational-databases/security/ledger/ledger-overview.md b/docs/relational-databases/security/ledger/ledger-overview.md
@@ -106,7 +106,7 @@ When a block is formed, its associated database digest is published and stored o
 Ledger provides the ability to automatically generate and store the database digests in [immutable storage](/azure/storage/blobs/immutable-storage-overview) or [Azure Confidential Ledger](/azure/confidential-ledger/index), to prevent tampering. Alternatively, users can manually generate database digests and store them in the location of their choice. Database digests are used for later verifying that the data stored in ledger tables hasn't been tampered with.
 
 > [!NOTE]
-> [Automatic digest management](ledger-how-to-enable-automatic-digest-storage.md) is only supported in Azure SQL Database and [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] CTP 2.1 or higher. Managing digests manually is supported both in Azure SQL Database and SQL Server.
+> [Automatic digest management](ledger-how-to-enable-automatic-digest-storage.md) is only supported in Azure SQL Database and [!INCLUDE [sssql22-md](../../../includes/sssql22-md.md)] or higher. Managing digests manually is supported both in Azure SQL Database and SQL Server.
 
 ### Ledger verification
 
