diff --git a/website/docs/table-design/data-distribution/ttl.md b/website/docs/table-design/data-distribution/ttl.md
index ad75d51f0f..a9c869e834 100644
--- a/website/docs/table-design/data-distribution/ttl.md
+++ b/website/docs/table-design/data-distribution/ttl.md
@@ -23,4 +23,4 @@ sidebar_position: 3
 Fluss supports TTL for data by setting the TTL attribute for tables with `'table.log.ttl' = '<duration>'` (default is 7 days). Fluss can periodically and automatically check for and clean up expired data in the table.
 
 For log tables, this attribute indicates the expiration time of the log table data.
-For primary key tables, this attribute indicates the expiration time of their binlog and does not represent the expiration time of the primary key table data. If you also want the data in the primary key table to expire automatically, please use [auto partitioning](partitioning.md).
+For primary key tables, this attribute indicates the expiration time of the changelog and does not represent the expiration time of the primary key table data. If you also want the data in the primary key table to expire automatically, please use [auto partitioning](partitioning.md).
diff --git a/website/docs/table-design/table-types/pk-table/index.md b/website/docs/table-design/table-types/pk-table/index.md
index bd102c92ad..8713e02368 100644
--- a/website/docs/table-design/table-types/pk-table/index.md
+++ b/website/docs/table-design/table-types/pk-table/index.md
@@ -136,9 +136,9 @@ For primary key tables, Fluss supports various kinds of querying abilities.
 ### Reads
 
 For a primary key table, the default read method is a full snapshot followed by incremental data. First, the
-snapshot data of the table is consumed, followed by the binlog data of the table.
+snapshot data of the table is consumed, followed by the changelog data of the table.
 
-It is also possible to only consume the binlog data of the table. For more details, please refer to the [Flink Reads](engine-flink/reads.md)
+It is also possible to only consume the changelog data of the table. For more details, please refer to the [Flink Reads](engine-flink/reads.md)
 
 ### Lookup