Apply suggestions from code review

Blargian · web-flow · commit 84e6f95ab4be · 2025-07-13T19:50:16.000+02:00
diff --git a/docs/about-us/cloud.md b/docs/about-us/cloud.md
@@ -11,7 +11,7 @@ title: '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:
 
diff --git a/docs/best-practices/sizing-and-hardware-recommendations.md b/docs/best-practices/sizing-and-hardware-recommendations.md
@@ -6,7 +6,7 @@ title: 'Sizing and hardware recommendations'
 description: 'This guide discusses our general recommendations regarding hardware, compute, memory, and disk configurations for open-source users.'
 ---
 
-# Sizing and hardware recommendations'
+# Sizing and hardware recommendations
 
 This guide discusses our general recommendations regarding hardware, compute, memory, and disk configurations for open-source users. If you would like to simplify your setup, we recommend using [ClickHouse Cloud](https://clickhouse.com/cloud) as it automatically scales and adapts to your workloads while minimizing costs pertaining to infrastructure management.
 
diff --git a/docs/cloud/manage/account-close.md b/docs/cloud/manage/account-close.md
@@ -5,13 +5,13 @@ title: 'Account Close & Deletion'
 description: 'We know there are circumstances that sometimes necessitate account closure. This guide will help you through the process.'
 ---
 
-## Account close & deletion {#account-close--deletion}
+## Account closure and deletion {#account-close--deletion}
 Our goal is to help you be successful in your project. If you have questions that are not answered on this site or need help evaluating a
 unique use case, please contact us at [support@clickhouse.com](mailto:support@clickhouse.com).
 
 We know there are circumstances that sometimes necessitate account closure. This guide will help you through the process.
 
-## Close vs delete {#close-vs-delete}
+## Close versus delete your account {#close-vs-delete}
 Customers may log back into closed accounts to view usage, billing and account-level activity logs. This enables you to easily access
 details that are useful for a variety of purposes, from documenting use cases to downloading invoices at the end of the year for tax purposes.
 You will also continue receiving product updates so that you know if a feature you may have been waiting for is now available. Additionally,
@@ -31,7 +31,7 @@ Before requesting account closure, please take the following steps to prepare th
 3. Remove all users except the admin that will request closure. This will help you ensure no new services are created while the process completes.
 4. Review the 'Usage' and 'Billing' tabs in the control panel to verify all charges have been paid. We are not able to close accounts with unpaid balances.
 
-## Request account closure {#request-account-closure}
+## Request an account closure {#request-account-closure}
 
 We are required to authenticate requests for both closure and deletion. To ensure your request can be processed quickly, please follow the steps outlined
 below.
@@ -51,7 +51,7 @@ Description: We would appreciate it if you would share a brief note about why yo
 6. We will close your account and send a confirmation email to let you know when it is complete.
 
 
-## Request personal data deletion {#request-personal-data-deletion}
+## Request deletion of your personal data {#request-personal-data-deletion}
 Please note, only account administrators may request personal data deletion from ClickHouse. If you are not an account administrator, please contact
 your ClickHouse account administrator to request to be removed from the account.
 
diff --git a/docs/cloud/security/aws-privatelink.md b/docs/cloud/security/aws-privatelink.md
@@ -39,7 +39,7 @@ ClickHouse Cloud currently supports [cross-region PrivateLink](https://aws.amazo
 Find Terraform examples [here](https://github.com/ClickHouse/terraform-provider-clickhouse/tree/main/examples/).
 
 
-## Attention to the following {#attention}
+## Points of attention {#attention}
 ClickHouse attempts to group your services to reuse the same published [service endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-share-your-services.html#endpoint-service-overview) within the AWS region. However, this grouping is not guaranteed, especially if you spread your services across multiple ClickHouse organizations.
 If you already have PrivateLink configured for other services in your ClickHouse organization, you can often skip most of the steps because of that grouping and proceed directly to the final step: Add ClickHouse "Endpoint ID" to ClickHouse service allow list.
 
diff --git a/docs/deployment-guides/replicated.md b/docs/deployment-guides/replicated.md
@@ -46,7 +46,7 @@ Install ClickHouse Keeper on the three servers `clickhouse-keeper-01`, `clickhou
 
 <ConfigFileNote />
 
-## Clickhouse-01 configuration {#clickhouse-01-configuration}
+## Configure `clickhouse-01` {#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}
+## Configure `clickhouse-02` {#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}
+## Configure `clickhouse-keeper-01` {#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}
+## Configure `clickhouse-keeper-02` {#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}
+## Configure `clickhouse-keeper-03` {#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.
 
diff --git a/docs/getting-started/example-datasets/nypd_complaint_data.md b/docs/getting-started/example-datasets/nypd_complaint_data.md
@@ -365,7 +365,7 @@ of `ORDER BY` or `PRIMARY KEY` must be specified.  Here are some guidelines on d
 columns to includes in `ORDER BY`, and more information is in the *Next Steps* section at the end
 of this document.
 
-### Order by and primary key clauses {#order-by-and-primary-key-clauses}
+### `ORDER BY` and `PRIMARY KEY` clauses {#order-by-and-primary-key-clauses}
 
 - The `ORDER BY` tuple should include fields that are used in query filters
 - To maximize compression on disk the `ORDER BY` tuple should be ordered by ascending cardinality
diff --git a/docs/guides/best-practices/skipping-indexes.md b/docs/guides/best-practices/skipping-indexes.md
@@ -174,7 +174,7 @@ queries.  In circumstances where querying a table is too expensive unless a skip
 names will return an exception for any query that does not use the listed index.  This would prevent poorly written queries from
 consuming server resources.
 
-## Skip best practices {#skip-best-practices}
+## Skip index best practices {#skip-best-practices}
 
 Skip indexes are not intuitive, especially for users accustomed to secondary row-based indexes from the RDMS realm or inverted indexes from document stores. To get any benefit, applying a ClickHouse data skipping index must avoid enough granule reads to offset the cost of calculating the index. Critically, if a value occurs even once in an indexed block, it means the entire block must be read into memory and evaluated, and the index cost has been needlessly incurred.
 
