fix(kafka): add info

Author: RoRoJ

pages/clusters-for-kafka/faq.mdx

@@ -18,6 +18,10 @@ Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway.
 
 Clusters for Apache Kafka® is Scaleway's product to provide a secure, fully-managed infrastructure for your Apache Kafka® deployments. With our clusters, you can create data pipelines and event-driven architectures that run natively on Apache Kafka®, without having to manage the underlying infrastructure. This product is currently in Private Beta.
 
+### How do I use my cluster, and how can I connect to it?
+
+To use your cluster, you first [connect](/clusters-for-kafka/how-to/connect-to-cluster/) via the Kafka CLI or any supported programming language. The connection is secured, and requires the appropriate credentials, certificate, and endpoint provided by Scaleway. All configuration is done through a Kafka client, allowing you to manage topics, producers, and consumers easily. This flexibility ensures seamless integration with your applications and workflows.
+
 ### What limitations apply during the Private Beta?
 
 Private Beta is aimed at providing an early version of a future product, to allow users to test and validate it during its development. The following limitations apply to Clusters for Apache Kafka® in its current Private Beta phase:
@@ -33,6 +37,20 @@ Private Beta is aimed at providing an early version of a future product, to allo
 
 We aim to improve and develop the product based on feedback received during the beta stage.
 
+### Is Scaleway's Clusters for Apache Kafka® based on the open-source Kafka framework? 
+
+Yes, Scaleway's Clusters for Apache Kafka is built on the open-source Apache Kafka framework. We use the Kafka API to ensure compatibility and leverage the robust features of the open-source ecosystem. 
+
+## How is Apache Kafka® different to RabbitMQ and NATS?
+
+Apache Kafka, RabbitMQ, and NATS are all messaging systems but serve different purposes and have distinct architectures. 
+
+- Apache Kafka is designed for high-throughput, real-time data streaming, and is topic-based, using the pull model. It can process large amounts of data in real-time with high concurrency and fault tolerance, and is ideal for stream processing, event sourcing, and big data applications.
+- RabbitMQ is a versatile message broker that supports multiple protocols, and offers strong support for message delivery guarantees and reliability. It uses the push model, and is well-suited for traditional message queuing and task distribution. 
+- [NATS](/nats/) is a lightweight, high-performance subject-based messaging system focused on speed and simplicity, making it great for microservices. 
+
+Each system has its own strengths and is suited to different use cases depending on the requirements of the application.
+
 ## Billing
 
 ### How am I billed for Clusters for Apache Kafka®?

pages/clusters-for-kafka/how-to/connect-to-cluster.mdx

@@ -34,24 +34,15 @@ All clients that want to connect to your cluster must:
 
 3. In the **Connectivity** panel, click **Download** next to the TLS certificate.
 
-The TLS certificate is downloaded to your local device. If using Java, import it into a truststore and configure your `client.properties` appropriately. For other types of client (e.g. Python, Go, CLI), you may be able to use the certificate directly by setting its location in your Kafka consumer configuration code (e.g. `'ssl.ca.location': '/path/to/ca.crt'`).
+The TLS certificate in `.pem` format is downloaded to your local device. If using Java, import it into a truststore and configure your `client.properties` appropriately. For other types of client (e.g. Python, Go, CLI), you may be able to use the certificate directly by setting its location in your Kafka consumer configuration code.
 
-TODO CHECK:
-- Check all of the info above
-- Add more info to help users with whatever else is likely to be problematic 
-- Server side TLS only? (no client cert needed?)
-- What CA is used? Is it well known or private? Is the TLS cert in crt or pem format?
+<Message type="note">
+TLS is server-side only, and no client certificate is required.
+</Message>
 
 ## How to ensure clients have network access
 
-Any clients wanting to connect to the cluster must either be attached to a Private Network in the same VPC as the cluster, or connect via a Public Gateway in the VPC.
-
-TODO set up static NAT to map ports/IP address?
-
-See the following pages for help:
-- [How to attach a resource to a Private Network](/vpc/how-to/attach-resources-to-pn/)
-- [How to create a Public Gateway](/public-gateways/how-to/create-a-public-gateway/)
-- [Getting the most from Private Networks](/vpc/reference-content/getting-most-private-networks/)
+Any clients wanting to connect to the cluster must be [attached to a Private Network](/vpc/how-to/attach-resources-to-pn/) in the same VPC as the cluster. 
 
 ## How to access the username and password
 

pages/clusters-for-kafka/how-to/manage-cluster.mdx

@@ -14,7 +14,7 @@ Clusters for Apache Kafka® is currently in [Private Beta](https://www.scaleway.
 
 After creating your cluster, you can renew its TLS certificate, change the attached Private Network, and change its password.
 
-Other management actions, such as creating topics and events, and configuring partitions and replication factors, must be carried out via TODO HOW.
+Other management actions for internally configuring your cluster, such as creating topics and events, and configuring partitions and replication factors, can be carried out via a client library or Kafka CLI.
 
 <Requirements />
 

pages/clusters-for-kafka/quickstart.mdx

@@ -74,7 +74,7 @@ Configuration actions that cannot currently be carried out via the Scaleway cons
 - Configuring cluster parameters, such as replication factors, retention policies, and partitions
 - Integrating clients and consumers
 
-These actions can be done via TODO HOW?
+All such actions for internally configuring your cluster can be carried out via a client library or Kafka CLI.
 
 ## How to delete a cluster