Adjust FAQ for Kafka and Kinesis ClickPipes

Author: morsapaes

docs/cloud/manage/jan2025_faq/_snippets/_clickpipes_faq.md

@@ -54,7 +54,7 @@ This corresponds to **0.25** ClickHouse compute units (1 unit = 8 GiB RAM, 2 vCP
 
 Yes, ClickPipes for streaming can be scaled both horizontally and vertically.
 Horizontal scaling adds more replicas to increase throughput, while vertical scaling increases the resources (CPU and RAM) allocated to each replica to handle more intensive workloads.
-Both can be done via the UI during the creation of the ClickPipe or later in the editing mode under "Settings" -> "Advanced Settings" -> "Scaling"
+This can be configured during ClickPipe creation, or at any other point under **Settings** -> **Advanced Settings** -> **Scaling**.
 
 </details>
 

docs/integrations/data-ingestion/clickpipes/kafka/04_best_practices.md

@@ -133,17 +133,17 @@ the ClickPipe will automatically restart the consumer and continue processing me
 
 ### Benchmarks {#benchmarks}
 
-Below are some informal benchmarks for ClickPipes for Kafka that can be used get a general idea of ClickPipes performance. It is important to know that many factors can impact performance including message size, data types, and data format. Your mileage may vary, and what we show here is not a guarantee of performance.
+Below are some informal benchmarks for ClickPipes for Kafka that can be used get a general idea of the baseline performance. It's important to know that many factors can impact performance, including message size, data types, and data format. Your mileage may vary, and what we show here is not a guarantee of actual performance.
 
 Benchmark details:
+
 - We used production ClickHouse Cloud services with enough resources to ensure that throughput was not bottlenecked by the insert processing on the ClickHouse side.
 - The ClickHouse Cloud service, the Kafka cluster (Confluent Cloud), and the ClickPipe were all running in the same region (`us-east-2`).
-- The ClickPipe was configured with a single replica.
-- The sample data included nested data with a mix of UUID, String, and Int datatypes.
-  - Other datatypes, such as Floats, Decimals, and DateTime types may be less performant.
-- There was no appreciable difference in performance between compressed and uncompressed data.
-
-| Replica Size | Message Size | Data Format | Throughput |
-|---------------|-----------|-------------|-----------|
-| 1vcpu/4gb     | 1.6kb    |   JSON        | 63mb/s    |
-| 1vcpu/4gb    | 1.6kb    |   AVRO        | 99mb/s    |
+- The ClickPipe was configured with a single L-sized replica (4 GiB of RAM and 1 vCPU).
+- The sample data included nested data with a mix of `UUID`, `String`, and `Int` datatypes. Other datatypes, such as `Float`, `Decimal`, and `DateTime`, may be less performant.
+- There was no appreciable difference in performance using compressed and uncompressed data.
+
+| Replica Size  | Message Size | Data Format | Throughput |
+|---------------|--------------|-------------|------------|
+| Large (L)     | 1.6kb        |   JSON      | 63mb/s     |
+| Large (L)     | 1.6kb        |   Avro      | 99mb/s     |

docs/integrations/data-ingestion/clickpipes/kafka/05_faq.md

@@ -55,6 +55,15 @@ No, the ClickPipes for Kafka is designed for reading data from Kafka topics, not
 Yes, if the brokers are part of the same quorum they can be configured together delimited with `,`.
 </details>
 
+<details>
+
+<summary>Can ClickPipes replicas be scaled?</summary>
+
+Yes, ClickPipes for streaming can be scaled both horizontally and vertically.
+Horizontal scaling adds more replicas to increase throughput, while vertical scaling increases the resources (CPU and RAM) allocated to each replica to handle more intensive workloads.
+This can be configured during ClickPipe creation, or at any other point under **Settings** -> **Advanced Settings** -> **Scaling**.
+</details>
+
 ### Upstash {#upstash}
 
 <details>

docs/integrations/data-ingestion/clickpipes/kinesis.md

@@ -161,10 +161,9 @@ If you have specific low-latency requirements, please [contact us](https://click
 
 ### Scaling {#scaling}
 
-ClickPipes for Kinesis is designed to scale horizontally. By default, we create a consumer group with one consumer.
-This can be changed with the scaling controls in the ClickPipe details view.
+ClickPipes for Kinesis is designed to scale both horizontally and vertically. By default, we create a consumer group with one consumer. This can be configured during ClickPipe creation, or at any other point under **Settings** -> **Advanced Settings** -> **Scaling**.
 
-ClickPipes provides a high-availability with an availability zone distributed architecture.
+ClickPipes provides high-availability with an availability zone distributed architecture.
 This requires scaling to at least two consumers.
 
 Regardless number of running consumers, fault tolerance is available by design.