diff --git a/ticdc/ticdc-overview.md b/ticdc/ticdc-overview.md
index 32a895f7b566c..48e811eee8da8 100644
--- a/ticdc/ticdc-overview.md
+++ b/ticdc/ticdc-overview.md
@@ -86,10 +86,6 @@ As shown in the architecture diagram, TiCDC supports replicating data to TiDB, M
 
 - To ensure eventual consistency when using TiCDC for disaster recovery, you need to configure [redo log](/ticdc/ticdc-sink-to-mysql.md#eventually-consistent-replication-in-disaster-scenarios) and ensure that the storage system where the redo log is written can be read normally when a disaster occurs in the upstream.
 
-> **Note:**
->
-> Since v4.0.8, TiCDC supports replicating tables without a valid index by modifying the task configuration. However, this compromises the guarantee of data consistency to some extent. For more details, see [Replicate tables without a valid index](/ticdc/ticdc-manage-changefeed.md#replicate-tables-without-a-valid-index).
-
 ## Implementation of processing data changes
 
 This section mainly describes how TiCDC processes data changes generated by upstream DML operations.