Fix CustomContent format in note (#11601) (#11605)

TOC-tidb-cloud.md

@@ -71,6 +71,9 @@
       - [SQL Development Specifications](/develop/dev-guide-sql-development-specification.md)
   - Cloud Native Development Environment
     - [Gitpod](/develop/dev-guide-playground-gitpod.md)
+  - Third-Party Support
+    - [Third-Party Tools Supported by TiDB](/develop/dev-guide-third-party-support.md)
+    - [Known Incompatibility Issues with Third-Party Tools](/develop/dev-guide-third-party-tools-compatibility.md)
 - Manage Cluster
   - Plan Your Cluster
     - [Select Your Cluster Tier](/tidb-cloud/select-cluster-tier.md)
@@ -273,6 +276,7 @@
       - [`REVOKE <privileges>`](/sql-statements/sql-statement-revoke-privileges.md)
       - [`REVOKE <role>`](/sql-statements/sql-statement-revoke-role.md)
       - [`ROLLBACK`](/sql-statements/sql-statement-rollback.md)
+      - [`SAVEPOINT`](/sql-statements/sql-statement-savepoint.md)
       - [`SELECT`](/sql-statements/sql-statement-select.md)
       - [`SET DEFAULT ROLE`](/sql-statements/sql-statement-set-default-role.md)
       - [`SET [NAMES|CHARACTER SET]`](/sql-statements/sql-statement-set-names.md)

develop/dev-guide-choose-driver-or-orm.md

@@ -11,14 +11,9 @@ summary: Learn how to choose a driver or ORM framework to connect to TiDB.
 >
 > - **Full**: indicates that using this driver or ORM does not have any known issues.
 > - **Verified**: indicates that using this driver or ORM might get errors because of compatibility differences between TiDB and MySQL.
-
-<CustomContent platform="tidb">
-
 >
 > For more information, refer to [Third-Party Tools Supported by TiDB](/develop/dev-guide-third-party-support.md).
 
-</CustomContent>
-
 TiDB is highly compatible with the MySQL protocol but some features are incompatible with MySQL.
 
 For example:
@@ -109,13 +104,9 @@ implementation group: 'org.bouncycastle', name: 'bcpkix-jdk15on', version: '1.67
 > **Note:**
 >
 > - Currently, Hibernate does [not support nested transactions](https://stackoverflow.com/questions/37927208/nested-transaction-in-spring-app-with-jpa-postgres).
-
-<CustomContent platform="tidb">
-
+>
 > - Since v6.2.0, TiDB supports [savepoint](/sql-statements/sql-statement-savepoint.md). To use the `Propagation.NESTED` transaction propagation option in `@Transactional`, that is, to set `@Transactional(propagation = Propagation.NESTED)`, make sure that your TiDB is v6.2.0 or later.
 
-</CustomContent>
-
 <SimpleTab>
 <div label="Hibernate">
 

develop/dev-guide-third-party-tools-compatibility.md

@@ -39,8 +39,18 @@ MySQL maintains a series of [server status variables starting with `Com_`](https
 
 **Way to avoid**
 
+<CustomContent platform="tidb">
+
 Do not use these variables. One common scenario is monitoring. TiDB is well observable and does not require querying from server status variables. For custom monitoring tools, refer to [TiDB Monitoring Framework Overview](/tidb-monitoring-framework.md).
 
+</CustomContent>
+
+<CustomContent platform="tidb-cloud">
+
+Do not use these variables. One common scenario is monitoring. TiDB Cloud is well observable and does not require querying from server status variables. For more information about TiDB Cloud monitoring services, refer to [Monitor a TiDB Cluster](/tidb-cloud/monitor-tidb-cluster.md).
+
+</CustomContent>
+
 ### TiDB distinguishes between `TIMESTAMP` and `DATETIME` in error messages
 
 **Description**
@@ -49,8 +59,18 @@ TiDB error messages distinguish between `TIMESTAMP` and `DATETIME`, while MySQL
 
 **Way to avoid**
 
+<CustomContent platform="tidb">
+
 Do not use the error messages for string matching. Instead, use [Error Codes](/error-codes.md) for troubleshooting.
 
+</CustomContent>
+
+<CustomContent platform="tidb-cloud">
+
+Do not use the error messages for string matching. Instead, use [Error Codes](https://docs.pingcap.com/tidb/stable/error-codes) for troubleshooting.
+
+</CustomContent>
+
 ### TiDB does not support the `CHECK TABLE` statement
 
 **Description**