more spellings

Author: gingerwizard

docs/en/chdb/install/python.md

@@ -67,7 +67,7 @@ res = chdb.query('select * from file("data.csv", CSV)', 'CSV');  print(res)
 print(f"SQL read {res.rows_read()} rows, {res.bytes_read()} bytes, elapsed {res.elapsed()} seconds")
 ```
 
-**Pandas dataframe output**
+**Pandas DataFrame output**
 ```python
 # See more in https://clickhouse.com/docs/en/interfaces/formats
 chdb.query('select * from file("data.parquet", Parquet)', 'Dataframe')

docs/en/cloud/reference/changelog.md

@@ -966,7 +966,7 @@ Adds support for a subset of features in ClickHouse 23.1, for example:
   - Added a feature to explore all available databases
   - Fixed synchronization of database with AggregationFunction type
 - [DBT-clickhouse](/docs/en/integrations/data-ingestion/etl-tools/dbt/index.md): Added support for the latest DBT version v1.4.1
-- [Python client](/docs/en/integrations/language-clients/python/index.md): Improved proxy and ssh tunneling support; added a number of fixes and performance optimizations for Pandas dataframes
+- [Python client](/docs/en/integrations/language-clients/python/index.md): Improved proxy and ssh tunneling support; added a number of fixes and performance optimizations for Pandas DataFrames
 - [Nodejs client](/docs/en/integrations/language-clients/js.md): Released ability to attach `query_id` to query result, which can be used to retrieve query metrics from the `system.query_log`
 - [Golang client](/docs/en/integrations/language-clients/go/index.md): Optimized network connection with ClickHouse Cloud
 

docs/en/cloud/security/cmek.md

