Fix minor wording issue in Kafka capabilities guide

Author: thild42

pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.de-de.md

@@ -1,20 +1,20 @@
 ---
 title: Kafka - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Kafka
+excerpt: Discover the capabilities and limitations of Public Cloud Analytics for Kafka
 updated: 2025-08-04
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Kafka offer.
+This page provides the technical capabilities and limitations of the Public Cloud Analytics for Kafka offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
 ## Capabilities and limitations
 
 ### Supported regions and multi-AZ
 
-The Public Cloud Databases offer is available in the following regions:
+The Public Cloud Analytics offer is available in the following regions:
 
 - `BHS` (Beauharnois, Canada)
 - `DE` (Frankfurt, Germany)
@@ -27,7 +27,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 ### Kafka versions
 
-The Public Cloud Databases offer supports the following Kafka version:
+The Public Cloud Analytics offer supports the following Kafka version:
 
 - Kafka 3.8
 
@@ -55,9 +55,6 @@ Here is an overview of the various plans' capabilities:
 
 Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
 
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
 #### Nodes and replicas
 
 - **Business/Production**: the cluster is delivered with 3 nodes by default.
@@ -84,7 +81,7 @@ The type of storage available may vary according to the region your cluster live
 
 Also, the performance characteristics of the various storage offerings may vary depending on e.g. the storage size your cluster uses: *High Speed* may offer better iops than *High Speed Gen2* for some disk sizes. See the [Block Storage page](/links/public-cloud/block-storage) for more information about those performance characteristics.
 
-Public Cloud Databases will select the most efficient disk type for your cluster depending on your cluster parameters.
+Public Cloud Analytics will select the most efficient disk type for your cluster depending on your cluster parameters.
 
 #### Effective storage
 
@@ -108,14 +105,14 @@ Public as well as private networking (vRack) can be used for all the offers.
 
 Ingress and Egress traffic are included in the service plans and unmetered.
 
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
+The analytics service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
 
 ##### Private network considerations
 
 Here are some considerations to take into account when using private network:
 
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
+- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Analytics services first.
+- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Analytics service. The customer is responsible for any other custom network setup.
 - Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
 - OpenStack subnets routes announcement will not be applied to your services.
 - You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
@@ -126,7 +123,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Kafka depends on the available total memory on the node.
+The number of simultaneous connections in Public Cloud Analytics for Kafka depends on the available total memory on the node.
 We allow approximately 100 connections per 4 GB of RAM memory, capped to a maximum of 1000 active connections.
 
 So for example on a server with 7 GB memory, you will get approximately 200 connections, and with 15 GB memory you will get 400 connections.
@@ -154,7 +151,7 @@ Logs and metrics are available through the Control Panel and the API. Additional
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
 
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
+Please note that if the analytics service is deleted, logs and metrics are also automatically deleted.
 
 #### Users and roles
 
@@ -182,4 +179,4 @@ We would love to help answer questions and appreciate any feedback you may have.
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
 
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
+Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our analytics service!

pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-asia.md

@@ -1,20 +1,20 @@
 ---
 title: Kafka - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Kafka
+excerpt: Discover the capabilities and limitations of Public Cloud Analytics for Kafka
 updated: 2025-08-04
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Kafka offer.
+This page provides the technical capabilities and limitations of the Public Cloud Analytics for Kafka offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
 ## Capabilities and limitations
 
 ### Supported regions and multi-AZ
 
-The Public Cloud Databases offer is available in the following regions:
+The Public Cloud Analytics offer is available in the following regions:
 
 - `BHS` (Beauharnois, Canada)
 - `DE` (Frankfurt, Germany)
@@ -27,7 +27,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 ### Kafka versions
 
-The Public Cloud Databases offer supports the following Kafka version:
+The Public Cloud Analytics offer supports the following Kafka version:
 
 - Kafka 3.8
 
@@ -55,9 +55,6 @@ Here is an overview of the various plans' capabilities:
 
 Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
 
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
 #### Nodes and replicas
 
 - **Business/Production**: the cluster is delivered with 3 nodes by default.
@@ -84,7 +81,7 @@ The type of storage available may vary according to the region your cluster live
 
 Also, the performance characteristics of the various storage offerings may vary depending on e.g. the storage size your cluster uses: *High Speed* may offer better iops than *High Speed Gen2* for some disk sizes. See the [Block Storage page](/links/public-cloud/block-storage) for more information about those performance characteristics.
 
-Public Cloud Databases will select the most efficient disk type for your cluster depending on your cluster parameters.
+Public Cloud Analytics will select the most efficient disk type for your cluster depending on your cluster parameters.
 
 #### Effective storage
 
@@ -108,14 +105,14 @@ Public as well as private networking (vRack) can be used for all the offers.
 
 Ingress and Egress traffic are included in the service plans and unmetered.
 
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
+The analytics service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
 
 ##### Private network considerations
 
 Here are some considerations to take into account when using private network:
 
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
+- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Analytics services first.
+- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Analytics service. The customer is responsible for any other custom network setup.
 - Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
 - OpenStack subnets routes announcement will not be applied to your services.
 - You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
@@ -126,7 +123,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Kafka depends on the available total memory on the node.
+The number of simultaneous connections in Public Cloud Analytics for Kafka depends on the available total memory on the node.
 We allow approximately 100 connections per 4 GB of RAM memory, capped to a maximum of 1000 active connections.
 
 So for example on a server with 7 GB memory, you will get approximately 200 connections, and with 15 GB memory you will get 400 connections.
