diff --git a/.markdownlint.yaml b/.markdownlint.yaml
index 178e1f7fd65b0..4ee86212623c4 100644
--- a/.markdownlint.yaml
+++ b/.markdownlint.yaml
@@ -1,4 +1,4 @@
-comment: 'Rules for PingCAP docs'
+comment: 'Markdownlint Rules for PingCAP docs'
 
 # disable all by default
 default: false
diff --git a/deploy-test-cluster-using-docker-compose.md b/deploy-test-cluster-using-docker-compose.md
index 7920c29afda86..966d68985c02c 100644
--- a/deploy-test-cluster-using-docker-compose.md
+++ b/deploy-test-cluster-using-docker-compose.md
@@ -7,14 +7,14 @@ aliases: ['/docs/stable/deploy-test-cluster-using-docker-compose/','/docs/v4.0/d
 
 # TiDB Docker Compose Deployment
 
+> **Warning:**
+>
+> The Docker Compose deployment method provided in this document is no longer maintained. If you want to test TiDB, it is recommended to refer to [Quick Start Guide for the TiDB Database Platform](/quick-start-with-tidb.md) for deployment. For **production environment**, **do not use** Docker Compose for deployment, but [deploy TiDB with TiUP](/production-deployment-using-tiup.md) or [TiDB Operator in Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/v1.1/deploy-tidb-operator).
+
 This document describes how to quickly deploy a TiDB testing cluster with a single command using [Docker Compose](https://docs.docker.com/compose/overview).
 
 With Docker Compose, you can use a YAML file to configure application services in multiple containers. Then, with a single command, you can create and start all the services from your configuration.
 
-> **Warning:**
->
-> This is for testing only. DO NOT USE in production! It is recommended to deploy TiDB using [TiUP](/production-deployment-using-tiup.md) or [TiDB Operator in Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/v1.1/deploy-tidb-operator) in production.
-
 ## Prerequisites
 
 Make sure you have installed the following items on your machine:
diff --git a/test-deployment-using-docker.md b/test-deployment-using-docker.md
index 23ae223122eb9..73616e2aa750e 100644
--- a/test-deployment-using-docker.md
+++ b/test-deployment-using-docker.md
@@ -7,13 +7,13 @@ aliases: ['/docs/stable/test-deployment-using-docker/','/docs/v4.0/test-deployme
 
 # Deploy TiDB Using Docker
 
-This page shows you how to manually deploy a multi-node TiDB cluster on multiple machines using Docker.
-
-To learn more, see [TiDB architecture](/architecture.md) and [Software and Hardware Recommendations](/hardware-and-software-requirements.md).
-
 > **Warning:**
 >
-> This is for testing only. DO NOT USE in production! It is recommended to deploy TiDB using [TiUP](/production-deployment-using-tiup.md) or [TiDB Operator in Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/v1.1/deploy-tidb-operator) in production.
+> The Docker deployment method provided in this document is no longer maintained. If you want to test TiDB, it is recommended to refer to [Quick Start Guide for the TiDB Database Platform](/quick-start-with-tidb.md) for deployment. For **production environment**, **do not use** Docker Compose for deployment, but [deploy TiDB with TiUP](/production-deployment-using-tiup.md) or [TiDB Operator in Kubernetes](https://docs.pingcap.com/tidb-in-kubernetes/v1.1/deploy-tidb-operator).
+
+This document shows you how to manually deploy a multi-node TiDB cluster on multiple machines using Docker.
+
+To learn more, see [TiDB architecture](/architecture.md) and [Software and Hardware Recommendations](/hardware-and-software-requirements.md).
 
 ## Preparation