diff --git a/modules/manage/pages/cluster-maintenance/cluster-balancing.adoc b/modules/manage/pages/cluster-maintenance/cluster-balancing.adoc
index 2656a3d1c..1fdc4aad4 100644
--- a/modules/manage/pages/cluster-maintenance/cluster-balancing.adoc
+++ b/modules/manage/pages/cluster-maintenance/cluster-balancing.adoc
@@ -133,7 +133,7 @@ In Redpanda, every partition replica is assigned to a CPU core on a broker. Whil
 
 Starting in this version of Redpanda, topic-aware intra-broker partition balancing allows for dynamically reassigning partitions within a broker.  Redpanda prioritizes an even distribution of a topic's partition replicas across all cores in a broker. If a broker's core count changes, when the broker starts back up, Redpanda can check partition assignments across the broker's cores and reassign partitions, so that a balanced assignment is maintained across all cores. Redpanda can also check partition assignments when partitions are added to or removed from a broker, and rebalance the remaining partitions between cores.
 
-NOTE: Decreasing the number of CPU cores in a running cluster is supported from v24.2 only, and requires that you enable `node_local_core_assignment` as described in the previous note. 
+NOTE: Decreasing the number of CPU cores in a running cluster requires that you enable the `node_local_core_assignment` feature flag.
 
 To determine when to use intra-broker partition balancing, use the public metrics for CPU usage described in the xref:manage:monitoring.adoc#cpu-usage[Monitoring] guide.