update MD by dispatch event pingcap/docs feature/preview-top-navigation

Author: github-actions

markdown-pages/en/tidb/release-8.5/TOC-develop.md

@@ -20,7 +20,6 @@
     - [VS Code](/develop/dev-guide-gui-vscode-sqltools.md)
     - [MySQL Workbench](/develop/dev-guide-gui-mysql-workbench.md)
     - [Navicat](/develop/dev-guide-gui-navicat.md)
-    - [Looker Studio](/develop/dev-guide-bi-looker-studio.md)
   - Drivers & ORMs
     - [Choose a Driver or ORM](/develop/dev-guide-choose-driver-or-orm.md)
     - Java

markdown-pages/en/tidb/release-8.5/develop/dev-guide-bookshop-schema-design.md

@@ -12,12 +12,12 @@ To make your reading on the application developer guide more smoothly, we presen
 
 ## Import table structures and data
 
-Do one of the following:
+To import table structures and data of the Bookshop application, choose one of the following import methods:
 
-- For TiDB Cloud, you can skip [Method 1: Via `tiup demo`](#method-1-via-tiup-demo) and import Bookshop table structures [via the import feature of TiDB Cloud](#method-2-via-tidb-cloud-import).
-- For TiDB Self-Managed, you can import Bookshop table structures and data either [via TiUP](#method-1-via-tiup-demo) and skip [Method 2: Via TiDB Cloud Import](#method-2-via-tidb-cloud-import).
+- [TiDB Self-Managed: via `tiup demo`](#tidb-self-managed-via-tiup-demo).
+- [TiDB Cloud: via the Import feature](#tidb-cloud-via-the-import-feature).
 
-### Method 1: Via `tiup demo`
+### TiDB Self-Managed: via `tiup demo`
 
 If your TiDB cluster is deployed using [TiUP](/tiup/tiup-reference.md#tiup-reference) or you can connect to your TiDB server, you can quickly generate and import sample data for the Bookshop application by running the following command:
 
@@ -71,7 +71,7 @@ tiup demo bookshop prepare --users=200000 --books=500000 --authors=100000 --rati
 
 You can delete the original table structure through the `--drop-tables` parameter. For more parameter descriptions, run the `tiup demo bookshop --help` command.
 
-### Method 2: Via TiDB Cloud Import
+### TiDB Cloud: via the Import feature
 
 1. Open the **Import** page for your target cluster.
 

markdown-pages/en/tidb/release-8.5/develop/dev-guide-connection-parameters.md

@@ -8,7 +8,13 @@ aliases: ['/tidb/stable/dev-guide-connection-parameters/','/tidb/dev/dev-guide-c
 
 This document describes how to configure connection pools and connection parameters when you use a driver or ORM framework to connect to TiDB.
 
-If you are interested in more tips about Java application development, see [Best Practices for Developing Java Applications with TiDB](/develop/java-app-best-practices.md#connection-pool)
+> **Tip:**
+>
+> In this document, the following sections are excerpted from [Best Practices for Developing Java Applications with TiDB](/develop/java-app-best-practices.md):
+>
+> - [Configure the number of connections](#configure-the-number-of-connections)
+> - [Probe configuration](#probe-configuration)
+> - [Connection parameters](#connection-parameters)
 
 ## Connection pool
 

markdown-pages/en/tidb/release-8.5/develop/dev-guide-delete-data.md

@@ -161,11 +161,10 @@ with connection:
 
 </SimpleTab>
 
-The `rated_at` field is of the `DATETIME` type in [Date and Time Types](/data-type-date-and-time.md). You can assume that it is stored as a literal quantity in TiDB, independent of the time zone. On the other hand, the `TIMESTAMP` type stores a timestamp and thus displays a different time string in a different [time zone](/configure-time-zone.md).
-
 > **Note:**
 >
-> Like MySQL, the `TIMESTAMP` data type is affected by the [year 2038 problem](https://en.wikipedia.org/wiki/Year_2038_problem). It is recommended to use the `DATETIME` type if you store values larger than 2038.
+> - The `rated_at` field is of the `DATETIME` type in [Date and Time Types](/data-type-date-and-time.md). You can assume that it is stored as a literal quantity in TiDB, independent of the time zone. On the other hand, the `TIMESTAMP` type stores a timestamp and thus displays a different time string in a different [time zone](/configure-time-zone.md).
+> - Like MySQL, the `TIMESTAMP` data type is affected by the [year 2038 problem](https://en.wikipedia.org/wiki/Year_2038_problem). It is recommended to use the `DATETIME` type if you store values larger than 2038.
 
 ## Performance considerations
 

markdown-pages/en/tidb/release-8.5/develop/dev-guide-get-data-from-single-table.md

@@ -114,7 +114,7 @@ public class AuthorDAO {
 }
 ```
 
-After [connecting to TiDB using the JDBC driver](/develop/dev-guide-choose-driver-or-orm.md#java-drivers), you can create a `Statement` object with `conn.createStatus()`, and then call `stmt.executeQuery("query_sql")` to initiate a database query request to TiDB.
+After [connecting to TiDB using the JDBC driver](/develop/dev-guide-sample-application-java-jdbc.md), you can create a `Statement` object with `conn.createStatement()`, and then call `stmt.executeQuery("query_sql")` to initiate a database query request to TiDB.
 
 The query results are stored in a `ResultSet` object. By traversing `ResultSet`, the returned results can be mapped to the `Author` object.
 

markdown-pages/en/tidb/release-8.5/develop/dev-guide-insert-data.md

@@ -236,15 +236,15 @@ The following are the recommended tools for bulk-insert:
 <SimpleTab groupId="platform">
 <div label="TiDB Cloud" value="tidb-cloud">
 
-- Data export: [Dumpling](https://docs.pingcap.com/tidb/stable/dumpling-overview). You can export MySQL or TiDB data to local or Amazon S3. For a TiDB Cloud Starter or Essential cluster, you can also use the [Export](/tidb-cloud/serverless-export.md) feature to export data more efficiently.
-- Data import: [Import](/tidb-cloud/import-sample-data.md) page in the [TiDB Cloud console](https://tidbcloud.com/). You can import **Dumpling** exported data, import a local **CSV** file, or [Import CSV Files from Amazon S3 or GCS into TiDB Cloud](/tidb-cloud/import-csv-files.md). It also supports reading data from a local disk, Amazon S3 cloud disk, or GCS cloud disk.
-- Data replication: [TiDB Data Migration](https://docs.pingcap.com/tidb/stable/dm-overview). You can replicate MySQL, MariaDB, and Amazon Aurora databases to TiDB. It also supports merging and migrating the sharded instances and tables from the source databases.
-- Data backup and restore: [Backup](/tidb-cloud/backup-and-restore.md) page in the TiDB Cloud console. Compared to **Dumpling**, backup and restore is more suitable for **_big data_** scenario.
+- Data export: use [Dumpling](/dumpling-overview.md) to export MySQL or TiDB data to local or your cloud storage. For a TiDB Cloud Starter or Essential cluster, you can also use the [Export](/tidb-cloud/serverless-export.md) feature in the [TiDB Cloud console](https://tidbcloud.com/) to export data more efficiently.
+- Data import: use the [Import](/tidb-cloud/import-sample-data.md) feature in the [TiDB Cloud console](https://tidbcloud.com/). You can import Dumpling exported data, import a local CSV file, or [import CSV files from cloud storage into TiDB Cloud](/tidb-cloud/import-csv-files.md).
+- Data replication: use the [TiDB Data Migration](/tidb-cloud/migrate-from-mysql-using-data-migration.md) feature in the [TiDB Cloud console](https://tidbcloud.com/). You can replicate MySQL-compatible databases to TiDB. It also supports merging and migrating the sharded instances and tables from the source databases.
+- Data backup and restore: use the [Backup](/tidb-cloud/backup-and-restore.md) feature in the [TiDB Cloud console](https://tidbcloud.com/). Compared to Dumpling, backup and restore is more suitable for big data scenario.
 
 </div>
 <div label="TiDB Self-Managed" value="tidb">
 
-- Data export: [Dumpling](https://docs.pingcap.com/tidb/stable/dumpling-overview). You can export MySQL or TiDB data to local or Amazon S3.
+- Data export: [Dumpling](/dumpling-overview.md). You can export MySQL or TiDB data to local or Amazon S3.
 - Data import: [TiDB Lightning](/tidb-lightning/tidb-lightning-overview.md). You can import **Dumpling** exported data, a **CSV** file, or [Migrate Data from Amazon Aurora to TiDB](/migrate-aurora-to-tidb.md). It also supports reading data from a local disk or Amazon S3 cloud disk.
 - Data replication: [TiDB Data Migration](/dm/dm-overview.md). You can replicate MySQL, MariaDB, and Amazon Aurora databases to TiDB. It also supports merging and migrating the sharded instances and tables from the source databases.
 - Data backup and restore: [Backup & Restore (BR)](/br/backup-and-restore-overview.md). Compared to **Dumpling**, **BR** is more suitable for **_big data_** scenario.

markdown-pages/en/tidb/release-8.5/develop/dev-guide-third-party-tools-compatibility.md

@@ -41,10 +41,10 @@ MySQL maintains a series of [server status variables starting with `Com_`](https
 
 **Way to avoid**
 
-Do not use these variables. One common scenario is monitoring. TiDB is well observable and does not require querying from server status variables.
+Do not use these variables. One common scenario is monitoring. TiDB is well observable and does not require querying from server status variables. For more information about monitoring services, refer to the following documentation:
 
-- For more information about TiDB Cloud monitoring services, see [Monitor a TiDB Cluster](/tidb-cloud/monitor-tidb-cluster.md).
-- For more information about TiDB Self-Managed monitoring tools, see [TiDB Monitoring Framework Overview](/tidb-monitoring-framework.md).
+- TiDB Cloud documentation: [Monitor a TiDB Cluster](/tidb-cloud/monitor-tidb-cluster.md).
+- TiDB Self-Managed documentation: [TiDB Monitoring Framework Overview](/tidb-monitoring-framework.md).
 
 ### TiDB distinguishes between `TIMESTAMP` and `DATETIME` in error messages
 

markdown-pages/en/tidb/release-8.5/develop/dev-guide-use-follower-read.md

@@ -20,12 +20,10 @@ By default, TiDB only reads and writes data on the leader of the same Region. Wh
 
 You can visually analyze whether your application has a hotspot Region by doing one of the following:
 
-- For TiDB Cloud, use [Key Visualizer in the TiDB Cloud console](/tidb-cloud/tune-performance.md#key-visualizer) to analyze the hotspot Region.
-- For TiDB Self-Managed, use [Key Visualizer in TiDB Dashboard](/dashboard/dashboard-key-visualizer.md) to analyze the hotspot Region.
+- TiDB Cloud: navigate to the [Key Visualizer in the TiDB Cloud console](/tidb-cloud/tune-performance.md#key-visualizer), and then check whether a read hotspot occurs by selecting the "metrics selection box" to `Read (bytes)` or `Read (keys)`.
+- TiDB Self-Managed: navigate to the [Key Visualizer in TiDB Dashboard](/dashboard/dashboard-key-visualizer.md), and then check whether a read hotspot occurs by selecting the "metrics selection box" to `Read (bytes)` or `Read (keys)`.
 
-You can check whether a read hotspot occurs by selecting the "metrics selection box" to `Read (bytes)` or `Read (keys)`.
-
-For more information about handling hotspot, see [Troubleshoot Hotspot Issues](/troubleshoot-hot-spot-issues.md).
+If hotspot issues do exist, you can troubleshoot them by referring to [Handle TiDB Hotspot Issues](/troubleshoot-hot-spot-issues.md), which helps to avoid hotspot generation at the application level.
 
 If read hotspots are unavoidable or the changing cost is very high, you can try using the Follower Read feature to better load the balance of reading requests to the follower Region.
 

markdown-pages/en/tidbcloud/master/develop/dev-guide-bookshop-schema-design.md

@@ -12,12 +12,12 @@ To make your reading on the application developer guide more smoothly, we presen
 
 ## Import table structures and data
 
-Do one of the following:
+To import table structures and data of the Bookshop application, choose one of the following import methods:
 
-- For TiDB Cloud, you can skip [Method 1: Via `tiup demo`](#method-1-via-tiup-demo) and import Bookshop table structures [via the import feature of TiDB Cloud](#method-2-via-tidb-cloud-import).
-- For TiDB Self-Managed, you can import Bookshop table structures and data either [via TiUP](#method-1-via-tiup-demo) and skip [Method 2: Via TiDB Cloud Import](#method-2-via-tidb-cloud-import).
+- [TiDB Self-Managed: via `tiup demo`](#tidb-self-managed-via-tiup-demo).
+- [TiDB Cloud: via the Import feature](#tidb-cloud-via-the-import-feature).
 
-### Method 1: Via `tiup demo`
+### TiDB Self-Managed: via `tiup demo`
 
 If your TiDB cluster is deployed using [TiUP](/tiup/tiup-reference.md#tiup-reference) or you can connect to your TiDB server, you can quickly generate and import sample data for the Bookshop application by running the following command:
 
@@ -71,7 +71,7 @@ tiup demo bookshop prepare --users=200000 --books=500000 --authors=100000 --rati
 
 You can delete the original table structure through the `--drop-tables` parameter. For more parameter descriptions, run the `tiup demo bookshop --help` command.
 
-### Method 2: Via TiDB Cloud Import
+### TiDB Cloud: via the Import feature
 
 1. Open the **Import** page for your target cluster.
 

markdown-pages/en/tidbcloud/master/develop/dev-guide-connection-parameters.md

@@ -8,7 +8,13 @@ aliases: ['/tidb/stable/dev-guide-connection-parameters/','/tidb/dev/dev-guide-c
 
 This document describes how to configure connection pools and connection parameters when you use a driver or ORM framework to connect to TiDB.
 
-If you are interested in more tips about Java application development, see [Best Practices for Developing Java Applications with TiDB](/develop/java-app-best-practices.md#connection-pool)
+> **Tip:**
+>
+> In this document, the following sections are excerpted from [Best Practices for Developing Java Applications with TiDB](/develop/java-app-best-practices.md):
+>
+> - [Configure the number of connections](#configure-the-number-of-connections)
+> - [Probe configuration](#probe-configuration)
+> - [Connection parameters](#connection-parameters)
 
 ## Connection pool