Merge branch 'main' into Blargian-patch-399150

Author: Blargian

docs/about-us/cloud.md

@@ -1,6 +1,6 @@
 ---
 slug: /about-us/cloud
-sidebar_label: 'Cloud Service'
+sidebar_label: 'Cloud service'
 sidebar_position: 10
 description: 'ClickHouse Cloud'
 title: 'ClickHouse Cloud'

docs/about-us/history.md

@@ -1,6 +1,6 @@
 ---
 slug: /about-us/history
-sidebar_label: 'ClickHouse History'
+sidebar_label: 'ClickHouse history'
 sidebar_position: 40
 description: 'History of ClickHouse development'
 keywords: ['history','development','Metrica']

docs/about-us/index.md

@@ -12,7 +12,6 @@ the table of contents below for a list of pages in this section of the docs.
 
 | Page                                                                       | Description                                                                                                                                                                                                       |
 |----------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| [What is ClickHouse](/about-clickhouse)                                    | Introduces ClickHouse's core features, architecture, and uses, providing a concise overview for new users.                                                                                                        |
 | [Adopters](/about-us/adopters)                                             | A list of companies using ClickHouse and their success stories, assembled from public sources                                                                                                                     |
 | [Support](/about-us/support)                                               | An introduction to ClickHouse Cloud support services and their mission.                                                                                                                                           |
 | [Beta features and experimental features](/beta-and-experimental-features) | Learn about how ClickHouse uses "Beta" and "Experimental" labels to distinguish between officially supported and early-stage, unsupported features due to varied development speeds from community contributions. |

docs/about-us/intro.mdx

@@ -9,15 +9,15 @@ doc_type: 'reference'
 
 # ClickHouse Cloud support services
 
-ClickHouse provides Support Services for our ClickHouse Cloud users and customers. Our objective is a Support Services team that represents the ClickHouse product – unparalleled performance, ease of use, and exceptionally fast, high-quality results. For details, [visit our ClickHouse Support Program](https://clickhouse.com/support/program/) page.
+ClickHouse provides support services for our ClickHouse Cloud users and customers. Our objective is a support services team that represents the ClickHouse product – unparalleled performance, ease of use, and exceptionally fast, high-quality results. For details, [visit our ClickHouse Support Program](https://clickhouse.com/support/program/) page.
 
 [Login to the Cloud console](https://console.clickhouse.cloud/support) and select **Help -> Support** from the menu options to open a new support case and view the status of your submitted cases. 
 
 You can also subscribe to our [status page](https://status.clickhouse.com) to get notified quickly about any incidents affecting our platform.
 
 :::note
-Please note that only Subscription Customers have a Service Level Agreement on Support Incidents. If you are not currently a ClickHouse Cloud user – while we will try to answer your question, we'd encourage you to go instead to one of our Community resources:
+Please note that only subscription customers have a service level agreement on support incidents. If you are not currently a ClickHouse Cloud user – while we will try to answer your question, we'd encourage you to go instead to one of our community resources:
 
-- [ClickHouse Community Slack Channel](https://clickhouse.com/slack)
-- [Other Community Options](https://github.com/ClickHouse/ClickHouse/blob/master/README.md#useful-links)
+- [ClickHouse community Slack channel](https://clickhouse.com/slack)
+- [Other community options](https://github.com/ClickHouse/ClickHouse/blob/master/README.md#useful-links)
 :::

docs/about-us/support.md

@@ -1,7 +1,7 @@
 ---
 slug: /best-practices/avoid-optimize-final
 sidebar_position: 10
-sidebar_label: 'Avoid Optimize Final'
+sidebar_label: 'Avoid optimize final'
 title: 'Avoid OPTIMIZE FINAL'
 description: 'Page describing why you should avoid the OPTIMIZE FINAL clause in ClickHouse'
 keywords: ['avoid OPTIMIZE FINAL', 'background merges']

docs/best-practices/avoid_optimize_final.md

@@ -1,7 +1,7 @@
 ---
 slug: /best-practices/choosing-a-primary-key
 sidebar_position: 10
-sidebar_label: 'Choosing a Primary Key'
+sidebar_label: 'Choosing a primary key'
 title: 'Choosing a Primary Key'
 description: 'Page describing how to choose a primary key in ClickHouse'
 keywords: ['primary key']

docs/best-practices/choosing_a_primary_key.md

@@ -9,7 +9,7 @@ show_related_blogs: true
 doc_type: 'reference'
 ---
 
-ClickHouse now offers a native JSON column type designed for semi-structured and dynamic data. It's important to clarify that **this is a column type, not a data format**—you can insert JSON into ClickHouse as a string or via supported formats like [JSONEachRow](/docs/interfaces/formats/JSONEachRow), but that does not imply using the JSON column type. Users should only use the JSON type when the structure of their data is dynamic, not when they simply happen to store JSON.
+ClickHouse now offers a native JSON column type designed for semi-structured and dynamic data. It's important to clarify that **this is a column type, not a data format**—you can insert JSON into ClickHouse as a string or via supported formats like [JSONEachRow](/interfaces/formats/JSONEachRow), but that does not imply using the JSON column type. Users should only use the JSON type when the structure of their data is dynamic, not when they simply happen to store JSON.
 
 ## When to use the JSON type {#when-to-use-the-json-type}
 

docs/best-practices/json_type.md

@@ -1,7 +1,7 @@
 ---
 slug: /best-practices/minimize-optimize-joins
 sidebar_position: 10
-sidebar_label: 'Minimize and Optimize JOINs'
+sidebar_label: 'Minimize and optimize JOINs'
 title: 'Minimize and optimize JOINs'
 description: 'Page describing best practices for JOINs'
 keywords: ['JOIN', 'Parallel Hash JOIN']

docs/best-practices/minimize_optimize_joins.md

@@ -1,7 +1,7 @@
 ---
 slug: /best-practices/choosing-a-partitioning-key
 sidebar_position: 10
-sidebar_label: 'Choosing a Partitioning Key'
+sidebar_label: 'Choosing a partitioning key'
 title: 'Choosing a Partitioning Key'
 description: 'Page describing how to choose a partitioning key'
 keywords: ['partitioning key']