Remove old preview references

Author: rwestMSFT

docs/database-engine/install-windows/supported-version-and-edition-upgrades.md

@@ -45,7 +45,7 @@ You can upgrade from [!INCLUDE [sql2008-md](../../includes/sql2008-md.md)], [!IN
 
 - Upgrade from an Evaluation edition of a previous [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] version isn't supported.
 
-- When you upgrade from RC1 or previous versions of SQL Server 2016 to RC3 or later versions, PolyBase must be uninstalled before the upgrade and reinstalled after the upgrade.
+- When you upgrade from previous versions to SQL Server 2016, PolyBase must be uninstalled before the upgrade and reinstalled after the upgrade.
 
 ## Upgrades from earlier versions to SQL Server 2016
 

docs/includes/entra-id-tutorial.md

@@ -64,7 +64,7 @@ In this tutorial, you learn how to:
 ## Create and register a Microsoft Entra application
 
 - Go to the [Azure portal](https://portal.azure.com), select **Microsoft Entra ID** > **App Registrations** > **New Registration**.
-  1. Specify a name - The example in this article uses *SQLServerCTP1*.
+  1. Specify a name - The example in this article uses *SQLServer*.
   1. Select **Supported account types** and use **Accounts in this organization directory only**
   1. Don't set a redirect URI
   1. Select **Register**

docs/integration-services/what-s-new-in-integration-services-in-sql-server-2016.md

@@ -216,7 +216,7 @@ The Incremental Package Deployment feature lets you deploy one or more packages
 
  The method GetIdentificationStringByLineageID has been renamed to <xref:Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSComponentMetaData130.GetIdentificationStringByID%2A>. For more info, see [Column names for errors in the data flow](#ErrorColumn).  
 
- For more info about this change and about the error column improvement, see the following updated blog post. [Error Column Improvements for SSIS Data Flow (Updated for CTP3.3)](https://techcommunity.microsoft.com/t5/sql-server-integration-services/error-column-improvements-for-ssis-data-flow-updated-for-rc2/ba-p/388253)  
+ For more info about this change and about the error column improvement, see the following updated blog post. [Error Column Improvements for SSIS Data Flow (Updated for RC2)](https://techcommunity.microsoft.com/blog/ssis/error-column-improvements-for-ssis-data-flow-updated-for-rc2/388253).  
 
 > [!NOTE]  
 > This method has been moved to the <xref:Microsoft.SqlServer.Dts.Pipeline.Wrapper.IDTSComponentMetaData130> interface. For more info, see [New IDTSComponentMetaData130 interface in the API](#CMD130).

docs/linux/sql-server-linux-docker-container-deployment.md

@@ -578,7 +578,7 @@ This updates the SQL Server image for any new containers you create, but it does
 1. Create a new SQL Server container with `docker run` and specify either a mapped host directory or a data volume container. Make sure to use the specific tag for your SQL Server upgrade. The new container now uses a new version of SQL Server with your existing SQL Server data.
 
    > [!IMPORTANT]  
-   > Upgrade is only supported between RC1, RC2, and GA at this time.
+   > Upgrade is only supported between release candidate previews and GA at this time.
 
 1. Verify your databases and data in the new container.
 

docs/linux/sql-server-linux-migrate-ssis.md

@@ -69,7 +69,7 @@ There are three ways to run an SSIS package that's encrypted with a password:
 
 ## Design packages
 
-**Connect to ODBC data sources**. With SSIS on Linux CTP 2.1 Refresh and later, SSIS packages can use ODBC connections on Linux. This functionality has been tested with the SQL Server and the MySQL ODBC drivers, but is also expected to work with any Unicode ODBC driver that observes the ODBC specification. At design time, you can provide either a DSN or a connection string to connect to the ODBC data; you can also use Windows authentication. For more info, see the [blog post announcing ODBC support on Linux](https://techcommunity.microsoft.com/blog/ssis/odbc-is-supported-in-ssis-on-linux-sql-server-2017-ctp-2-1-refresh/388346).
+**Connect to ODBC data sources**. With SSIS on Linux, SSIS packages can use ODBC connections on Linux. This functionality has been tested with the SQL Server and the MySQL ODBC drivers, but is also expected to work with any Unicode ODBC driver that observes the ODBC specification. At design time, you can provide either a DSN or a connection string to connect to the ODBC data; you can also use Windows authentication. For more info, see the [blog post announcing ODBC support on Linux](https://techcommunity.microsoft.com/blog/ssis/odbc-is-supported-in-ssis-on-linux-sql-server-2017-ctp-2-1-refresh/388346).
 
 **Paths**. Provide Windows-style paths in your SSIS packages. SSIS on Linux doesn't support Linux-style paths, but maps Windows-style paths to Linux-style paths at run time. Then, for example, SSIS on Linux maps the Windows-style path `C:\test` to the Linux-style path `/test`.
 
@@ -89,8 +89,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 2017 CTP 2.1](https://techcommunity.microsoft.com/category/sql-server/blog/ssis)
-- [ODBC is supported in SSIS on Linux (SQL Server 2017 CTP 2.1 refresh)](https://techcommunity.microsoft.com/category/sql-server/blog/ssis)
+- [SSIS on Linux is available in SQL Server 2017](https://techcommunity.microsoft.com/category/sql-server/blog/ssis)
+- [ODBC is supported in SSIS on Linux (SQL Server 2017)](https://techcommunity.microsoft.com/category/sql-server/blog/ssis)
 
 ## More info about SSIS
 

docs/relational-databases/search/query-with-full-text-search.md

@@ -26,7 +26,7 @@ Write full-text queries by using the predicates **CONTAINS** and **FREETEXT** an
 
 ## <a name="examples_simple"></a> Examples of each predicate and function
 
-The following examples use the AdventureWorks sample database. For the final release of AdventureWorks, see [AdventureWorks Databases and Scripts for SQL Server 2016 CTP3](https://github.com/microsoft/sql-server-samples/releases/tag/adventureworks). To run the sample queries, you also have to set up Full-Text Search. For more info, see [Get Started with Full-Text Search](get-started-with-full-text-search.md). 
+The following examples use the AdventureWorks sample database. For the final release of AdventureWorks, see [AdventureWorks sample databases](https://github.com/microsoft/sql-server-samples/releases/tag/adventureworks). To run the sample queries, you also have to set up Full-Text Search. For more info, see [Get Started with Full-Text Search](get-started-with-full-text-search.md). 
 
 ### Example - CONTAINS  
 The following example finds all products with a price of `$80.99` that contain the word `"Mountain"`:

docs/relational-databases/security/authentication-access/microsoft-entra-authentication-sql-server-enable-without-arc.md

@@ -66,7 +66,7 @@ In this tutorial, you learn how to:
 ## Create and register a Microsoft Entra ID application
 
 - Go to the [Azure portal](https://portal.azure.com), select **Microsoft Entra ID** > **App Registrations** > **New Registration**.
-   1. Specify a name - The example in this article uses *SQLServerCTP1*.
+   1. Specify a name - The example in this article uses *SQLServer*.
    1. Select **Supported account types** and use **Accounts in this organization directory only**
    1. Don't set a redirect URI
    1. Select **Register**

docs/relational-databases/system-stored-procedures/sp-addlinkedserver-transact-sql.md

@@ -463,14 +463,14 @@ With pass-through authentication, the security context of the local login is car
 
 ### J. Use Microsoft SQL Server OLE DB Provider version 19
 
-The following example creates a linked server named `SQLSales`, targeting a SQL Server named `LABSQL2025` with instance name `SQL2025CTP2`, using OLE DB version 19, Encryption is disabled.
+The following example creates a linked server named `SQLSales`, targeting a SQL Server named `LABSQL2025` with instance name `SQL2025`, using OLE DB version 19, encryption is disabled.
 
 ```sql
 EXECUTE sp_addlinkedserver
     @server = N'SQLSales',
     @srvproduct = N'',
     @provider = N'MSOLEDBSQL19',
-    @datasrc = N'LABSQL2025\SQL2025CTP2',
+    @datasrc = N'LABSQL2025\SQL2025',
     @provstr = N'Encrypt=No;';
 ```
 

docs/ssma/access/what-s-new-in-ssma-for-access-accesstosql.md

@@ -323,7 +323,7 @@ The v7.2 release of SSMA for Access contains the following changes:
 
 The v7.1 release of SSMA for Access contains the following changes:
 
-- SQL Server 2017 on Windows and Linux CTP1 is now a supported target platform for migration. This feature is in technical preview and supports schema and data movement to target SQL Server instances.
+- SQL Server 2017 Preview on Windows and Linux is now a supported target platform for migration. This feature is in technical preview and supports schema and data movement to target SQL Server instances.
 - SSMA now supports automatic updates to download the latest version of SSMA as soon as it's available.
 - SSMA installable binaries are now delivered through Windows Installer package files (.msi).
 

docs/ssma/db2/what-s-new-in-ssma-for-db2-db2tosql.md

@@ -416,7 +416,7 @@ The v7.2 release of SSMA for Db2 contains the following changes:
 
 The v7.1 release of SSMA for Db2 contains the following changes:
 
-- SQL Server 2017 on Windows and Linux CTP1 is now a supported target platform for migration. This feature is in technical preview and allows schema and data movement to target SQL Server instances.
+- SQL Server 2017 Preview on Windows and Linux is now a supported target platform for migration. This feature is in technical preview and allows schema and data movement to target SQL Server instances.
 
 - Support for automatic updates to download the latest version of SSMA as soon as it's available.