Ensure headers are in sentence case except for product names

contribute/CODE_OF_CONDUCT.md

@@ -1,4 +1,4 @@
-# ClickHouse Community Code of Conduct
+# ClickHouse community code of conduct
 This code of conduct governs ClickHouse Community discussions, channels, and events.
 
 ## Introduction {#introduction}
@@ -7,13 +7,13 @@ This code of conduct governs ClickHouse Community discussions, channels, and eve
 * Our goal is to maintain a safe and friendly community for everyone, regardless of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other defining characteristic.
 * This code and related procedures apply to unacceptable behavior occurring in all community venues, including behavior outside the scope of community activities — online and in-person — as well as in all one-on-one communications, and anywhere such behavior has the potential to adversely affect the safety and well-being of community members.
 
-## Expected Behavior {#expected-behavior}
+## Expected behavior {#expected-behavior}
 * Be welcoming.
 * Be kind and patient.
 * Look out for each other.
 * Be careful and aware of your wording and tone.
 
-## Unacceptable Behavior {#unacceptable-behavior}
+## Unacceptable behavior {#unacceptable-behavior}
 * Conduct or speech which might be considered sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory or offensive in nature.
     * Do not use unwelcome, suggestive, derogatory or inappropriate nicknames or terms.
     * Do not show disrespect towards others. (Jokes, innuendo, dismissive attitudes.)

contribute/contrib-writing-guide.md

