DOC-1459 Document new cluster scope default for Redpanda Operator 25.2

modules/ROOT/nav.adoc

@@ -66,7 +66,6 @@
 ** xref:deploy:redpanda/index.adoc[Redpanda]
 *** xref:deploy:redpanda/kubernetes/index.adoc[Kubernetes]
 **** xref:deploy:redpanda/kubernetes/k-deployment-overview.adoc[Overview]
-**** xref:deploy:redpanda/kubernetes/k-25.2-beta.adoc[Try v25.2]
 **** xref:deploy:redpanda/kubernetes/get-started-dev.adoc[Get Started]
 ***** xref:deploy:redpanda/kubernetes/aks-guide.adoc[Azure AKS]
 ***** xref:deploy:redpanda/kubernetes/eks-guide.adoc[Amazon EKS]

modules/deploy/pages/redpanda/kubernetes/k-deployment-overview.adoc

@@ -41,7 +41,7 @@ To deploy Redpanda in Kubernetes, you can choose between Helm for its simplicity
 | Multi-tenancy management
 | ✅
 | ⚠️
-| Helm requires separate releases to manage multiple clusters, making management more complex. The Redpanda Operator simplifies this through declarative custom resources.
+| Helm requires separate releases to manage multiple clusters, making management more complex. The Redpanda Operator simplifies multi-tenancy by managing clusters across different namespaces from a single operator instance.
 
 |===
 
@@ -50,7 +50,7 @@ TIP: If you are already using the Redpanda Helm chart and want to migrate to the
 [[helm-and-redpanda-operator]]
 === Redpanda Operator
 
-The Redpanda Operator is designed for production-grade Redpanda deployments, offering enhanced lifecycle management, automation, and GitOps compatibility.
+The Redpanda Operator is designed for production-grade Redpanda deployments, offering enhanced lifecycle management, automation, and GitOps compatibility. The Redpanda Operator defaults to cluster scope, enabling it to manage multiple Redpanda clusters across different namespaces from a single operator instance.
 
 The Redpanda Operator directly reconciles Redpanda resources, performing tasks such as installations, updates, and cleanup.