fix anchors

Blargian · Blargian · commit 228809d76b1d · 2025-03-01T16:05:39.000+01:00
diff --git a/docs/guides/best-practices/sparse-primary-indexes.md b/docs/guides/best-practices/sparse-primary-indexes.md
diff --git a/docs/guides/sre/keeper/index.md b/docs/guides/sre/keeper/index.md
@@ -482,7 +482,7 @@ If you have ClickHouse installed, you can use the binary directly:
 clickhouse keeper-converter ...
 ```
 
-Otherwise, you can [download the binary](/getting-started/quick-start#1-download-the-binary) and run the tool as described above without installing ClickHouse.
+Otherwise, you can [download the binary](/getting-started/quick-start#download-the-binary) and run the tool as described above without installing ClickHouse.
 :::
 
 
diff --git a/docs/guides/sre/network-ports.md b/docs/guides/sre/network-ports.md
@@ -6,7 +6,7 @@ sidebar_label: Network ports
 # Network ports
 
 :::note
-Ports described as **default** mean that the port number is configured in `/etc/clickhouse-server/config.xml`.  To customize your settings, add a file to `/etc/clickhouse-server/config.d/`.  See the [configuration file](../../operations/configuration-files.md#override) documentation.
+Ports described as **default** mean that the port number is configured in `/etc/clickhouse-server/config.xml`.  To customize your settings, add a file to `/etc/clickhouse-server/config.d/`.  See the [configuration file](/operations/configuration-files) documentation.
 :::
 
 |Port|Description|
diff --git a/docs/guides/troubleshooting.md b/docs/guides/troubleshooting.md
@@ -155,7 +155,7 @@ Check:
     - If you run ClickHouse in Docker in an IPv6 network, make sure that `network=host` is set.
 
 1. Endpoint settings.
-    - Check [listen_host](../operations/server-configuration-parameters/settings.md#server_configuration_parameters-listen_host) and [tcp_port](../operations/server-configuration-parameters/settings.md#server_configuration_parameters-tcp_port) settings.
+    - Check [listen_host](/operations/server-configuration-parameters/settings#listen_host) and [tcp_port](/operations/server-configuration-parameters/settings#tcp_port) settings.
     - ClickHouse server accepts localhost connections only by default.
 
 1. HTTP protocol settings:
@@ -165,8 +165,8 @@ Check:
 1. Secure connection settings.
 
     - Check:
-        - The [tcp_port_secure](../operations/server-configuration-parameters/settings.md#server_configuration_parameters-tcp_port_secure) setting.
-        - Settings for [SSL certificates](../operations/server-configuration-parameters/settings.md#server_configuration_parameters-openssl).
+        - The [tcp_port_secure](/operations/server-configuration-parameters/settings#tcp_port_secure) setting.
+        - Settings for [SSL certificates](/operations/server-configuration-parameters/settings#openssl).
     - Use proper parameters while connecting. For example, use the `port_secure` parameter with `clickhouse_client`.
 
 1. User settings:
diff --git a/docs/integrations/data-ingestion/clickpipes/index.md b/docs/integrations/data-ingestion/clickpipes/index.md
@@ -78,7 +78,7 @@ If ClickPipes cannot connect to a data source or destination after 15min., Click
 
 - **Does using ClickPipes incur an additional cost?**
 
-  ClickPipes is billed on two dimensions: Ingested Data and Compute. The full details of the pricing are available on [this page](/cloud/manage/jan-2025-faq/pricing-dimensions#clickpipes-pricing). Running ClickPipes might also generate an indirect compute and storage cost on the destination ClickHouse Cloud service similar to any ingest workload.
+  ClickPipes is billed on two dimensions: Ingested Data and Compute. The full details of the pricing are available on [this page](/cloud/manage/jan-2025-faq/pricing-dimensions#clickpipes-pricing-faq). Running ClickPipes might also generate an indirect compute and storage cost on the destination ClickHouse Cloud service similar to any ingest workload.
 
 - **Is there a way to handle errors or failures when using ClickPipes for Kafka?**
 
diff --git a/docs/integrations/data-ingestion/clickpipes/kafka.md b/docs/integrations/data-ingestion/clickpipes/kafka.md
@@ -127,7 +127,7 @@ The following ClickHouse data types are currently supported in ClickPipes:
 ### Avro {#avro}
 #### Supported Avro Data Types {#supported-avro-data-types}
 
-ClickPipes supports all Avro Primitive and Complex types, and all Avro Logical types except `time-millis`, `time-micros`, `local-timestamp-millis`, `local_timestamp-micros`, and `duration`.  Avro `record` types are converted to Tuple, `array` types to Array, and `map` to Map (string keys only).  In general the conversions listed [here](../../../interfaces/formats.md#data-types-matching) are available.  We recommend using exact type matching for Avro numeric types, as ClickPipes does not check for overflow or precision loss on type conversion.
+ClickPipes supports all Avro Primitive and Complex types, and all Avro Logical types except `time-millis`, `time-micros`, `local-timestamp-millis`, `local_timestamp-micros`, and `duration`.  Avro `record` types are converted to Tuple, `array` types to Array, and `map` to Map (string keys only).  In general the conversions listed [here](/interfaces/formats/Avro#data-types-matching) are available.  We recommend using exact type matching for Avro numeric types, as ClickPipes does not check for overflow or precision loss on type conversion.
 
 #### Nullable Types and Avro Unions {#nullable-types-and-avro-unions}
 
diff --git a/docs/integrations/data-ingestion/clickpipes/object-storage.md b/docs/integrations/data-ingestion/clickpipes/object-storage.md
@@ -83,9 +83,9 @@ More connectors are will get added to ClickPipes, you can find out more by [cont
 ## Supported Data Formats {#supported-data-formats}
 
 The supported formats are:
-- [JSON](../../../interfaces/formats.md/#json)
-- [CSV](../../../interfaces/formats.md/#csv)
-- [Parquet](../../../interfaces/formats.md/#parquet)
+- [JSON](/interfaces/formats/JSON)
+- [CSV](/interfaces/formats/CSV)
+- [Parquet](/interfaces/formats/Parquet)
 
 ## Exactly-Once Semantics {#exactly-once-semantics}
 
@@ -107,7 +107,7 @@ To increase the throughput on large ingest jobs, we recommend scaling the ClickH
 - There are limitations on the types of views that are supported. Please read the section on [exactly-once semantics](#exactly-once-semantics) and [view support](#view-support) for more information.
 - Role authentication is not available for S3 ClickPipes for ClickHouse Cloud instances deployed into GCP or Azure. It is only supported for AWS ClickHouse Cloud instances.
 - ClickPipes will only attempt to ingest objects at 10GB or smaller in size. If a file is greater than 10GB an error will be appended to the ClickPipes dedicated error table.
-- S3 / GCS ClickPipes **does not** share a listing syntax with the [S3 Table Function](/sql-reference/table-functions/file#globs_in_path).
+- S3 / GCS ClickPipes **does not** share a listing syntax with the [S3 Table Function](/sql-reference/table-functions/s3).
   - `?` — Substitutes any single character
   - `*` — Substitutes any number of any characters except / including empty string
   - `**` — Substitutes any number of any character include / including empty string
diff --git a/docs/integrations/data-ingestion/etl-tools/apache-beam.md b/docs/integrations/data-ingestion/etl-tools/apache-beam.md
@@ -140,7 +140,7 @@ You can adjust the `ClickHouseIO.Write` configuration with the following setter
 
 Please consider the following limitations when using the connector:
 * As of today, only Sink operation is supported. The connector doesn't support Source operation.
-* ClickHouse performs deduplication when inserting into a `ReplicatedMergeTree` or a `Distributed` table built on top of a `ReplicatedMergeTree`. Without replication, inserting into a regular MergeTree can result in duplicates if an insert fails and then successfully retries. However, each block is inserted atomically, and the block size can be configured using `ClickHouseIO.Write.withMaxInsertBlockSize(long)`. Deduplication is achieved by using checksums of the inserted blocks. For more information about deduplication, please visit [Deduplication](/guides/developer/deduplication) and [Deduplicate insertion config](/operations/settings/settings#insert-deduplicate). 
+* ClickHouse performs deduplication when inserting into a `ReplicatedMergeTree` or a `Distributed` table built on top of a `ReplicatedMergeTree`. Without replication, inserting into a regular MergeTree can result in duplicates if an insert fails and then successfully retries. However, each block is inserted atomically, and the block size can be configured using `ClickHouseIO.Write.withMaxInsertBlockSize(long)`. Deduplication is achieved by using checksums of the inserted blocks. For more information about deduplication, please visit [Deduplication](/guides/developer/deduplication) and [Deduplicate insertion config](/operations/settings/settings#insert_deduplicate). 
 * The connector doesn't perform any DDL statements; therefore, the target table must exist prior insertion.
 
 
