Merge pull request #2831 from ClickHouse/fix-asynchronous-inserts-broken-link

Fix asynchronous insert page broken link

Author: SpencerTorres

docs/en/cloud/bestpractices/asyncinserts.md

@@ -56,5 +56,5 @@ Asynchronous inserts can be enabled for a particular user, or for a specific que
 Our strong recommendation is to use async_insert=1,wait_for_async_insert=1 if using asynchronous inserts. Using wait_for_async_insert=0 is very risky because your INSERT client may not be aware if there are errors, and also can cause potential overload if your client continues to write quickly in a situation where the ClickHouse server needs to slow down the writes and create some backpressure in order to ensure reliability of the service.
 
 :::note Automatic deduplication is disabled by default when using asynchronous inserts
-Manual batching (see [section above](#ingest-data-in-bulk))) has the advantage that it supports the [built-in automatic deduplication](/docs/en/engines/table-engines/mergetree-family/replication.md) of table data if (exactly) the same insert statement is sent multiple times to ClickHouse Cloud, for example, because of an automatic retry in client software because of some temporary network connection issues.
+Manual batching (see [bulk insert](/docs/en/cloud/bestpractices/bulkinserts.md))) has the advantage that it supports the [built-in automatic deduplication](/docs/en/engines/table-engines/mergetree-family/replication.md) of table data if (exactly) the same insert statement is sent multiple times to ClickHouse Cloud, for example, because of an automatic retry in client software because of some temporary network connection issues.
 :::