@@ -18,7 +18,7 @@ Coming soon:
 
 - [Azure Key Vault](https://azure.microsoft.com/en-us/products/key-vault) for services hosted on: Azure
 - [GCP Cloud Key Management](https://cloud.google.com/security-key-management) for services hosted on: GCP
-- [Hashicorp Vault](https://www.hashicorp.com/products/vault) for services hosted on: AWS, Azure, GCP
+- [HashiCorp Vault](https://www.hashicorp.com/products/vault) for services hosted on: AWS, Azure, GCP
 
 :::warning
 Deleting a KMS key used to encrypt a ClickHouse Cloud service will cause your ClickHouse service to be stopped and its data will be unretrievable, along with existing backups.

docs/en/cloud/security/gcp-private-service-connect.md

@@ -108,7 +108,7 @@ In the Google Cloud console, navigate to **Network services -> Private Service C
 Open the Private Service Connect creation dialog by clicking on the **Connect Endpoint** button.
 
 - **Target**: use **Published service**
-- **Target service**: use **endpointServiceId** from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step.
+- **Target service**: use `endpointServiceId` from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step.
 - **Endpoint name**: set a name for the PSC **Endpoint name**.
 - **Network/Subnetwork/IP address**: Choose the network you want to use for the connection. You will need to create an IP address or use an existing one for the Private Service Connect endpoint. In our example, we pre-created an address with the name **your-ip-address** and assigned IP address `10.128.0.2`
 - To make the endpoint available from any region, you can enable the **Enable global access** checkbox.
@@ -172,7 +172,7 @@ output "psc_connection_id" {
 ```
 
 :::note
-TARGET - Use **endpointServiceId** from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
+TARGET - Use `endpointServiceId` from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
 :::
 
 ## Setting up DNS
@@ -228,7 +228,7 @@ gcloud dns \
   --rrdatas="10.128.0.2"
 ```
 :::note
-DNS_RECORD - use **privateDnsHostname** from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
+DNS_RECORD - use `privateDnsHostname` from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
 :::
 
 ### Option 3: Using Terraform
@@ -256,12 +256,12 @@ resource "google_dns_record_set" "psc_dns_record" {
 ```
 
 :::note
-DNS_NAME - Use **privateDnsHostname** from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
+DNS_NAME - Use `privateDnsHostname` from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
 :::
 
 ## Verify DNS setup
 
-DNS_RECORD - Use **privateDnsHostname** from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
+DNS_RECORD - Use `privateDnsHostname` from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
 
 ```bash
 ping $DNS_RECORD
@@ -387,7 +387,7 @@ curl --silent --user ${KEY_ID:?}:${KEY_SECRET:?} -X PATCH -H "Content-Type: appl
 
 ## Accessing instance using Private Service Connect
 
-Each instance with configured Private Service Connect filters has two endpoints: public and private. In order to connect using Private Service Connect, you need to use a private endpoint, see use **endpointServiceId** from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
+Each instance with configured Private Service Connect filters has two endpoints: public and private. In order to connect using Private Service Connect, you need to use a private endpoint, see use `endpointServiceId` from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
 
 :::note
 Private DNS hostname is only available from your GCP VPC. Do not try to resolve the DNS host from a machine that resides outside of GCP VPC.
@@ -421,7 +421,7 @@ In this example, connection to the `xxxxxxx.yy-xxxxN.p.gcp.clickhouse.cloud` hos
 
 ### Test DNS setup
 
-DNS_NAME - Use **privateDnsHostname** from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
+DNS_NAME - Use `privateDnsHostname` from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
 
 ```bash
 nslookup $DNS_NAME
@@ -443,7 +443,7 @@ If you have problems with connecting using PSC link, check your connectivity usi
 
 OpenSSL should be able to connect (see CONNECTED in the output). `errno=104` is expected.
 
-DNS_NAME - Use **privateDnsHostname** from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
+DNS_NAME - Use `privateDnsHostname` from [Obtain GCP service attachment for Private Service Connect](#obtain-gcp-service-attachment-and-dns-name-for-private-service-connect) step
 
 ```bash
 openssl s_client -connect ${DNS_NAME}:9440

docs/en/integrations/data-ingestion/clickpipes/postgres/faq.md

@@ -9,7 +9,7 @@ sidebar_position: 2
 
 ### How does idling affect my Postgres CDC ClickPipe?
 
-If your ClickHouse Cloud service is idling, your Postgres CDC clickpipe will continue to sync data, your service will wake-up at the next sync interval to handle the incoming data. Once the sync is finished and the idle period is reached, your service will go back to idling.
+If your ClickHouse Cloud service is idling, your Postgres CDC ClickPipe will continue to sync data, your service will wake-up at the next sync interval to handle the incoming data. Once the sync is finished and the idle period is reached, your service will go back to idling.
 
 As an example, if your sync interval is set to 30 mins and your service idle time is set to 10 mins, Your service will wake-up every 30 mins and be active for 10 mins, then go back to idling.
 
@@ -48,9 +48,9 @@ Yes! ClickPipes for Postgres offers two ways to connect to databases in private
 
 ### How do you handle UPDATEs and DELETEs?
 
-ClickPipes for Postgres captures both INSERTs and UPDATEs from Postgres as new rows with different versions (using the _peerdb_version column) in ClickHouse. The ReplacingMergeTree table engine periodically performs deduplication in the background based on the ordering key (ORDER BY columns), retaining only the row with the latest _peerdb_version.
+ClickPipes for Postgres captures both INSERTs and UPDATEs from Postgres as new rows with different versions (using the `_peerdb_` version column) in ClickHouse. The ReplacingMergeTree table engine periodically performs deduplication in the background based on the ordering key (ORDER BY columns), retaining only the row with the latest `_peerdb_` version.
 
-DELETEs from Postgres are propagated as new rows marked as deleted (using the _peerdb_is_deleted column). Since the deduplication process is asynchronous, you might temporarily see duplicates. To address this, you need to handle deduplication at the query layer.
+DELETEs from Postgres are propagated as new rows marked as deleted (using the `_peerdb_is_deleted` column). Since the deduplication process is asynchronous, you might temporarily see duplicates. To address this, you need to handle deduplication at the query layer.
 
 For more details, refer to:
 
@@ -97,7 +97,7 @@ If you're noticing that the size of your Postgres replication slot keeps increas
 
 4. **VACUUM and VACUUM ANALYZE**  
    - Although necessary for database health, these operations can create extra WAL traffic—especially if they scan large tables.  
-   - Consider using autovacuum tuning parameters or scheduling manual VACUUMs during off-peak hours.
+   - Consider using autovacuum tuning parameters or scheduling manual VACUUM operations during off-peak hours.
 
 5. **Replication Consumer Not Actively Reading the Slot**  
    - If your CDC pipeline (e.g., ClickPipes) or another replication consumer stops, pauses, or crashes, WAL data will accumulate in the slot.  
@@ -136,13 +136,13 @@ As of now, you can create a ClickPipe only via the UI. However, we are actively
 
 You cannot speed up an already running initial load. However, you can optimize future initial loads by adjusting certain settings. By default, the settings are configured with 4 parallel threads and a snapshot number of rows per partition set to 100,000. These are advanced settings and are generally sufficient for most use cases.
 
-For Postgres versions 13 or lower, ctid range scans are slower, and these settings become more critical. In such cases, consider the following process to improve performance:
+For Postgres versions 13 or lower, CTID range scans are slower, and these settings become more critical. In such cases, consider the following process to improve performance:
 
 1. **Drop the existing pipe**: This is necessary to apply new settings.
 2. **Delete destination tables on ClickHouse**: Ensure that the tables created by the previous pipe are removed.
 3. **Create a new pipe with optimized settings**: Typically, increase the snapshot number of rows per partition to between 1 million and 10 million, depending on your specific requirements and the load your Postgres instance can handle.
 
-These adjustments should significantly enhance the performance of the initial load, especially for older Postgres versions. If you are using Postgres 14 or later, these settings are less impactful due to improved support for ctid range scans.
+These adjustments should significantly enhance the performance of the initial load, especially for older Postgres versions. If you are using Postgres 14 or later, these settings are less impactful due to improved support for CTID range scans.
 
 ### How should I scope my publications when setting up replication?
 

docs/en/integrations/data-ingestion/clickpipes/postgres/postgres_generated_columns.md

@@ -7,7 +7,7 @@ When using PostgreSQL's generated columns in tables that are being replicated, t
 
 ## The Problem with Generated Columns
 
-1. **Not Published via pgoutput:** Generated columns are not published through the pgoutput logical replication plugin. This means that when you're replicating data from PostgreSQL to another system, the values of generated columns are not included in the replication stream.
+1. **Not Published via `pgoutput`:** Generated columns are not published through the `pgoutput` logical replication plugin. This means that when you're replicating data from PostgreSQL to another system, the values of generated columns are not included in the replication stream.
 
 2. **Issues with Primary Keys:** If a generated column is part of your primary key, it can cause deduplication problems on the destination. Since the generated column values are not replicated, the destination system won't have the necessary information to properly identify and deduplicate rows.
 

docs/en/integrations/data-ingestion/clickpipes/postgres/source/google-cloudsql.md

@@ -1,10 +1,10 @@
 ---
-sidebar_label: Google CloudSQL
-description: Set up Google CloudSQL Postgres instance as a source for ClickPipes
+sidebar_label: Google Cloud SQL
+description: Set up Google Cloud SQL Postgres instance as a source for ClickPipes
 slug: /en/integrations/clickpipes/postgres/source/google-cloudsql
 ---
 
-# Google CloudSQL Postgres Source Setup Guide
+# Google Cloud SQL Postgres Source Setup Guide
 
 :::info
 
@@ -23,19 +23,19 @@ Anything on or after Postgres 12
 
 1. Click on **Edit** button on the Overview page.
 
-   ![Edit Button in CloudSQL Postgres](images/setup/google-cloudsql/edit.png)
+   ![Edit Button in Cloud SQL Postgres](images/setup/google-cloudsql/edit.png)
 
 
 2. Go to Flags and change `cloudsql.logical_decoding` to on and `wal_sender_timeout` to 0. These changes will need restarting your Postgres server.
 
-   ![Change cloudsql.logical_decoding to on](images/setup/google-cloudsql/cloudsql_logical_decoding1.png)
-   ![Changed cloudsql.logical_decoding and wal_sender_timeout](images/setup/google-cloudsql/cloudsql_logical_decoding2.png)
+   ![Change `cloudsql.logical_decoding` to on](images/setup/google-cloudsql/cloudsql_logical_decoding1.png)
+   ![Changed `cloudsql.logical_decoding` and `wal_sender_timeout`](images/setup/google-cloudsql/cloudsql_logical_decoding2.png)
    ![Restart Server](images/setup/google-cloudsql/cloudsql_logical_decoding3.png)
 
 
 ## Creating ClickPipes User and Granting permissions
 
-Connect to your CloudSQL Postgres through the admin user and run the below commands:
+Connect to your Cloud SQL Postgres through the admin user and run the below commands:
 
 1. Create a Postgres user for exclusively ClickPipes.
 

docs/en/integrations/data-ingestion/clickpipes/postgres/source/supabase.md

@@ -10,7 +10,7 @@ This is a guide on how to setup Supabase Postgres for usage in ClickPipes.
 
 :::note
 
-ClickPipes supports Supabase via IPv6 natively for seemless replication.
+ClickPipes supports Supabase via IPv6 natively for seamless replication.
 
 :::
 

docs/en/integrations/data-ingestion/data-formats/binary.md

@@ -197,7 +197,7 @@ This saves data to the [proto.bin](assets/proto.bin) file. ClickHouse also suppo
 
 <CloudNotSupportedBadge/>
 
-Another popular binary serialization format supported by ClickHouse is [Cap’n Proto](https://capnproto.org/). Similarly to `Protobuf` format, we have to define a schema file ([schema.capnp](assets/schema.capnp)) in our example:
+Another popular binary serialization format supported by ClickHouse is [Cap’n Proto](https://capnproto.org/). Similarly to `Protobuf` format, we have to define a schema file ([`schema.capnp`](assets/schema.capnp)) in our example:
 
 ```
 @0xec8ff1a10aa10dbe;