diff --git a/docs/en/faq.md b/docs/en/faq.md
index 735dc3f7a69..e7d2766f0a6 100644
--- a/docs/en/faq.md
+++ b/docs/en/faq.md
@@ -30,7 +30,7 @@ Please refer to the official SeaTunnel documentation for the necessary steps to
 Yes, SeaTunnel supports CDC from MySQL replicas by subscribing to binlog logs, which are then parsed on the SeaTunnel server.
 
 ## Does SeaTunnel support CDC integration for tables without primary keys?
-No, SeaTunnel does not support CDC integration for tables without primary keys. This is because, in cases where two identical records exist in the upstream and one is deleted or modified, the downstream cannot determine which record to delete or modify, leading to potential issues. Having primary keys is essential for ensuring data uniqueness, similar to identifying the real Monkey King in the classic "Journey to the West."
+SeaTunnel does not support CDC integration for tables without primary keys. The reason is that if two identical records exist in the upstream and one is deleted or modified, the downstream cannot determine which record to delete or modify, leading to potential issues. Primary keys are essential to ensure data uniqueness.
 
 ## How does SeaTunnel handle changes in data sources (source) or data destinations (sink)?
 When the structure of a data source or destination changes, SeaTunnel provides various mechanisms to adapt, such as automatically detecting and updating the schema or configuring data mapping rules. You can adjust the `schema_save_mode` or `data_save_mode` parameters to control how these changes are handled based on your needs.