Merge main branch into add_laion5b branch to fix spell check issue unrelated to this PR

Author: Blargian

docs/cloud/manage/billing/marketplace/azure-marketplace-payg.md

@@ -114,9 +114,9 @@ You will receive an email like the one below with details on configuring your ac
 
 <br />
 
-12. You will be redirected to the ClickHouse Cloud sign up or sign in page. You can either sign up using a new account or sign in using an existing account. Once you are signed in, a new organization will be created that is ready to be used and billed via the Azure Marketplace.
+12. You will be redirected to the ClickHouse Cloud sign up or sign in page. Once you redirect to ClickHouse Cloud, you can either login with an existing account, or register with a new account. This step is very important so we can bind your ClickHouse Cloud organization to the Azure Marketplace billing.
 
-13. You will need to answer a few questions - address and company details - before you can proceed.
+13. Note that if you are a new user, you will also need to provide some basic information about your business. See the screenshots below.
 
 <br />
 
@@ -128,7 +128,7 @@ You will receive an email like the one below with details on configuring your ac
 
 <br />
 
-14. Once you hit **Complete sign up**, you will be taken to your organization within ClickHouse Cloud where you can view the billing screen to ensure you are being billed via the Azure Marketplace and can create services.
+Once you hit **Complete sign up**, you will be taken to your organization within ClickHouse Cloud where you can view the billing screen to ensure you are being billed via the Azure Marketplace and can create services.
 
 <br />
 
@@ -144,4 +144,4 @@ You will receive an email like the one below with details on configuring your ac
 
 <br />
 
