From e72c06ce489e54272f02dbaa555a5c31d7c36c40 Mon Sep 17 00:00:00 2001
From: Steven <54518670+yangjf2019@users.noreply.github.com>
Date: Sun, 1 Dec 2024 19:40:14 +0800
Subject: [PATCH] [doc] fix url links in documentation (#4610)

---
 docs/content/concepts/table-types.md       | 2 +-
 docs/content/engines/doris.md              | 4 ++--
 docs/content/engines/starrocks.md          | 2 +-
 docs/content/primary-key-table/overview.md | 2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/docs/content/concepts/table-types.md b/docs/content/concepts/table-types.md
index 58199031b6e7..b5a1fafa3da1 100644
--- a/docs/content/concepts/table-types.md
+++ b/docs/content/concepts/table-types.md
@@ -33,7 +33,7 @@ Paimon supports table types:
 3. view: metastore required, views in SQL are a kind of virtual table
 4. format-table: file format table refers to a directory that contains multiple files of the same format, where
    operations on this table allow for reading or writing to these files, compatible with Hive tables
-5. object table: provides metadata indexes for unstructured data objects in the specified Object Storage storage directory.
+5. object table: provides metadata indexes for unstructured data objects in the specified Object Storage directory.
 6. materialized-table: aimed at simplifying both batch and stream data pipelines, providing a consistent development
    experience, see [Flink Materialized Table](https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/materialized-table/overview/)
 
diff --git a/docs/content/engines/doris.md b/docs/content/engines/doris.md
index cd778cd57797..6d22bc376a88 100644
--- a/docs/content/engines/doris.md
+++ b/docs/content/engines/doris.md
@@ -89,11 +89,11 @@ See [Apache Doris Website](https://doris.apache.org/docs/lakehouse/datalake-anal
 
 - Read optimized for Primary Key Table
 
-    Doris can utilize the [Read optimized](https://paimon.apache.org/releases/release-0.6/#read-optimized) feature for Primary Key Table(release in Paimon 0.6), by reading base data files using native Parquet/ORC reader and delta file using JNI.
+    Doris can utilize the [Read optimized](https://paimon.apache.org/docs/0.8/primary-key-table/read-optimized/) feature for Primary Key Table(release in Paimon 0.6), by reading base data files using native Parquet/ORC reader and delta file using JNI.
 
 - Deletion Vectors
 
-    Doris(2.1.4+) natively supports [Deletion Vectors](https://paimon.apache.org/releases/release-0.8/#deletion-vectors)(released in Paimon 0.8).
+    Doris(2.1.4+) natively supports [Deletion Vectors](https://paimon.apache.org/docs/0.8/primary-key-table/deletion-vectors/)(released in Paimon 0.8).
 
 ## Doris to Paimon type mapping
 
diff --git a/docs/content/engines/starrocks.md b/docs/content/engines/starrocks.md
index 1ab821a9a103..dda22d35f76a 100644
--- a/docs/content/engines/starrocks.md
+++ b/docs/content/engines/starrocks.md
@@ -81,7 +81,7 @@ SELECT * FROM paimon_catalog.test_db.partition_tbl$partitions;
 ## StarRocks to Paimon type mapping
 
 This section lists all supported type conversion between StarRocks and Paimon. 
-All StarRocks’s data types can be found in this doc [StarRocks Data type overview](https://docs.starrocks.io/docs/sql-reference/data-types/data-type-list/).
+All StarRocks’s data types can be found in this doc [StarRocks Data type overview](https://docs.starrocks.io/docs/sql-reference/data-types/).
 
 <table class="table table-bordered">
     <thead>
diff --git a/docs/content/primary-key-table/overview.md b/docs/content/primary-key-table/overview.md
index 508b990abc59..552d60eff6de 100644
--- a/docs/content/primary-key-table/overview.md
+++ b/docs/content/primary-key-table/overview.md
@@ -56,6 +56,6 @@ Records within a data file are sorted by their primary keys. Within a sorted run
 
 {{< img src="/img/sorted-runs.png">}}
 
-As you can see, different sorted runs may have overlapping primary key ranges, and may even contain the same primary key. When querying the LSM tree, all sorted runs must be combined and all records with the same primary key must be merged according to the user-specified [merge engine]({{< ref "primary-key-table/merge-engine" >}}) and the timestamp of each record.
+As you can see, different sorted runs may have overlapping primary key ranges, and may even contain the same primary key. When querying the LSM tree, all sorted runs must be combined and all records with the same primary key must be merged according to the user-specified [merge engine]({{< ref "primary-key-table/merge-engine/overview" >}}) and the timestamp of each record.
 
 New records written into the LSM tree will be first buffered in memory. When the memory buffer is full, all records in memory will be sorted and flushed to disk. A new sorted run is now created.