use claude to fix more heading style violations

Author: Blargian

docs/deployment-guides/horizontal-scaling.md

@@ -19,7 +19,7 @@ This example architecture is designed to provide scalability.  It includes three
 <ReplicationShardingTerminology />
 
 ## Environment {#environment}
-### Architecture Diagram {#architecture-diagram}
+### Architecture diagram {#architecture-diagram}
 
 <Image img={scalingOut1} size='md' alt='Architecture diagram for 2 shards and 1 replica' />
 
@@ -41,7 +41,7 @@ Install Clickhouse on three servers following the [instructions for your archive
 
 <ConfigFileNote />
 
-## chnode1 configuration {#chnode1-configuration}
+## Chnode1 configuration {#chnode1-configuration}
 
 For `chnode1`, there are five configuration files.  You may choose to combine these files into a single file, but for clarity in the documentation it may be simpler to look at them separately.  As you read through the configuration files, you will see that most of the configuration is the same between `chnode1` and `chnode2`; the differences will be highlighted.
 
@@ -183,7 +183,7 @@ Up above a few files ClickHouse Keeper was configured.  This configuration file
 </clickhouse>
 ```
 
-## chnode2 configuration {#chnode2-configuration}
+## Chnode2 configuration {#chnode2-configuration}
 
 As the configuration is very similar on `chnode1` and `chnode2`, only the differences will be pointed out here.
 
@@ -309,7 +309,7 @@ The macros configuration has one of the differences between `chnode1` and `chnod
 </clickhouse>
 ```
 
-## chnode3 configuration {#chnode3-configuration}
+## Chnode3 configuration {#chnode3-configuration}
 
 As `chnode3` is not storing data and is only used for ClickHouse Keeper to provide the third node in the quorum, `chnode3` has only two configuration files, one to configure the network and logging, and one to configure ClickHouse Keeper.
 
@@ -481,7 +481,7 @@ SELECT * FROM db1.table1_dist;
 ```
 
 
-## More information about: {#more-information-about}
+## More information about {#more-information-about}
 
 - The [Distributed Table Engine](/engines/table-engines/special/distributed.md)
 - [ClickHouse Keeper](/guides/sre/keeper/index.md)

docs/deployment-guides/index.md

@@ -4,7 +4,7 @@ title: 'Deployment Guides Overview'
 description: 'Landing page for the deployment and scaling section'
 ---
 
-# Deployment and Scaling
+# Deployment and scaling
 
 This section covers the following topics:
 

docs/deployment-guides/replicated.md

@@ -20,7 +20,7 @@ In this architecture, there are five servers configured. Two are used to host co
 <ReplicationShardingTerminology />
 
 ## Environment {#environment}
-### Architecture Diagram {#architecture-diagram}
+### Architecture diagram {#architecture-diagram}
 
 <Image img={ReplicationArchitecture} size="md" alt="Architecture diagram for 1 shard and 2 replicas with ReplicatedMergeTree" />
 
@@ -46,7 +46,7 @@ Install ClickHouse Keeper on the three servers `clickhouse-keeper-01`, `clickhou
 
 <ConfigFileNote />
 
-## clickhouse-01 configuration {#clickhouse-01-configuration}
+## Clickhouse-01 configuration {#clickhouse-01-configuration}
 
 For clickhouse-01 there are five configuration files.  You may choose to combine these files into a single file, but for clarity in the documentation it may be simpler to look at them separately.  As you read through the configuration files you will see that most of the configuration is the same between clickhouse-01 and clickhouse-02; the differences will be highlighted.
 
@@ -143,7 +143,7 @@ This configuration file `use-keeper.xml` is configuring ClickHouse Server to use
 </clickhouse>
 ```
 
-## clickhouse-02 configuration {#clickhouse-02-configuration}
+## Clickhouse-02 configuration {#clickhouse-02-configuration}
 
 As the configuration is very similar on clickhouse-01 and clickhouse-02 only the differences will be pointed out here.
 
@@ -232,7 +232,7 @@ This file is the same on both clickhouse-01 and clickhouse-02.
 </clickhouse>
 ```
 
-## clickhouse-keeper-01 configuration {#clickhouse-keeper-01-configuration}
+## Clickhouse-keeper-01 configuration {#clickhouse-keeper-01-configuration}
 
 <KeeperConfigFileNote />
 
@@ -286,7 +286,7 @@ If for any reason a Keeper node is replaced or rebuilt, do not reuse an existing
 </clickhouse>
 ```
 
-## clickhouse-keeper-02 configuration {#clickhouse-keeper-02-configuration}
+## Clickhouse-keeper-02 configuration {#clickhouse-keeper-02-configuration}
 
 There is only one line difference between `clickhouse-keeper-01` and `clickhouse-keeper-02`.  `server_id` is set to `2` on this node.
 
@@ -334,7 +334,7 @@ There is only one line difference between `clickhouse-keeper-01` and `clickhouse
 </clickhouse>
 ```
 
-## clickhouse-keeper-03 configuration {#clickhouse-keeper-03-configuration}
+## Clickhouse-keeper-03 configuration {#clickhouse-keeper-03-configuration}
 
 There is only one line difference between `clickhouse-keeper-01` and `clickhouse-keeper-03`.  `server_id` is set to `3` on this node.
 

docs/dictionary/index.md

@@ -314,7 +314,7 @@ LIMIT 4
 Peak memory usage: 666.82 MiB.
 ```
 
-## Advanced Dictionary Topics {#advanced-dictionary-topics}
+## Advanced dictionary topics {#advanced-dictionary-topics}
 
 ### Choosing the Dictionary `LAYOUT` {#choosing-the-dictionary-layout}
 

docs/faq/general/columnar-database.md

@@ -10,7 +10,7 @@ import Image from '@theme/IdealImage';
 import RowOriented from '@site/static/images/row-oriented.gif';
 import ColumnOriented from '@site/static/images/column-oriented.gif';
 
-# What Is a Columnar Database? {#what-is-a-columnar-database}
+# What is a columnar database? {#what-is-a-columnar-database}
 
 A columnar database stores the data of each column independently. This allows reading data from disk only for those columns that are used in any given query. The cost is that operations that affect whole rows become proportionally more expensive. The synonym for a columnar database is a column-oriented database management system. ClickHouse is a typical example of such a system.
 

docs/faq/general/dbms-naming.md

@@ -6,7 +6,7 @@ slug: /faq/general/dbms-naming
 description: 'Learn about What does "ClickHouse" mean?'
 ---
 
-# What Does "ClickHouse" Mean? {#what-does-clickhouse-mean}
+# What does "ClickHouse" mean? {#what-does-clickhouse-mean}
 
 It's a combination of "**Click**stream" and "Data ware**House**". It comes from the original use case at Yandex.Metrica, where ClickHouse was supposed to keep records of all clicks by people from all over the Internet, and it still does the job. You can read more about this use case on [ClickHouse history](../../about-us/history.md) page.
 

docs/faq/general/index.md

@@ -7,7 +7,7 @@ title: 'General Questions About ClickHouse'
 description: 'Index page listing general questions about ClickHouse'
 ---
 
-# General Questions About ClickHouse
+# General questions about ClickHouse
 
 - [What is ClickHouse?](../../intro.md)
 - [Why is ClickHouse so fast?](../../concepts/why-clickhouse-is-so-fast.md)

docs/faq/general/mapreduce.md

@@ -7,7 +7,7 @@ description: 'This page explains why you would use ClickHouse over MapReduce'
 keywords: ['MapReduce']
 ---
 
-# Why Not Use Something Like MapReduce? {#why-not-use-something-like-mapreduce}
+# Why not use something like MapReduce? {#why-not-use-something-like-mapreduce}
 
 We can refer to systems like MapReduce as distributed computing systems in which the reduce operation is based on distributed sorting. The most common open-source solution in this class is [Apache Hadoop](http://hadoop.apache.org). 
 

docs/faq/general/ne-tormozit.md

@@ -7,7 +7,7 @@ description: 'This page explains what "Не тормозит" means'
 keywords: ['Yandex']
 ---
 
-# What Does "Не тормозит" Mean? {#what-does-ne-tormozit-mean}
+# What does "Не тормозит" mean? {#what-does-ne-tormozit-mean}
 
 We often get this question when people see vintage (limited production) ClickHouse t-shirts. They have the words **"ClickHouse не тормозит"** written in big bold text on the front.
 

docs/faq/general/olap.md

@@ -20,15 +20,15 @@ Analytical
 Online
 :   ...in real-time.
 
-## OLAP from the Business Perspective {#olap-from-the-business-perspective}
+## OLAP from the business perspective {#olap-from-the-business-perspective}
 
 In recent years, business people started to realize the value of data. Companies who make their decisions blindly, more often than not fail to keep up with the competition. The data-driven approach of successful companies forces them to collect all data that might be remotely useful for making business decisions and need mechanisms to timely analyze them. Here's where OLAP database management systems (DBMS) come in.
 
 In a business sense, OLAP allows companies to continuously plan, analyze, and report operational activities, thus maximizing efficiency, reducing expenses, and ultimately conquering the market share. It could be done either in an in-house system or outsourced to SaaS providers like web/mobile analytics services, CRM services, etc. OLAP is the technology behind many BI applications (Business Intelligence).
 
 ClickHouse is an OLAP database management system that is pretty often used as a backend for those SaaS solutions for analyzing domain-specific data. However, some businesses are still reluctant to share their data with third-party providers and an in-house data warehouse scenario is also viable.
 
-## OLAP from the Technical Perspective {#olap-from-the-technical-perspective}
+## OLAP from the technical perspective {#olap-from-the-technical-perspective}
 
 All database management systems could be classified into two groups: OLAP (Online **Analytical** Processing) and OLTP (Online **Transactional** Processing). Former focuses on building reports, each based on large volumes of historical data, but doing it not so frequently. While the latter usually handle a continuous stream of transactions, constantly modifying the current state of data.