@@ -31,7 +31,7 @@ Our build process is a little different because part of our docs are in the [Cli
 The documentation is built with Docusaurus, which requires Node.js. We recommend version 18. Install [Node.js](https://nodejs.org/en/download/).
 
 
-### Installing npm and yarn {#installing-npm-and-yarn}
+### Installing NPM and yarn {#installing-npm-and-yarn}
 
 We use [yarn classic](https://classic.yarnpkg.com/lang/en/) to build the ClickHouse docs.
 
@@ -146,12 +146,12 @@ We have seen more and more 404s as the size of the docs grow.
 It seems that these are related to the use of `../` in the path to the markdown files.  Please write links to other doc
 pages as:
 
-#### link to another doc {#link-to-another-doc}
+#### Link to another doc {#link-to-another-doc}
 ```md title="foo"
 [async_insert](/operations/settings/settings.md)
 ```
 
-#### link to an anchor within another doc {#link-to-an-anchor-within-another-doc}
+#### Link to an anchor within another doc {#link-to-an-anchor-within-another-doc}
 
 ```md
 [async_insert](/operations/settings/settings.md/#async-insert)
@@ -252,7 +252,7 @@ Some docs contain information for both Cloud and Self-managed ClickHouse, and so
 
 Note: in the examples below you may notice that the H1 and H2 headers are outside of the tabs, the right-side "What's on this page" nav is built from the H1,2,3 headers in the main body of the markdown file, headings within the tabs are not currently included.
 
-### Differences between Cloud and Self-managed {#differences-between-cloud-and-self-managed}
+### Differences between cloud and Self-managed {#differences-between-cloud-and-self-managed}
 
 Backup and restore are very different across Cloud and Self-managed as the target for the backup does not need to be specified, etc.  The backup docs are an example where there is no content reused, so everything goes into one tab or the other. This is how the tabs are constructed:
 

contribute/style-guide.md

@@ -20,9 +20,9 @@ doc_type: 'reference' (or 'guide' or 'changelog')
 ---
 ```
 
-### Associated markdown rule or CI check
+### Associated Markdown rule or ci check
 
-#### front-matter validation 
+#### Front-matter validation
 
 There is a custom Docusaurus plugin which runs on build that makes the following
 checks on front-matter:
@@ -46,7 +46,7 @@ For example:
 ## My header {#my-header}
 ```
 
-### Associated markdown rule or CI check
+### Associated Markdown rule or ci check
 - [`custom-anchor-headings`](/scripts/.markdownlint-cli2.yaml)
 
 ## Images
@@ -214,7 +214,7 @@ Processed 335.87 thousand rows,
 13.54 MB (12.91 million rows/s., 520.38 MB/s.)
 ```
 
-### Associated markdown rule or CI check
+### Associated Markdown rule or ci check
 
 - [`MD040` enforces that codeblocks have a language specified](/scripts/.markdownlint-cli2.yaml)
 
@@ -249,7 +249,7 @@ imported by that page. Find the snippet location from the import statement at th
 Docusaurus also has a built-in broken anchor checker. Unfortunately it sometimes
 can give false positives.
 
-### linking to spans
+### Linking to spans
 
 Sometimes you want to link to something other than a header. It is logical to 
 use a span for this purpose. For instance if you want to link to an image.
@@ -335,7 +335,7 @@ which may need versioned documentation, we use the following custom
 
 The `ClientVersionDropdown` component supports two APIs:
 
-#### API 1: Inline Content (Recommended)
+#### API 1: inline content (recommended)
 
 This approach keeps all content in the main file, which allows Docusaurus to properly generate the table of contents (TOC) for all versions.
 
@@ -375,7 +375,7 @@ Your v0.7.x content here...
 - The TOC will show only headers from the currently selected version
 - The component will display the first version as 'selected' by default
 
-#### API 2: External Snippets (Legacy)
+#### API 2: external snippets (legacy)
 
 This approach uses separate snippet files for each version. Note that this method has limitations with TOC generation.
 
@@ -458,7 +458,7 @@ in your component configuration. For example:
 - URL: `docs/api?v=v08`
 - Matches: `version: 'v0.8+'` in your dropdown configuration
 
-#### Conventions That Work
+#### Conventions that work
 
 - **Simple Version Strings**: Parameters like `?v=v08`, `?v=v07` work by 
 - matching against stripped versions of your configured version names.
@@ -471,7 +471,7 @@ in your component configuration. For example:
 - **Preserving Other Parameters**: Other URL parameters are preserved when 
 switching versions.
 
-#### What Won't Work
+#### What won't work
 
 - **Partial Matches**: `?v=8` won't match `v0.8` with the default implementation.
 
@@ -481,7 +481,7 @@ require more sophisticated matching logic. (Reach out to the docs team if requir
 - **Non-Standard Formats**: Version formats not accounted for in the matching 
 logic might fail.
 
-#### Best Practices
+#### Best practices
 
 1. Keep version strings in consistent formats for predictable results.
 

docs/_snippets/_GCS_authentication_and_bucket.md

@@ -11,17 +11,17 @@ import Image from '@theme/IdealImage';
 <details>
     <summary>Create GCS buckets and an HMAC key</summary>
 
-### ch_bucket_us_east1 {#ch_bucket_us_east1}
+### Ch_bucket_us_east1 {#ch_bucket_us_east1}
 
 <Image size="md" img={GCS_bucket_1} alt="Creating a GCS bucket in US East 1" border />
 
-### ch_bucket_us_east4 {#ch_bucket_us_east4}
+### Ch_bucket_us_east4 {#ch_bucket_us_east4}
 
 <Image size="md" img={GCS_bucket_2} alt="Creating a GCS bucket in US East 4" border />
 
 ### Generate an access key {#generate-an-access-key}
 
-### Create a service account HMAC key and secret {#create-a-service-account-hmac-key-and-secret}
+### Create a service account hmac key and secret {#create-a-service-account-hmac-key-and-secret}
 
 Open **Cloud Storage > Settings > Interoperability** and either choose an existing **Access key**, or **CREATE A KEY FOR A SERVICE ACCOUNT**.  This guide covers the path for creating a new key for a new service account.
 

docs/_snippets/_S3_authentication_and_bucket.md

@@ -22,7 +22,7 @@ import s3_h from '@site/static/images/_snippets/s3/s3-h.png';
 
 This article demonstrates the basics of how to configure an AWS IAM user, create an S3 bucket and configure ClickHouse to use the bucket as an S3 disk. You should work with your security team to determine the permissions to be used, and consider these as a starting point.
 
-### Create an AWS IAM user {#create-an-aws-iam-user}
+### Create an AWS iam user {#create-an-aws-iam-user}
 In this procedure, we'll be creating a service account user, not a login user.
 1.  Log into the AWS IAM Management Console.
 

docs/_snippets/_direct_observability_integration_options.md

@@ -7,7 +7,7 @@ import NativeAdvancedDashboard from '@site/static/images/cloud/manage/monitoring
 The ClickHouse data source plugin for Grafana enables visualization and exploration of data directly from ClickHouse using system tables. This approach works well for monitoring performance and creating custom dashboards for detailed system analysis.
 For plugin installation and configuration details, see the ClickHouse [data source plugin](/integrations/grafana). For a complete monitoring setup using the Prometheus-Grafana mix-in with pre-built dashboards and alerting rules, see [Monitor ClickHouse with the new Prometheus-Grafana mix-in](https://clickhouse.com/blog/monitor-with-new-prometheus-grafana-mix-in).
 
-### Direct Datadog Integration {#direct-datadog}
+### Direct Datadog integration {#direct-datadog}
 
 Datadog offers a Clickhouse Monitoring plugin for its agent which queries system tables directly. This integration provides comprehensive database monitoring with cluster awareness through clusterAllReplicas functionality. 
 :::note

docs/_snippets/_observability_integration_options.md

@@ -7,7 +7,7 @@ import NativeAdvancedDashboard from '@site/static/images/cloud/manage/monitoring
 External integration allows organizations to maintain established monitoring workflows, leverage existing team expertise with familiar tools, and integrate ClickHouse monitoring with broader infrastructure observability without disrupting current processes or requiring significant retraining investments.
 Teams can apply existing alerting rules and escalation procedures to ClickHouse metrics, while correlating database performance with application and infrastructure health within a unified observability platform. This approach maximizes ROI on current monitoring setups and enables faster troubleshooting through consolidated dashboards and familiar tooling interfaces.
 
-### Grafana Cloud monitoring {#grafana}
+### Grafana cloud monitoring {#grafana}
 
 Grafana provides ClickHouse monitoring through both direct plugin integration and Prometheus-based approaches. The Prometheus endpoint integration maintains operational separation between monitoring and production workloads while enabling visualization within existing Grafana Cloud infrastructure. See [Grafana's ClickHouse documentation](https://grafana.com/docs/grafana-cloud/monitor-infrastructure/integrations/integration-reference/integration-clickhouse/) for configuration guidance.
 

docs/_snippets/_users-and-roles-common.md

@@ -183,7 +183,7 @@ Roles are used to define groups of users for certain privileges instead of manag
 
 <VerticalStepper headerLevel="h5">
 
-##### Log into the clickhouse client using the `clickhouse_admin` user {#login-admin-user}
+##### Log into the ClickHouse client using the `clickhouse_admin` user {#login-admin-user}
 
    ```bash
    clickhouse-client --user clickhouse_admin --password password

docs/about-us/cloud.md

@@ -8,12 +8,12 @@ keywords: ['ClickHouse Cloud', 'cloud database', 'managed ClickHouse', 'serverle
 doc_type: 'reference'
 ---
 
-# ClickHouse Cloud
+# ClickHouse cloud
 
 ClickHouse Cloud is the cloud offering created by the original creators of the popular open-source OLAP database ClickHouse. 
 You can experience ClickHouse Cloud by [starting a free trial](https://console.clickhouse.cloud/signUp).
 
-## ClickHouse Cloud benefits {#clickhouse-cloud-benefits}
+## ClickHouse cloud benefits {#clickhouse-cloud-benefits}
 
 Some of the benefits of using ClickHouse Cloud are described below:
 
@@ -25,7 +25,7 @@ Some of the benefits of using ClickHouse Cloud are described below:
 - **Broad ecosystem**: Bring your favorite data connectors, visualization tools, SQL and language clients with you.
 
 <!--
-## OSS vs ClickHouse Cloud comparison {#oss-vs-clickhouse-cloud}
+## OSS vs ClickHouse cloud comparison {#oss-vs-clickhouse-cloud}
 
 | Feature                        | Benefits                                                                                                                                                                                                                                                                                                   | OSS ClickHouse  | ClickHouse Cloud  |
 |--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------|-------------------|
@@ -45,7 +45,7 @@ Some of the benefits of using ClickHouse Cloud are described below:
 | **Managed services**           | With a cloud-managed service, teams can focus on business outcomes and accelerate time-to-market without having to worry about the operational overhead of sizing, setup, and maintenance of ClickHouse.                                                                                                   | ❌               | ✅                 |
 -->
 
-## What version of ClickHouse does ClickHouse Cloud use? {#what-version-of-clickhouse-does-clickhouse-cloud-use}
+## What version of ClickHouse does ClickHouse cloud use? {#what-version-of-clickhouse-does-clickhouse-cloud-use}
 
 Clickhouse Cloud continuously upgrades your service to a newer version. After publishing a core database version in the open source, we do additional validation in our cloud staging environment, which typically takes 6-8 weeks before rolling out to production. The rollout is phased out by cloud service provider, service type, and region.
 

docs/about-us/distinctive-features.md

@@ -88,7 +88,7 @@ ClickHouse uses asynchronous multi-master replication. After being written to an
 
 For more information, see the section [Data replication](../engines/table-engines/mergetree-family/replication.md).
 
-## Role-Based Access Control {#role-based-access-control}
+## Role-based access control {#role-based-access-control}
 
 ClickHouse implements user account management using SQL queries and allows for [role-based access control configuration](/guides/sre/user-management/index.md) similar to what can be found in the ANSI SQL standard and popular relational database management systems.
 

docs/about-us/support.md

@@ -8,7 +8,7 @@ doc_type: 'reference'
 keywords: ['support', 'help', 'customer service', 'technical support', 'service level agreement']
 ---
 
-# ClickHouse Cloud support services
+# 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.
 

docs/best-practices/index.md

@@ -9,7 +9,7 @@ doc_type: 'landing-page'
 
 import TableOfContents from '@site/docs/best-practices/_snippets/_table_of_contents.md';
 
-# Best Practices in ClickHouse {#best-practices-in-clickhouse}
+# Best practices in ClickHouse {#best-practices-in-clickhouse}
 
 This section provides the best practices you will want to follow to get the most out of ClickHouse.
 

docs/best-practices/minimize_optimize_joins.md

@@ -25,7 +25,7 @@ Not all data needs to be denormalized — focus on the attributes that are frequ
 
 For a full guide on denormalizing data in ClickHouse see [here](/data-modeling/denormalization).
 
-## When JOINs are required {#when-joins-are-required}
+## When joins are required {#when-joins-are-required}
 
 When JOINs are required, ensure you're using **at least version 24.12 and preferably the latest version**, as JOIN performance continues to improve with each new release. As of ClickHouse 24.12, the query planner now automatically places the smaller table on the right side of the join for optimal performance — a task that previously had to be done manually. Even more enhancements are coming soon, including more aggressive filter pushdown and automatic re-ordering of multiple joins.
 
@@ -42,7 +42,7 @@ Follow these best practices to improve JOIN performance:
 When using dictionaries for JOINs in ClickHouse, it's important to understand that dictionaries, by design, do not allow duplicate keys. During data loading, any duplicate keys are silently deduplicated—only the last loaded value for a given key is retained. This behavior makes dictionaries ideal for one-to-one or many-to-one relationships where only the latest or authoritative value is needed. However, using a dictionary for a one-to-many or many-to-many relationship (e.g. joining roles to actors where an actor can have multiple roles) will result in silent data loss, as all but one of the matching rows will be discarded. As a result, dictionaries are not suitable for scenarios requiring full relational fidelity across multiple matches.
 :::
 
-## Choosing the correct JOIN Algorithm {#choosing-the-right-join-algorithm}
+## Choosing the correct join algorithm {#choosing-the-right-join-algorithm}
 
 ClickHouse supports several JOIN algorithms that trade off between speed and memory:
 

docs/best-practices/selecting_an_insert_strategy.md

@@ -91,7 +91,7 @@ Compressing insert data reduces the size of the payload sent over the network, m
 
 For inserts, compression is especially effective when used with the Native format, which already matches ClickHouse's internal columnar storage model. In this setup, the server can efficiently decompress and directly store the data with minimal transformation.
 
-#### Use LZ4 for speed, ZSTD for compression ratio {#use-lz4-for-speed-zstd-for-compression-ratio}
+#### Use lz4 for speed, zstd for compression ratio {#use-lz4-for-speed-zstd-for-compression-ratio}
 
 ClickHouse supports several compression codecs during data transmission. Two common options are:
 

docs/best-practices/sizing-and-hardware-recommendations.md

@@ -37,7 +37,7 @@
 
 ## CPU {#cpu}
 
-### Which CPU should I use? {#which-cpu-should-i-use}
+### Which CPU should i use? {#which-cpu-should-i-use}
 
 The type of CPU you should use depends on your usage pattern. In general, however, applications with many frequent concurrent queries, that process more data, or that use compute-intensive UDFs will require more CPU cores.
 
@@ -59,7 +59,7 @@
 
 There is no standard CPU utilization target for ClickHouse. Utilize a tool such as [iostat](https://linux.die.net/man/1/iostat) to measure average CPU usage, and accordingly adjust the size of your servers to manage unexpected traffic spikes. However, for analytical or data warehousing use cases with ad-hoc queries, you should target 10-20% CPU utilization.
 
-### How many CPU cores should I use? {#how-many-cpu-cores-should-i-use}
+### How many CPU cores should i use? {#how-many-cpu-cores-should-i-use}
 
 The number of CPUs you should use depends on your workload. However, we generally recommend the following memory-to-CPU-core ratios based on your CPU type:
 
@@ -102,7 +102,7 @@
 
 To provide guidance (not recommendations), the following are example configurations of ClickHouse users in production:
 
-### Fortune 500 B2B SaaS {#fortune-500-b2b-saas}
+### Fortune 500 b2b saas {#fortune-500-b2b-saas}
 
 <table>
     <tr>
@@ -164,7 +164,7 @@
     </tr>
 </table>
 
-### Fortune 500 Telecom Operator for a logging use case {#fortune-500-telecom-operator-for-a-logging-use-case}
+### Fortune 500 telecom operator for a logging use case {#fortune-500-telecom-operator-for-a-logging-use-case}
 
 <table>
     <tr>

docs/best-practices/use_materialized_views.md

@@ -59,7 +59,7 @@ In summary, use refreshable materialized views when:
 
 For examples of refreshable materialized views see [here](/materialized-view/refreshable-materialized-view).
 
-### APPEND vs REPLACE mode {#append-vs-replace-mode}
+### Append vs replace mode {#append-vs-replace-mode}
 
 Refreshable materialized views support two modes for writing data to the target table: `APPEND` and `REPLACE`. These modes define how the result of the view's query is written when the view is refreshed.