diff --git a/modules/manage/pages/kubernetes/k-decommission-brokers.adoc b/modules/manage/pages/kubernetes/k-decommission-brokers.adoc
index 09c591411..2570b29d6 100644
--- a/modules/manage/pages/kubernetes/k-decommission-brokers.adoc
+++ b/modules/manage/pages/kubernetes/k-decommission-brokers.adoc
@@ -1,12 +1,14 @@
 = Decommission Brokers in Kubernetes
-:description: Remove a broker so that it is no longer considered part of the cluster.
+:description: Remove a Redpanda broker from the cluster without risking data loss or causing instability.
 :page-context-links: [{"name": "Linux", "to": "manage:cluster-maintenance/decommission-brokers.adoc" },{"name": "Kubernetes", "to": "manage:kubernetes/k-decommission-brokers.adoc" } ]
 :tags: ["Kubernetes"]
 :page-aliases: manage:kubernetes/decommission-brokers.adoc
 :page-categories: Management
 :env-kubernetes: true
 
-When you decommission a broker, its partition replicas are reallocated across the remaining brokers and it is removed from the cluster. You may want to decommission a broker in the following circumstances:
+Decommissioning a broker is the *safe and controlled* way to remove a Redpanda broker from the cluster without risking data loss or causing instability. By decommissioning, you ensure that partition replicas are reallocated across the remaining brokers so that you can then safely shut down the broker.
+
+You may want to decommission a broker in the following situations:
 
 * You are removing a broker to decrease the size of the cluster, also known as scaling down.
 * The broker has lost its storage and you need a new broker with a new node ID (broker ID).