@@ -154,7 +151,7 @@ Logs and metrics are available through the Control Panel and the API. Additional
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
 
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
+Please note that if the analytics service is deleted, logs and metrics are also automatically deleted.
 
 #### Users and roles
 
@@ -182,4 +179,4 @@ We would love to help answer questions and appreciate any feedback you may have.
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
 
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
+Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our analytics service!

pages/public_cloud/public_cloud_databases/kafka_01_capabilities/guide.en-au.md

@@ -1,20 +1,20 @@
 ---
 title: Kafka - Capabilities and Limitations
-excerpt: Discover the capabilities and limitations of Public Cloud Databases for Kafka
+excerpt: Discover the capabilities and limitations of Public Cloud Analytics for Kafka
 updated: 2025-08-04
 ---
 
 ## Objective
 
-This page provides the technical capabilities and limitations of the Public Cloud Databases for Kafka offer.
+This page provides the technical capabilities and limitations of the Public Cloud Analytics for Kafka offer.
 
 We continuously improve our offers. You can follow and submit ideas to add to our roadmap at <https://github.com/orgs/ovh/projects/16/views/5>.
 
 ## Capabilities and limitations
 
 ### Supported regions and multi-AZ
 
-The Public Cloud Databases offer is available in the following regions:
+The Public Cloud Analytics offer is available in the following regions:
 
 - `BHS` (Beauharnois, Canada)
 - `DE` (Frankfurt, Germany)
@@ -27,7 +27,7 @@ The Public Cloud Databases offer is available in the following regions:
 
 ### Kafka versions
 
-The Public Cloud Databases offer supports the following Kafka version:
+The Public Cloud Analytics offer supports the following Kafka version:
 
 - Kafka 3.8
 
@@ -55,9 +55,6 @@ Here is an overview of the various plans' capabilities:
 
 Your choice of plan affects the number of nodes your cluster can run, the SLA, and a few other features such as read replicas or backup retention.
 
-> [!primary]
-> Be aware that you will be able to upgrade your plan but you won't be able to downgrade it afterwards.
-
 #### Nodes and replicas
 
 - **Business/Production**: the cluster is delivered with 3 nodes by default.
@@ -84,7 +81,7 @@ The type of storage available may vary according to the region your cluster live
 
 Also, the performance characteristics of the various storage offerings may vary depending on e.g. the storage size your cluster uses: *High Speed* may offer better iops than *High Speed Gen2* for some disk sizes. See the [Block Storage page](/links/public-cloud/block-storage) for more information about those performance characteristics.
 
-Public Cloud Databases will select the most efficient disk type for your cluster depending on your cluster parameters.
+Public Cloud Analytics will select the most efficient disk type for your cluster depending on your cluster parameters.
 
 #### Effective storage
 
@@ -108,14 +105,14 @@ Public as well as private networking (vRack) can be used for all the offers.
 
 Ingress and Egress traffic are included in the service plans and unmetered.
 
-The database service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
+The analytics service's IP address is subject to change periodically. Thus, it is advised not to rely on these IPs for any configuration, such as connection or egress policy. Instead, utilize the provided DNS record and implement CIDR-based egress policies for more robust and flexible network management.
 
 ##### Private network considerations
 
 Here are some considerations to take into account when using private network:
 
-- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Databases services first.
-- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Database service. The customer is responsible for any other custom network setup.
+- Network ports are created in the private network of your choice. Thus, further operations on that network might be restricted - e.g. you won’t be able to delete the network if you didn’t stop the Public Cloud Analytics services first.
+- When connecting from an outside subnet, the Openstack IP gateway must be enabled in the subnet used for the Analytics service. The customer is responsible for any other custom network setup.
 - Subnet sizing should include considerations for service nodes, other co-located services within the same subnet, and an allocation of additional available IP addresses for maintenance purposes. Failure to adequately size subnets could result in operational challenges and the malfunctioning of services.
 - OpenStack subnets routes announcement will not be applied to your services.
 - You can only create private network services if you are the original owner of the network. You can not create private network services on a shared network.
@@ -126,7 +123,7 @@ Once your service is up and running, you will be able to specify IP addresses (o
 
 #### Maximum simultaneous connections
 
-The number of simultaneous connections in Public Cloud Databases for Kafka depends on the available total memory on the node.
+The number of simultaneous connections in Public Cloud Analytics for Kafka depends on the available total memory on the node.
 We allow approximately 100 connections per 4 GB of RAM memory, capped to a maximum of 1000 active connections.
 
 So for example on a server with 7 GB memory, you will get approximately 200 connections, and with 15 GB memory you will get 400 connections.
@@ -154,7 +151,7 @@ Logs and metrics are available through the Control Panel and the API. Additional
 - **Logs retention**: 1000 lines of logs
 - **Metrics retention**: 1 calendar month
 
-Please note that if the database instance is deleted, logs and metrics are also automatically deleted.
+Please note that if the analytics service is deleted, logs and metrics are also automatically deleted.
 
 #### Users and roles
 
@@ -182,4 +179,4 @@ We would love to help answer questions and appreciate any feedback you may have.
 
 If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
 
-Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our databases service!
+Are you on Discord? Connect to our channel at <https://discord.gg/ovhcloud> and interact directly with the team that builds our analytics service!