-15. If you run into any issues, please do not hesitate to contact [our support team](https://clickhouse.com/support/program).
+14. If you run into any issues, please do not hesitate to contact [our support team](https://clickhouse.com/support/program).

docs/cloud/security/cmek.md

@@ -19,7 +19,7 @@ Enhanced encryption is currently available in AWS and GCP services. Azure is com
 
 ## Transparent Data Encryption (TDE) {#transparent-data-encryption-tde}
 
-TDE must be enabled on service creation. Existing services cannot be encrypted after creation.
+TDE must be enabled on service creation. Existing services cannot be encrypted after creation. Once TDE is enabled, it cannot be disabled. All data in the service will remain encrypted. If you want to disable TDE after it has been enabled, you must create a new service and migrate your data there.
 
 1. Select `Create new service`
 2. Name the service

docs/guides/examples/aggregate_function_combinators/sumForEach.md

@@ -1,12 +1,12 @@
 ---
 slug: '/examples/aggregate-function-combinators/sumForEach'
 title: 'sumForEach'
-description: 'Example of using the sumArray combinator'
-keywords: ['sum', 'array', 'combinator', 'examples', 'sumArray']
-sidebar_label: 'sumArray'
+description: 'Example of using the sumForEach aggregate function'
+keywords: ['sum', 'ForEach', 'combinator', 'examples', 'sumForEach']
+sidebar_label: 'sumForEach'
 ---
 
-# sumArray {#sumforeach}
+# sumForEach {#sumforeach}
 
 ## Description {#description}
 
@@ -45,4 +45,4 @@ ORDER BY hour_of_day;
 
 ## See also {#see-also}
 - [`sum`](/sql-reference/aggregate-functions/reference/sum)
-- [`ForEach combinator`](/sql-reference/aggregate-functions/combinators#-foreach)
+- [`ForEach` combinator](/sql-reference/aggregate-functions/combinators#-foreach)

docs/integrations/data-ingestion/apache-spark/spark-native-connector.md

@@ -137,7 +137,7 @@ If you want to avoid copying the JAR files to your Spark client node, you can us
 
 ```text
   --repositories https://{maven-central-mirror or private-nexus-repo} \
-  --packages com.clickhouse.spark:clickhouse-spark-runtime-{{ spark_binary_version }}_{{ scala_binary_version }}:{{ stable_version }},com.clickhouse:clickhouse-jdbc:{{ clickhouse_jdbc_version }}:all
+  --packages com.clickhouse.spark:clickhouse-spark-runtime-{{ spark_binary_version }}_{{ scala_binary_version }}:{{ stable_version }},com.clickhouse:clickhouse-jdbc:{{ clickhouse_jdbc_version }}
 ```
 
 Note: For SQL-only use cases, [Apache Kyuubi](https://github.com/apache/kyuubi) is recommended
@@ -476,7 +476,7 @@ ClickHouse.
 Spark SQL allows you to write queries exactly as you would in ClickHouse,
 so you can directly execute commands such as CREATE TABLE, TRUNCATE, and more - without modification, for instance:
 
-note:::
+:::note
 When using Spark SQL, only one statement can be executed at a time.
 :::
 

docs/integrations/index.mdx

@@ -246,6 +246,8 @@ We are actively compiling this list of ClickHouse integrations below, so it's no
 |Redis|<Redissvg alt="Redis logo" style={{width: '3rem', 'height': '3rem'}}/>|Data ingestion|Allows ClickHouse to use [Redis](https://redis.io/) as a dictionary source.|[Documentation](/sql-reference/dictionaries/index.md#redis)|
 |Redpanda|<Image img={redpanda} alt="Redpanda logo" size="logo"/>|Data ingestion|Redpanda is the streaming data platform for developers. It's API-compatible with Apache Kafka, but 10x faster, much easier to use, and more cost effective|[Blog](https://redpanda.com/blog/real-time-olap-database-clickhouse-redpanda)|
 |REST Catalog||Data ingestion|Integration with REST Catalog specification for Iceberg tables, supporting multiple catalog providers including Tabular.io.|[Documentation](/use-cases/data-lake/rest-catalog)|
+|Lakekeeper||Data ingestion|Integration with Lakekeeper, an open-source REST catalog implementation for Apache Iceberg with multi-tenant support.|[Documentation](/use-cases/data-lake/lakekeeper-catalog)|
+|Nessie||Data ingestion|Integration with Nessie, an open-source transactional catalog for data lakes with Git-like data version control.|[Documentation](/use-cases/data-lake/nessie-catalog)|
 |Rust|<Image img={rust} size="logo" alt="Rust logo"/>|Language client|A typed client for ClickHouse|[Documentation](/integrations/language-clients/rust.md)|
 |SQLite|<Sqlitesvg alt="Sqlite logo" style={{width: '3rem', 'height': '3rem'}}/>|Data ingestion|Allows to import and export data to SQLite and supports queries to SQLite tables directly from ClickHouse.|[Documentation](/engines/table-engines/integrations/sqlite)|
 |Superset|<Supersetsvg alt="Superset logo" style={{width: '3rem'}}/>|Data visualization|Explore and visualize your ClickHouse data with Apache Superset.|[Documentation](/integrations/data-visualization/superset-and-clickhouse.md)|

docs/use-cases/data_lake/index.md

@@ -14,3 +14,5 @@ ClickHouse supports integration with multiple catalogs (Unity, Glue, REST, Polar
 | [Querying data in S3 using ClickHouse and the Glue Data Catalog](/use-cases/data-lake/glue-catalog) |  Query your data in S3 buckets using ClickHouse and the Glue Data Catalog. |
 | [Querying data in S3 using ClickHouse and the Unity Data Catalog](/use-cases/data-lake/unity-catalog) | Query your using the Unity Catalog. |
 | [Querying data in S3 using ClickHouse and the REST Catalog](/use-cases/data-lake/rest-catalog) | Query your data using the REST Catalog (Tabular.io). |
+| [Querying data in S3 using ClickHouse and the Lakekeeper Catalog](/use-cases/data-lake/lakekeeper-catalog) | Query your data using the Lakekeeper Catalog. |
+| [Querying data in S3 using ClickHouse and the Nessie Catalog](/use-cases/data-lake/nessie-catalog) | Query your data using the Nessie Catalog with Git-like data version control. |