diff --git a/docs/content/maintenance/dedicated-compaction.md b/docs/content/maintenance/dedicated-compaction.md
index 45fb7ac68cf7..819ce448bb1d 100644
--- a/docs/content/maintenance/dedicated-compaction.md
+++ b/docs/content/maintenance/dedicated-compaction.md
@@ -151,7 +151,7 @@ CALL sys.compact(`table` => 'default.T', `where` => 'dt>10 and h<20');
 
 {{< hint info >}}
 Similarly, the default is synchronous compaction, which may cause checkpoint timeouts.
-You can configure `table_conf` to use [Asynchronous Compaction]({{< ref "maintenance/write-performance#asynchronous-compaction" >}}).
+You can configure `table_conf` to use [Asynchronous Compaction]({{< ref "primary-key-table/compaction#asynchronous-compaction" >}}).
 {{< /hint >}}
 
 ## Database Compaction Job
diff --git a/docs/content/maintenance/write-performance.md b/docs/content/maintenance/write-performance.md
index 6b3b0f09e43f..03e734874c05 100644
--- a/docs/content/maintenance/write-performance.md
+++ b/docs/content/maintenance/write-performance.md
@@ -40,7 +40,7 @@ large impact on write performance, if it is a snapshot / full synchronization ph
 then enable them again in the incremental phase.
 
 If you find that the input of the job shows a jagged pattern in the case of backpressure, it may be imbalanced work
-nodes. You can consider turning on [Asynchronous Compaction]({{< ref "#asynchronous-compaction" >}}) to observe if the
+nodes. You can consider turning on [Asynchronous Compaction]({{< ref "primary-key-table/compaction#asynchronous-compaction" >}}) to observe if the
 throughput is increased.
 
 ## Parallelism