-If you are using a TiDB Cloud Serverless Tier cluster, change the `get_connection` function in `mysqlclient_example.py`:
+If you are using a TiDB Serverless cluster, change the `get_connection` function in `mysqlclient_example.py`:
```python
def get_connection(autocommit: bool = True) -> MySQLdb.Connection:
@@ -932,7 +932,7 @@ def get_connection(autocommit: bool = True) -> MySQLdb.Connection:
-If you are using a TiDB Cloud Serverless Tier cluster, change the `get_connection` function in `pymysql_example.py`:
+If you are using a TiDB Serverless cluster, change the `get_connection` function in `pymysql_example.py`:
```python
def get_connection(autocommit: bool = False) -> Connection:
@@ -971,7 +971,7 @@ def get_connection(autocommit: bool = False) -> Connection:
-If you are using a TiDB Cloud Serverless Tier cluster, change the `get_connection` function in `mysql_connector_python_example.py`:
+If you are using a TiDB Serverless cluster, change the `get_connection` function in `mysql_connector_python_example.py`:
```python
def get_connection(autocommit: bool = True) -> MySQLConnection:
diff --git a/develop/dev-guide-sample-application-spring-boot.md b/develop/dev-guide-sample-application-spring-boot.md
index e6c5b95f82faa..543842a1e6e4e 100644
--- a/develop/dev-guide-sample-application-spring-boot.md
+++ b/develop/dev-guide-sample-application-spring-boot.md
@@ -21,9 +21,9 @@ You can build your own application based on this example.
The following introduces how to start a TiDB cluster.
-**Use a TiDB Cloud Serverless Tier cluster**
+**Use a TiDB Serverless cluster**
-For detailed steps, see [Create a Serverless Tier cluster](/develop/dev-guide-build-cluster-in-cloud.md#step-1-create-a-serverless-tier-cluster).
+For detailed steps, see [Create a TiDB Serverless cluster](/develop/dev-guide-build-cluster-in-cloud.md#step-1-create-a-tidb-serverless-cluster).
**Use a local cluster**
@@ -33,7 +33,7 @@ For detailed steps, see [Deploy a local test cluster](/quick-start-with-tidb.md#
-See [Create a Serverless Tier cluster](/develop/dev-guide-build-cluster-in-cloud.md#step-1-create-a-serverless-tier-cluster).
+See [Create a TiDB Serverless cluster](/develop/dev-guide-build-cluster-in-cloud.md#step-1-create-a-tidb-serverless-cluster).
@@ -97,7 +97,7 @@ If you want to learn more about the code of this application, refer to [Implemen
### Step 5.1 Change parameters
-If you are using a TiDB Cloud Serverless Tier cluster, change the `spring.datasource.url`, `spring.datasource.username`, `spring.datasource.password` parameters in the `application.yml` (located in `src/main/resources`).
+If you are using a TiDB Serverless cluster, change the `spring.datasource.url`, `spring.datasource.username`, `spring.datasource.password` parameters in the `application.yml` (located in `src/main/resources`).
```yaml
spring:
diff --git a/develop/dev-guide-tidb-crud-sql.md b/develop/dev-guide-tidb-crud-sql.md
index cbf26a3b34549..92233d7e3a50f 100644
--- a/develop/dev-guide-tidb-crud-sql.md
+++ b/develop/dev-guide-tidb-crud-sql.md
@@ -9,7 +9,7 @@ This document briefly introduces how to use TiDB's CURD SQL.
## Before you start
-Please make sure you are connected to a TiDB cluster. If not, refer to [Build a TiDB Cluster in TiDB Cloud (Serverless Tier)](/develop/dev-guide-build-cluster-in-cloud.md#step-1-create-a-serverless-tier-cluster) to create a Serverless Tier cluster.
+Please make sure you are connected to a TiDB cluster. If not, refer to [Build a TiDB Serverless Cluster](/develop/dev-guide-build-cluster-in-cloud.md#step-1-create-a-tidb-serverless-cluster) to create a TiDB Serverless cluster.
## Explore SQL with TiDB
diff --git a/develop/dev-guide-update-data.md b/develop/dev-guide-update-data.md
index b0a96d7f84c5d..2dcb69a80ccbb 100644
--- a/develop/dev-guide-update-data.md
+++ b/develop/dev-guide-update-data.md
@@ -14,7 +14,7 @@ This document describes how to use the following SQL statements to update the da
Before reading this document, you need to prepare the following:
-- [Build a TiDB Cluster in TiDB Cloud (Serverless Tier)](/develop/dev-guide-build-cluster-in-cloud.md).
+- [Build a TiDB Serverless Cluster](/develop/dev-guide-build-cluster-in-cloud.md).
- Read [Schema Design Overview](/develop/dev-guide-schema-design-overview.md), [Create a Database](/develop/dev-guide-create-database.md), [Create a Table](/develop/dev-guide-create-table.md), and [Create Secondary Indexes](/develop/dev-guide-create-secondary-indexes.md).
- If you want to `UPDATE` data, you need to [insert data](/develop/dev-guide-insert-data.md) first.
diff --git a/encryption-at-rest.md b/encryption-at-rest.md
index 4fc25a549aa1d..31b3d51f03056 100644
--- a/encryption-at-rest.md
+++ b/encryption-at-rest.md
@@ -21,7 +21,7 @@ When a TiDB cluster is deployed, the majority of user data is stored on TiKV and
TiKV supports encryption at rest. This feature allows TiKV to transparently encrypt data files using [AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) in [CTR](https://en.wikipedia.org/wiki/Block_cipher_mode_of_operation) mode. To enable encryption at rest, an encryption key must be provided by the user and this key is called master key. TiKV automatically rotates data keys that it used to encrypt actual data files. Manually rotating the master key can be done occasionally. Note that encryption at rest only encrypts data at rest (namely, on disk) and not while data is transferred over network. It is advised to use TLS together with encryption at rest.
-Optionally, you can use AWS KMS for both cloud and on-premises deployments. You can also supply the plaintext master key in a file.
+Optionally, you can use AWS KMS for both cloud and self-hosted deployments. You can also supply the plaintext master key in a file.
TiKV currently does not exclude encryption keys and user data from core dumps. It is advised to disable core dumps for the TiKV process when using encryption at rest. This is not currently handled by TiKV itself.
diff --git a/explore-htap.md b/explore-htap.md
index 5d32d5cb3d9a2..ec62e5e4be6f4 100644
--- a/explore-htap.md
+++ b/explore-htap.md
@@ -13,7 +13,7 @@ This guide describes how to explore and use the features of TiDB Hybrid Transact
## Use cases
-TiDB HTAP can handle the massive data that increases rapidly, reduce the cost of DevOps, and be deployed in either on-premises or cloud environments easily, which brings the value of data assets in real time.
+TiDB HTAP can handle the massive data that increases rapidly, reduce the cost of DevOps, and be deployed in either self-hosted or cloud environments easily, which brings the value of data assets in real time.
The following are the typical use cases of HTAP:
diff --git a/garbage-collection-configuration.md b/garbage-collection-configuration.md
index f2857d6898d57..89e8beaacfcaf 100644
--- a/garbage-collection-configuration.md
+++ b/garbage-collection-configuration.md
@@ -20,7 +20,7 @@ Garbage collection is configured via the following system variables:
> **Note:**
>
-> This section is only applicable to on-premises TiDB. TiDB Cloud does not have a GC I/O limit by default.
+> This section is only applicable to TiDB Self-Hosted. TiDB Cloud does not have a GC I/O limit by default.
@@ -58,7 +58,7 @@ Based on the `DISTRIBUTED` GC mode, the mechanism of GC in Compaction Filter use
> **Note:**
>
-> The following examples of modifying TiKV configurations are only applicable to on-premises TiDB. For TiDB Cloud, the mechanism of GC in Compaction Filter is enabled by default.
+> The following examples of modifying TiKV configurations are only applicable to TiDB Self-Hosted. For TiDB Cloud, the mechanism of GC in Compaction Filter is enabled by default.
diff --git a/quick-start-with-tidb.md b/quick-start-with-tidb.md
index bc8cc211e691c..b1d29280d610e 100644
--- a/quick-start-with-tidb.md
+++ b/quick-start-with-tidb.md
@@ -14,7 +14,7 @@ This guide walks you through the quickest way to get started with TiDB. For non-
>
> The deployment method provided in this guide is **ONLY FOR** quick start, **NOT FOR** production.
>
-> - To deploy an on-premises production cluster, see [production installation guide](/production-deployment-using-tiup.md).
+> - To deploy a self-hosted production cluster, see [production installation guide](/production-deployment-using-tiup.md).
> - To deploy TiDB on Kubernetes, see [Get Started with TiDB on Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/stable/get-started).
> - To manage TiDB in the cloud, see [TiDB Cloud Quick Start](https://docs.pingcap.com/tidbcloud/tidb-cloud-quickstart).
diff --git a/releases/release-5.2.0.md b/releases/release-5.2.0.md
index 79f428d01dc80..3bca214609478 100644
--- a/releases/release-5.2.0.md
+++ b/releases/release-5.2.0.md
@@ -20,7 +20,7 @@ In v5.2, the key new features and improvements are as follows:
- Add the TiFlash I/O traffic limit feature to improve the stability of read and write for TiFlash
- TiKV introduces a new flow control mechanism to replace the previous RocksDB write stall mechanism to improve the stability of TiKV flow control
- Simplify the operation and maintenance of Data Migration (DM) to reduce the management cost.
-- TiCDC supports HTTP protocol OpenAPI to manage TiCDC tasks. It provides a more user-friendly operation method for both Kubernetes and on-premises environments. (Experimental feature)
+- TiCDC supports HTTP protocol OpenAPI to manage TiCDC tasks. It provides a more user-friendly operation method for both Kubernetes and self-hosted environments. (Experimental feature)
## Compatibility changes
@@ -165,7 +165,7 @@ In v5.2, the key new features and improvements are as follows:
### TiDB data share subscription
-TiCDC supports using the HTTP protocol (OpenAPI) to manage TiCDC tasks, which is a more user-friendly operation method for both Kubernetes and on-premises environments. (Experimental feature)
+TiCDC supports using the HTTP protocol (OpenAPI) to manage TiCDC tasks, which is a more user-friendly operation method for both Kubernetes and self-hosted environments. (Experimental feature)
[#2411](https://github.com/pingcap/tiflow/issues/2411)
@@ -210,7 +210,7 @@ Support running the `tiup playground` command on Mac computers with Apple M1 chi
- Support completing the garbage collection automatically for the bindings in the "deleted" status [#26206](https://github.com/pingcap/tidb/pull/26206)
- Support showing whether a binding is used for query optimization in the result of `EXPLAIN VERBOSE` [#26930](https://github.com/pingcap/tidb/pull/26930)
- Add a new status variation `last_plan_binding_update_time` to view the timestamp corresponding to the binding cache in the current TiDB instance [#26340](https://github.com/pingcap/tidb/pull/26340)
- - Support reporting an error when starting binding evolution or running `admin evolve bindings` to ban the baseline evolution (currently disabled in the on-premises TiDB version because it is an experimental feature) affecting other features [#26333](https://github.com/pingcap/tidb/pull/26333)
+ - Support reporting an error when starting binding evolution or running `admin evolve bindings` to ban the baseline evolution (currently disabled in the TiDB Self-Hosted version because it is an experimental feature) affecting other features [#26333](https://github.com/pingcap/tidb/pull/26333)
+ PD
diff --git a/releases/release-6.0.0-dmr.md b/releases/release-6.0.0-dmr.md
index 09526e32a9742..d2d3b5f286792 100644
--- a/releases/release-6.0.0-dmr.md
+++ b/releases/release-6.0.0-dmr.md
@@ -41,7 +41,7 @@ Starting from TiDB v6.0.0, TiDB provides two types of releases:
- Development Milestone Releases
- Development Milestone Releases (DMR) are released approximately every two months. A DMR introduces new features and improvements, but does not accept patch releases. It is not recommended for on-premises users to use DMR in production environments. For example, v6.0.0-DMR is a DMR.
+ Development Milestone Releases (DMR) are released approximately every two months. A DMR introduces new features and improvements, but does not accept patch releases. It is not recommended for users to use DMR in production environments. For example, v6.0.0-DMR is a DMR.
TiDB v6.0.0 is a DMR, and its version is 6.0.0-DMR.
@@ -266,7 +266,7 @@ TiDB v6.0.0 is a DMR, and its version is 6.0.0-DMR.
- An enterprise-level database management platform, TiDB Enterprise Manager
- TiDB Enterprise Manager (TiEM) is an enterprise-level database management platform based on the TiDB database, which aims to help users manage TiDB clusters in on-premises or public cloud environments.
+ TiDB Enterprise Manager (TiEM) is an enterprise-level database management platform based on the TiDB database, which aims to help users manage TiDB clusters in self-hosted or public cloud environments.
TiEM not only provides full lifecycle visual management for TiDB clusters, but also provides one-stop services: parameter management, version upgrades, cluster clone, active-standby cluster switching, data import and export, data replication, and data backup and restore services. TiEM can improve the efficiency of DevOps on TiDB and reduce the DevOps cost for enterprises.