Merge pull request #3394 from Blargian/fix_broken_anchors_1

Fix broken anchors

Author: gingerwizard

docs/_snippets/_system_table_cloud.md

@@ -1,3 +1,3 @@
 :::note Querying in ClickHouse Cloud
-The data in this system table is held locally on each node in ClickHouse Cloud. Obtaining a complete view of all data, therefore, requires the `clusterAllReplicas` function. See [here](/operations/system-tables#system-tables-in-clickhouse-cloud) for further details.
+The data in this system table is held locally on each node in ClickHouse Cloud. Obtaining a complete view of all data, therefore, requires the `clusterAllReplicas` function. See [here](/operations/system-tables/overview#system-tables-in-clickhouse-cloud) for further details.
 :::

docs/chdb/guides/querying-parquet.md

@@ -48,7 +48,7 @@ But first, let's install `chDB`:
 import chdb
 ```
 
-When querying Parquet files, we can use the [`ParquetMetadata`](/interfaces/formats#parquetmetadata-data-format-parquet-metadata) input format to have it return Parquet metadata rather than the content of the file.
+When querying Parquet files, we can use the [`ParquetMetadata`](/interfaces/formats/ParquetMetadata) input format to have it return Parquet metadata rather than the content of the file.
 Let's use the `DESCRIBE` clause to see the fields returned when we use this format:
 
 ```python

docs/cloud/manage/cloud-tiers.md

@@ -186,7 +186,7 @@ Caters to large-scale, mission critical deployments that have stringent security
   - Single Sign On (SSO)
   - Enhanced Encryption: For AWS and GCP services. Services are encrypted by our key by default and can be rotated to their key to enable Customer Managed Encryption Keys (CMEK).
 - Allows Scheduled upgrades: Users can select the day of the week/time window for upgrades, both database and cloud releases.  
-- Offers [HIPAA](../security/compliance-overview.md/#hipaa) Compliance.
+- Offers [HIPAA](../security/compliance-overview.md/#hipaa-since-2024) Compliance.
 - Exports Backups to the user's account.
 
 :::note 

docs/cloud/manage/openapi.md

@@ -29,7 +29,7 @@ This document covers the ClickHouse Cloud API. For database API endpoints, pleas
 3. To create an API key, specify the key name, permissions for the key, and expiration time, then click `Generate API Key`.
 <br/>
 :::note
-Permissions align with ClickHouse Cloud [predefined roles](/cloud/security/cloud-access-management#predefined-roles). The developer role has read-only permissions and the admin role has full read and write permissions.
+Permissions align with ClickHouse Cloud [predefined roles](/cloud/security/cloud-access-management/overview#predefined-roles). The developer role has read-only permissions and the admin role has full read and write permissions.
 :::
 
   <img src={image_03} width="100%"/>

docs/cloud/reference/changelog.md

@@ -110,7 +110,7 @@ We are introducing a new vertical scaling mechanism for compute replicas, which
 
 ### Horizontal scaling (GA) {#horizontal-scaling-ga}
 
-Horizontal scaling is now Generally Available. Users can add additional replicas to scale out their service through the APIs and the cloud console. Please refer to the [documentation](/manage/scaling#self-serve-horizontal-scaling) for information.
+Horizontal scaling is now Generally Available. Users can add additional replicas to scale out their service through the APIs and the cloud console. Please refer to the [documentation](/manage/scaling#manual-horizontal-scaling) for information.
 
 ### Configurable backups {#configurable-backups}
 
@@ -446,7 +446,7 @@ The Fast release channel allows your services to receive updates ahead of the re
 
 ### Terraform support for horizontal scaling {#terraform-support-for-horizontal-scaling}
 
-ClickHouse Cloud supports [horizontal scaling](/manage/scaling#vertical-and-horizontal-scaling), or the ability to add additional replicas of the same size to your services. Horizontal scaling improves performance and parallelization to support concurrent queries. Previously, adding more replicas required either using the ClickHouse Cloud console or the API. You can now use Terraform to add or remove replicas from your service, allowing you to programmatically scale your ClickHouse services as needed.
+ClickHouse Cloud supports [horizontal scaling](/manage/scaling#how-scaling-works-in-clickhouse-cloud), or the ability to add additional replicas of the same size to your services. Horizontal scaling improves performance and parallelization to support concurrent queries. Previously, adding more replicas required either using the ClickHouse Cloud console or the API. You can now use Terraform to add or remove replicas from your service, allowing you to programmatically scale your ClickHouse services as needed.
 
 Please see the [ClickHouse Terraform provider](https://registry.terraform.io/providers/ClickHouse/clickhouse/latest/docs) for more information.
 

docs/cloud/security/shared-responsibility-model.md

@@ -8,7 +8,6 @@ title: Security Shared Responsibility Model
 
 ClickHouse Cloud offers three service types: Basic, Scale and Enterprise. For more information, review our [Service Types](/cloud/manage/cloud-tiers) page.
 
-
 ## Cloud architecture {#cloud-architecture}
 
 The Cloud architecture consists of the control plane and the data plane. The control plane is responsible for organization creation, user management within the control plane, service management, API key management, and billing. The data plane runs tooling for orchestration and management, and houses customer services. For more information, review our [ClickHouse Cloud Architecture](/cloud/reference/architecture) diagram.
@@ -58,9 +57,9 @@ The model below generally addresses ClickHouse responsibilities and shows respon
   | Setting                                                                                              | Status    | Cloud             | Service level           |  
   |------------------------------------------------------------------------------------------------------|-----------|-------------------|-------------------------|
   | [Standard role-based access](/cloud/security/cloud-access-management) in control plane | Available | AWS, GCP, Azure | All               | 
-  | [Multi-factor authentication (MFA)](/cloud/security/cloud-authentication#multi-factor-authhentication) available | Available | AWS, GCP, Azure | All   |
+  | [Multi-factor authentication (MFA)](/cloud/security/cloud-authentication#multi-factor-authentication) available | Available | AWS, GCP, Azure | All   |
   | [SAML Single Sign-On](/cloud/security/saml-setup) to control plane available                 | Preview   | AWS, GCP, Azure   | Enterprise              |
-  | Granular [role-based access control](/cloud/security/cloud-access-management#database-roles) in databases | Available | AWS, GCP, Azure | All          |
+  | Granular [role-based access control](/cloud/security/cloud-access-management/overview#database-roles) in databases | Available | AWS, GCP, Azure | All          |
 
 </details>
 <details>
@@ -69,8 +68,8 @@ The model below generally addresses ClickHouse responsibilities and shows respon
   | Setting                                                                                              | Status    | Cloud             | Service level           |  
   |------------------------------------------------------------------------------------------------------|-----------|-------------------|-------------------------|
   | [Cloud provider and region](/cloud/reference/supported-regions) selections                   | Available | AWS, GCP, Azure   | All                     |
-  | Limited [free daily backups](/cloud/manage/backups#default-backup-policy)                    | Available | AWS, GCP, Azure   | All                     |
-  | [Custom backup configurations](/cloud/manage/backups#configurable-backups) available         | Available | GCP, AWS, Azure   | Scale or Enterprise     |
+  | Limited [free daily backups](/cloud/manage/backups/overview#default-backup-policy)                    | Available | AWS, GCP, Azure   | All                     |
+  | [Custom backup configurations](/cloud/manage/backups/overview#configurable-backups) available         | Available | GCP, AWS, Azure   | Scale or Enterprise     |
   | [Customer managed encryption keys (CMEK)](/cloud/security/cmek) for transparent<br/> data encryption available  | Available | AWS | Scale or Enterprise |
   | [Field level encryption](/sql-reference/functions/encryption-functions) with manual key management for granular encryption | Available | GCP, AWS, Azure | All  |
 

docs/data-compression/compression-modes.md

@@ -14,7 +14,7 @@ ClickHouse protocol supports **data blocks** compression with checksums.
 Use `LZ4` if not sure what mode to pick.
 
 :::tip
-Learn more about the [column compression codecs](/sql-reference/statements/create/table.md/#column-compression-codecs) available and specify them when creating your tables, or afterward.
+Learn more about the [column compression codecs](/sql-reference/statements/create/table#column_compression_codec) available and specify them when creating your tables, or afterward.
 :::
 
 ## Modes {#modes}

docs/faq/operations/delete-old-data.md

@@ -39,13 +39,13 @@ ALTER DELETE removes rows using asynchronous batch operations. Unlike DELETE FRO
 
 This is the most common approach to make your system based on ClickHouse [GDPR](https://gdpr-info.eu)-compliant.
 
-More details on [mutations](../../sql-reference/statements/alter/index.md#alter-mutations).
+More details on [mutations](/sql-reference/statements/alter#mutations).
 
 ## DROP PARTITION {#drop-partition}
 
 `ALTER TABLE ... DROP PARTITION` provides a cost-efficient way to drop a whole partition. It’s not that flexible and needs proper partitioning scheme configured on table creation, but still covers most common cases. Like mutations need to be executed from an external system for regular use.
 
-More details on [manipulating partitions](../../sql-reference/statements/alter/partition.md#alter_drop-partition).
+More details on [manipulating partitions](/sql-reference/statements/alter/partition).
 
 ## TRUNCATE {#truncate}
 

docs/faq/use-cases/time-series.md

@@ -13,7 +13,7 @@ ClickHouse is a generic data storage solution for [OLAP](../../faq/general/olap.
 
 First of all, there are **[specialized codecs](../../sql-reference/statements/create/table.md#specialized-codecs)** which make typical time-series. Either common algorithms like `DoubleDelta` and `Gorilla` or specific to ClickHouse like `T64`.
 
-Second, time-series queries often hit only recent data, like one day or one week old. It makes sense to use servers that have both fast NVMe/SSD drives and high-capacity HDD drives. ClickHouse [TTL](/engines/table-engines/mergetree-family/mergetree.md/##table_engine-mergetree-multiple-volumes) feature allows to configure keeping fresh hot data on fast drives and gradually move it to slower drives as it ages. Rollup or removal of even older data is also possible if your requirements demand it.
+Second, time-series queries often hit only recent data, like one day or one week old. It makes sense to use servers that have both fast NVMe/SSD drives and high-capacity HDD drives. ClickHouse [TTL](/engines/table-engines/mergetree-family/mergetree#table_engine-mergetree-ttl) feature allows to configure keeping fresh hot data on fast drives and gradually move it to slower drives as it ages. Rollup or removal of even older data is also possible if your requirements demand it.
 
 Even though it’s against ClickHouse philosophy of storing and processing raw data, you can use [materialized views](../../sql-reference/statements/create/view.md) to fit into even tighter latency or costs requirements.