Update shared-catalog.md

Author: Blargian

docs/cloud/reference/shared-catalog.md

@@ -6,7 +6,7 @@ keywords: ['SharedCatalog', 'SharedDatabaseEngine']
 description: 'Describes the Shared Catalog component and the Shared database engine in ClickHouse Cloud'
 ---
 
-# Shared Catalog and Shared Database Engine
+# Shared Catalog and Shared Database Engine {#shared-catalog-and-shared-database-engine}
 
 **Available exclusively in ClickHouse Cloud (and first party partner cloud services)**
 
@@ -21,21 +21,21 @@ It supports replication of the following database engines:
 - MySQL
 - DataLakeCatalog
 
-## Architecture and Metadata Storage
+## Architecture and Metadata Storage {#architecture-and-metadata-storage}
 
 All metadata and DDL query history in Shared Catalog is stored centrally in ZooKeeper. Nothing is persisted on local disk. This architecture ensures:
 
 - Consistent state across all replicas
 - Statelessness of compute nodes
 - Fast, reliable replica bootstrapping
 
-## Shared Database Engine
+## Shared Database Engine {#shared-database-engine}
 
 The **Shared database engine** works in conjunction with Shared Catalog to manage databases whose tables use **stateless table engines** such as `SharedMergeTree`. These table engines do not write persistent state to disk and are compatible with dynamic compute environments.
 
 Shared database engine builds on and improves the behavior of the Replicated database engine while offering additional guarantees and operational benefits.
 
-### Key Benefits
+### Key benefits {#key-benefits}
 
 - **Atomic CREATE TABLE ... AS SELECT**
   Table creation and data insertion are executed atomically—either the entire operation completes, or the table is not created at all.
@@ -62,7 +62,7 @@ Shared database engine builds on and improves the behavior of the Replicated dat
 - **Centralized, versioned metadata state**
   Shared Catalog stores a single source of truth in ZooKeeper. When a replica starts, it fetches the latest state and applies the diff to reach consistency. During query execution, the system can wait for other replicas to reach at least the required version of metadata to ensure correctness.
 
-## Usage in ClickHouse Cloud
+## Usage in ClickHouse Cloud {#usage-in-clickhouse-cloud}
 
 For end users, using Shared Catalog and the Shared database engine requires no additional configuration. Database creation is the same as always:
 
@@ -72,7 +72,7 @@ CREATE DATABASE my_database;
 
 ClickHouse Cloud automatically assigns the Shared database engine to databases. Any tables created within such a database using stateless engines will automatically benefit from Shared Catalog’s replication and coordination capabilities.
 
-## Summary
+## Summary {#summary}
 
 Shared Catalog and the Shared database engine provide: