fix more headers

Author: Blargian

docs/cloud/manage/jan2025_faq/plan_migrations.md

@@ -28,19 +28,21 @@ Yes, see below for guidance on self-serve migrations:
 
 Users can upgrade during the trial and continue to use the trial credits to evaluate the new service tiers and the features it supports. However, if they choose to continue using the same Development and Production services, they can do so and upgrade to PAYG. They will still have to migrate before July 23, 2025.
 
-### Can users upgrade their tiers, i.e. Basic → Scale, Scale → Enterprise, etc? {#can-users-upgrade-their-tiers-ie-basic--scale-scale--enterprise-etc}
+### Can users upgrade their tiers {#can-users-upgrade-their-tiers-ie-basic--scale-scale--enterprise-etc}
 
-Yes, users can upgrade self-serve and the pricing will reflect the tier selection after upgrade.
+Can users upgrade their tiers, for example, Basic → Scale, Scale → Enterprise, etc.
+Yes, users can upgrade self-serve, and the pricing will reflect the tier selection after upgrade.
 
-### Can users move from a higher to a lower-cost tier, e.g., Enterprise → Scale, Scale → Basic, Enterprise → Basic self-serve? {#can-users-move-from-a-higher-to-a-lower-cost-tier-eg-enterprise--scale-scale--basic-enterprise--basic-self-serve}
+### Can users move from a higher to a lower-cost tier {#can-users-move-from-a-higher-to-a-lower-cost-tier-eg-enterprise--scale-scale--basic-enterprise--basic-self-serve}
 
+For example, Enterprise → Scale, Scale → Basic, Enterprise → Basic self-serve?
 No, we do not permit downgrading tiers.
 
-### Can users with only Development services in the organization migrate to the Basic tier? {#can-users-with-only-development-services-in-the-organization-migrate-to-the-basic-tier}
+### Can users with only development services in the organization migrate to the Basic tier? {#can-users-with-only-development-services-in-the-organization-migrate-to-the-basic-tier}
 
 Yes, this would be permitted. Users will be given a recommendation based on their past use and can select Basic `1x8GiB` or `1x12GiB`.
 
-### Can users with a Development and Production service in the same organization move to the Basic Tier? {#can-users-with-a-development-and-production-service-in-the-same-organization-move-to-the-basic-tier}
+### Can users with a development and production service in the same organization move to the basic tier? {#can-users-with-a-development-and-production-service-in-the-same-organization-move-to-the-basic-tier}
 
 No, if a user has both Development and Production services in the same organization, they can self-serve and migrate only to the Scale or Enterprise tier. If they want to migrate to Basic, they should delete all existing Production services.
 

docs/cloud/manage/postman.md

