From 0d918a90a173be850eaebdca1bb86637fefdf89e Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Fri, 23 Jan 2026 17:50:57 -0500 Subject: [PATCH] CMA 2.18.0 release note typo fix --- modules/nodes-pods-autoscaling-custom-rn-2181.adoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/modules/nodes-pods-autoscaling-custom-rn-2181.adoc b/modules/nodes-pods-autoscaling-custom-rn-2181.adoc index fdf9209757..2b45e5a7db 100644 --- a/modules/nodes-pods-autoscaling-custom-rn-2181.adoc +++ b/modules/nodes-pods-autoscaling-custom-rn-2181.adoc @@ -55,11 +55,10 @@ Fallback is now supported for triggers that use the `Value` metric type. Previou You can now configure a Kafka scaler to scale Kafka consumers by partition count on the topic. This ensures that the partitions are evenly spread across all consumers. (link:https://github.com/kedacore/keda/issues/2581[KEDA issue 2581]) - [id="nodes-pods-autoscaling-custom-rn-2181-new-log-zap_{context}"] === The Zap logger has replaced the Kubernetes logger -The Operator now use s the Zap logging library to emit logs. (link:https://github.com/kedacore/keda/issues/5732[KEDA issue 5732]) +The Operator now uses the Zap logging library to emit logs. (link:https://github.com/kedacore/keda/issues/5732[KEDA issue 5732]) [id="nodes-pods-autoscaling-custom-rn-2181-deprecated_{context}"] == Deprecated and removed features