input from Camilo + fix typo

Author: micheleRP

modules/manage/pages/cluster-maintenance/manage-throughput.adoc

@@ -21,6 +21,10 @@ NOTE: As of v24.2, Redpanda enforces all throughput limits per broker, including
 
 Throughput limits are enforced by applying backpressure to clients. When a connection is in breach of the throughput limit, the throttler advises the client about the delay (throttle time) that would bring the rate back to the allowed level. Redpanda starts by adding a `throttle_time_ms` field to responses. If that isn't honored, delays are inserted on the connection's next read operation. 
 
+ifdef::env-cloud[]
+In Redpanda Cloud, the throttling delay is set to 30 seconds.
+endif::[]
+
 ifndef::env-cloud[]
 The throttling delay may not exceed the limit set by xref:reference:tunable-properties.adoc#max_kafka_throttle_delay_ms[`max_kafka_throttle_delay_ms`].
 endif::[]
@@ -101,7 +105,7 @@ endif::[]
 === Individual client throughput limit
 
 ifdef::env-cloud[]
-NOTE: The following sections show how to manage throughput with `rpk`. You can also manage throughput with the link:https://docs.redpanda.com/api/doc/cloud-dataplane/operation/operation-quotaservice_listquotas[Redpanda Cloud Data Plane API]
+NOTE: The following sections show how to manage throughput with `rpk`. You can also manage throughput with the link:https://docs.redpanda.com/api/doc/cloud-dataplane/operation/operation-quotaservice_listquotas[Redpanda Cloud Data Plane API].
 endif::[]
 
 To view current throughput quotas set through the Kafka API, run xref:reference:rpk/rpk-cluster/rpk-cluster-quotas-describe.adoc[`rpk cluster quotas describe`].