@@ -28,16 +28,19 @@ This guide will help you test the ClickHouse Cloud API using [Postman](https://w
 The Postman Application is available for use within a web browser or can be downloaded to a desktop.
 
 ### Create an account {#create-an-account}
+
 * Free accounts are available at [https://www.postman.com](https://www.postman.com).
 
 <Image img={postman1} size="md" alt="Postman site" border/>
 
-### Create a Workspace {#create-a-workspace}
+### Create a workspace {#create-a-workspace}
+
 * Name your workspace and set the visibility level. 
 
 <Image img={postman2} size="md" alt="Create workspace" border/>
 
-### Create a Collection {#create-a-collection}
+### Create a collection {#create-a-collection}
+
 * Below "Explore" on the top left Menu click "Import": 
 
 <Image img={postman3} size="md" alt="Explore > Import" border/>
@@ -63,7 +66,7 @@ The Postman Application is available for use within a web browser or can be down
 
 <Image img={postman8} size="md" alt="Import complete" border/>
 
-### Set Authorization {#set-authorization}
+### Set authorization {#set-authorization}
 * Toggle the dropdown menu to select "Basic Auth":
 
 <Image img={postman9} size="md" alt="Basic auth" border/>
@@ -72,17 +75,22 @@ The Postman Application is available for use within a web browser or can be down
 
 <Image img={postman10} size="md" alt="credentials" border/>
 
-### Enable Variables {#enable-variables}
+### Enable variables {#enable-variables}
+
 * [Variables](https://learning.postman.com/docs/sending-requests/variables/) enable the storage and reuse of values in Postman allowing for easier API testing.
-#### Set the Organization ID and Service ID {#set-the-organization-id-and-service-id}
+
+#### Set the organization ID and Service ID {#set-the-organization-id-and-service-id}
+
 * Within the "Collection", click the "Variable" tab in the middle pane (The Base URL will have been set by the earlier API import):
 * Below `baseURL` click the open field "Add new value", and Substitute your organization ID and service ID:
 
 <Image img={postman11} size="md" alt="Organization ID and Service ID" border/>
 
 
 ## Test the ClickHouse Cloud API functionalities {#test-the-clickhouse-cloud-api-functionalities}
+
 ### Test "GET list of available organizations" {#test-get-list-of-available-organizations}
+
 * Under the "OpenAPI spec for ClickHouse Cloud", expand the folder > V1 > organizations
 * Click "GET list of available organizations" and press the blue "Send" button on the right:
 
@@ -93,6 +101,7 @@ The Postman Application is available for use within a web browser or can be down
 <Image img={postman13} size="md" alt="Status" border/>
 
 ### Test "GET organizational details" {#test-get-organizational-details}
+
 * Under the `organizationid` folder, navigate to "GET organizational details":
 * In the middle frame menu under Params an `organizationid` is required.
 
@@ -109,6 +118,7 @@ The Postman Application is available for use within a web browser or can be down
 * The returned results should deliver your organization details with "status": 200. (If you receive a "status" 400 with no organization information your configuration is not correct).
 
 ### Test "GET service details" {#test-get-service-details}
+
 * Click "GET service details"
 * Edit the Values for `organizationid` and `serviceid` with `{{orgid}}` and `{{serviceid}}` respectively.
 * Press "Save" and then the blue "Send" button on the right.

docs/cloud/manage/scaling.md

@@ -15,7 +15,7 @@ import scaling_configure from '@site/static/images/cloud/manage/scaling-configur
 import scaling_memory_allocation from '@site/static/images/cloud/manage/scaling-memory-allocation.png';
 import ScalePlanFeatureBadge from '@theme/badges/ScalePlanFeatureBadge'
 
-# Automatic Scaling
+# Automatic scaling
 
 Scaling is the ability to adjust available resources to meet client demands. Scale and Enterprise (with standard 1:4 profile) tier services can be scaled horizontally by calling an API programmatically, or changing settings on the UI to adjust system resources. Alternatively, these services can be **autoscaled** vertically to meet application demands.
 
@@ -110,7 +110,7 @@ Once the service has scaled, the metrics dashboard in the cloud console should s
 
 <Image img={scaling_memory_allocation} size="md" alt="Scaling memory allocation" border />
 
-## Automatic Idling {#automatic-idling}
+## Automatic idling {#automatic-idling}
 In the **Settings** page, you can also choose whether or not to allow automatic idling of your service when it is inactive as shown in the image above (i.e. when the service is not executing any user-submitted queries).  Automatic idling reduces the cost of your service, as you are not billed for compute resources when the service is paused.
 
 :::note
@@ -123,7 +123,8 @@ The service may enter an idle state where it suspends refreshes of [refreshable
 Use automatic idling only if your use case can handle a delay before responding to queries, because when a service is paused, connections to the service will time out. Automatic idling is ideal for services that are used infrequently and where a delay can be tolerated. It is not recommended for services that power customer-facing features that are used frequently.
 :::
 
-## Handling bursty workloads {#handling-bursty-workloads}
+## Handling spikes in workload {#handling-bursty-workloads}
+
 If you have an upcoming expected spike in your workload, you can use the
 [ClickHouse Cloud API](/cloud/manage/api/api-overview) to 
 preemptively scale up your service to handle the spike and scale it down once

docs/cloud/manage/settings.md

@@ -8,7 +8,7 @@ description: 'How to configure settings for your ClickHouse Cloud service for a
 import Image from '@theme/IdealImage';
 import cloud_settings_sidebar from '@site/static/images/cloud/manage/cloud-settings-sidebar.png';
 
-# Configuring Settings
+# Configuring settings
 
 To specify settings for your ClickHouse Cloud service for a specific [user](/operations/access-rights#user-account-management) or [role](/operations/access-rights#role-management), you must use [SQL-driven Settings Profiles](/operations/access-rights#settings-profiles-management). Applying Settings Profiles ensures that the settings you configure persist, even when your services stop, idle, and upgrade. To learn more about Settings Profiles, please see [this page](/operations/settings/settings-profiles.md).
 

docs/cloud/reference/byoc.md

@@ -48,23 +48,23 @@ Metrics and logs are stored within the customer's BYOC VPC. Logs are currently s
 
 <br />
 
-## Onboarding Process {#onboarding-process}
+## Onboarding process {#onboarding-process}
 
 Customers can initiate the onboarding process by reaching out to [us](https://clickhouse.com/cloud/bring-your-own-cloud). Customers need to have a dedicated AWS account and know the region they will use. At this time, we are allowing users to launch BYOC services only in the regions that we support for ClickHouse Cloud.
 
-### Prepare an AWS Account {#prepare-an-aws-account}
+### Prepare an AWS account {#prepare-an-aws-account}
 
 Customers are recommended to prepare a dedicated AWS account for hosting the ClickHouse BYOC deployment to ensure better isolation. However, using a shared account and an existing VPC is also possible. See the details in *Setup BYOC Infrastructure* below.
 
 With this account and the initial organization admin email, you can contact ClickHouse support.
 
-### Apply CloudFormation Template {#apply-cloudformation-template}
+### Apply CloudFormation template {#apply-cloudformation-template}
 
 BYOC setup is initialized via a [CloudFormation stack](https://s3.us-east-2.amazonaws.com/clickhouse-public-resources.clickhouse.cloud/cf-templates/byoc.yaml), which creates only a role allowing BYOC controllers from ClickHouse Cloud to manage infrastructure. The S3, VPC, and compute resources for running ClickHouse are not included in this stack.
 
 <!-- TODO: Add Screenshot for the rest of onboarding, once self-served onboarding is implemented. -->
 
-### Setup BYOC Infrastructure {#setup-byoc-infrastructure}
+### Set up BYOC infrastructure {#setup-byoc-infrastructure}
 
 After creating the CloudFormation stack, you will be prompted to set up the infrastructure, including S3, VPC, and the EKS cluster, from the cloud console. Certain configurations must be determined at this stage, as they cannot be changed later. Specifically:
 
@@ -106,7 +106,7 @@ Create a support ticket with the following information:
 
 To create or delete VPC peering for ClickHouse BYOC, follow the steps:
 
-#### Step 1 Enable Private Load Balancer for ClickHouse BYOC {#step-1-enable-private-load-balancer-for-clickhouse-byoc}
+#### Step 1: Enable private load balancer for ClickHouse BYOC {#step-1-enable-private-load-balancer-for-clickhouse-byoc}
 Contact ClickHouse Support to enable Private Load Balancer.
 
 #### Step 2 Create a peering connection {#step-2-create-a-peering-connection}
@@ -162,7 +162,7 @@ In the peering AWS account,
 
 <br />
 
-#### Step 6 Edit Security Group to allow Peered VPC access {#step-6-edit-security-group-to-allow-peered-vpc-access}
+#### Step 6: Edit security group to allow peered VPC access {#step-6-edit-security-group-to-allow-peered-vpc-access}
 In the ClickHouse BYOC account, you need to update the Security Group settings to allow traffic from your peered VPC. Please contact ClickHouse Support to request the addition of inbound rules that include the CIDR ranges of your peered VPC.
 
 ---
@@ -174,7 +174,7 @@ To access ClickHouse privately, a private load balancer and endpoint are provisi
 
 Optional, after verifying that peering is working, you can request the removal of the public load balancer for ClickHouse BYOC.
 
-## Upgrade Process {#upgrade-process}
+## Upgrade process {#upgrade-process}
 
 We regularly upgrade the software, including ClickHouse database version upgrades, ClickHouse Operator, EKS, and other components.
 
@@ -184,7 +184,7 @@ While we aim for seamless upgrades (e.g., rolling upgrades and restarts), some,
 Maintenance windows do not apply to security and vulnerability fixes. These are handled as off-cycle upgrades, with timely communication to coordinate a suitable time and minimize operational impact.
 :::
 
-## CloudFormation IAM Roles {#cloudformation-iam-roles}
+## CloudFormation IAM roles {#cloudformation-iam-roles}
 
 ### Bootstrap IAM role {#bootstrap-iam-role}
 
@@ -218,7 +218,7 @@ These roles are assumed by applications running within the customer's EKS cluste
 
 Lastly, **`data-plane-mgmt`** allows a ClickHouse Cloud Control Plane component to reconcile necessary custom resources, such as `ClickHouseCluster` and the Istio Virtual Service/Gateway.
 
-## Network Boundaries {#network-boundaries}
+## Network boundaries {#network-boundaries}
 
 This section covers different network traffic to and from the customer BYOC VPC:
 
@@ -309,7 +309,7 @@ Besides Clickhouse instances (ClickHouse servers and ClickHouse Keeper), we run
 
 Currently we have 3 m5.xlarge nodes (one for each AZ) in a dedicated node group to run those workloads.
 
-### Network and Security {#network-and-security}
+### Network and security {#network-and-security}
 
 #### Can we revoke permissions set up during installation after setup is complete? {#can-we-revoke-permissions-set-up-during-installation-after-setup-is-complete}
 
@@ -331,9 +331,9 @@ Contact support to schedule maintenance windows. Please expect a minimum of a we
 
 ## Observability {#observability}
 
-### Built-in Monitoring Tools {#built-in-monitoring-tools}
+### Built-in monitoring tools {#built-in-monitoring-tools}
 
-#### Observability Dashboard {#observability-dashboard}
+#### Observability dashboard {#observability-dashboard}
 
 ClickHouse Cloud includes an advanced observability dashboard that displays metrics such as memory usage, query rates, and I/O. This can be accessed in the **Monitoring** section of ClickHouse Cloud web console interface.
 
@@ -343,7 +343,7 @@ ClickHouse Cloud includes an advanced observability dashboard that displays metr
 
 <br />
 
-#### Advanced Dashboard {#advanced-dashboard}
+#### Advanced dashboard {#advanced-dashboard}
 
 You can customize a dashboard using metrics from system tables like `system.metrics`, `system.events`, and `system.asynchronous_metrics` and more to monitor server performance and resource utilization in detail.
 

docs/cloud/reference/changelog.md

@@ -274,7 +274,7 @@ Org Admins can now add more email addresses to a specific notification as additi
 
 Bring Your Own Cloud for AWS is now available in Beta. This deployment model allows you to deploy and run ClickHouse Cloud in your own AWS account. We support deployments in 11+ AWS regions, with more coming soon. Please [contact support](https://clickhouse.com/support/program) for access. Note that this deployment is reserved for large-scale deployments.
 
-### Postgres Change Data Capture (CDC) Connector in ClickPipes {#postgres-change-data-capture-cdc-connector-in-clickpipes}
+### Postgres Change Data Capture (CDC) connector in ClickPipes {#postgres-change-data-capture-cdc-connector-in-clickpipes}
 
 This turnkey integration enables customers to replicate their Postgres databases to ClickHouse Cloud in just a few clicks and leverage ClickHouse for blazing-fast analytics. You can use this connector for both continuous replication and one-time migrations from Postgres.
 
@@ -553,7 +553,7 @@ You can try the new Amazon Kinesis integration for ClickPipes in the cloud conso
 
 <Image img={kenesis} size="lg" alt="ClickPipes interface showing Amazon Kinesis integration configuration options" border />
 
-### Configurable Backups (Private Preview) {#configurable-backups-private-preview}
+### Configurable backups (private preview) {#configurable-backups-private-preview}
 
 Backups are important for every database (no matter how reliable), and we've taken backups very seriously since day 1 of ClickHouse Cloud. This week, we launched Configurable Backups, which allows for much more flexibility for your service's backups. You can now control start time, retention, and frequency. This feature is available for **Production** and **Dedicated** services and is not available for **Development** services. As this feature is in private preview, please contact [email protected] to enable this for your service. Read more about configurable backups [here](https://clickhouse.com/blog/configurable-backups-in-clickhouse-cloud).
 
@@ -1020,14 +1020,15 @@ This release brings the public release of the ClickHouse Cloud Programmatic API
 
 ## May 11, 2023 {#may-11-2023}
 
-This release brings the ~~public beta~~ (now GA, see June 20th entry above) of ClickHouse Cloud on GCP (see [blog](https://clickhouse.com/blog/clickhouse-cloud-on-gcp-available-in-public-beta) for details), extends administrators rights to grant terminate query permissions, and adds more visibility into the status of MFA users in the Cloud console.
+This release brings the public beta (now GA, see June 20th entry above) of ClickHouse Cloud on GCP (see [blog](https://clickhouse.com/blog/clickhouse-cloud-on-gcp-available-in-public-beta) for details), extends administrators' rights to grant terminate query permissions, and adds more visibility into the status of MFA users in the Cloud console.
 
-### ClickHouse Cloud on GCP ~~(Public Beta)~~ (now GA, see June 20th entry above) {#clickhouse-cloud-on-gcp-public-beta-now-ga-see-june-20th-entry-above}
+### ClickHouse Cloud on GCP is now available in public beta (now GA, see June 20th entry above) {#clickhouse-cloud-on-gcp-is-now-available-in-public-beta-now-ga-see-june-20th-entry-above}
 - Launches a fully-managed separated storage and compute ClickHouse offering, running on top of Google Compute and Google Cloud Storage
 - Available in Iowa (us-central1), Netherlands (europe-west4), and Singapore (asia-southeast1) regions
 - Supports both Development and Production services in all three initial regions
 - Provides strong security by default: End-to-end encryption in transit, data-at-rest encryption, IP Allow Lists
 
+{{ ... }}
 ### Integrations changes {#integrations-changes-18}
 - Golang client: Added proxy environment variables support
 - Grafana: Added the ability to specify ClickHouse custom settings and proxy environment variables in Grafana datasource setup
@@ -1279,7 +1280,7 @@ This release introduces seamless logins for administrators to SQL console, impro
 ### Integrations changes {#integrations-changes-26}
 - The [Metabase plugin](/integrations/data-visualization/metabase-and-clickhouse.md) got a long-awaited v0.9.1 major update. Now it is compatible with the latest Metabase version and has been thoroughly tested against ClickHouse Cloud.
 
-## December 6, 2022 - General Availability {#december-6-2022---general-availability}
+## December 6, 2022 - General availability {#december-6-2022---general-availability}
 
 ClickHouse Cloud is now production-ready with SOC2 Type II compliance, uptime SLAs for production workloads, and public status page. This release includes major new capabilities like AWS Marketplace integration, SQL console - a data exploration workbench for ClickHouse users, and ClickHouse Academy - self-paced learning in ClickHouse Cloud. Learn more in this [blog](https://clickhouse.com/blog/clickhouse-cloud-generally-available).