Michael comments

Author: jhlodin

src/current/v25.2/migrate-cockroachdb-kubernetes-helm.md

@@ -26,7 +26,7 @@ If your existing cluster was created using the {{ site.data.products.public-oper
 This migration can be completed without affecting cluster availability, and preserves existing disks so that data doesn't need to be replicated into empty volumes. The process scales down the StatefulSet by one node before adding each operator-managed pod, so the maximum cluster capacity will be reduced by one node periodically throughout the migration.
 
 {{site.data.alerts.callout_danger}}
-The {{ site.data.products.cockroachdb-operator }} uses a different port than StatefulSets for RPC services, meaning that the migration will cause temporary downtime specifically for issuing commands that use RPCs. This includes commands such as `cockroach node drain` and `cockroach node decommission`. Plan for this limited downtime until the public service is updated in Step 4 as described in this guide. 
+Commands that use RPCs (such as `cockroach node drain` and `cockroach node decommission`) will be unavailable until the public service is updated in step 4. The {{ site.data.products.cockroachdb-operator }} uses a different port than StatefulSets for RPC services, causing these commands to fail for a limited time.
 {{site.data.alerts.end}}
 
 ## Step 1. Prepare the migration helper

src/current/v25.2/monitor-cockroachdb-operator.md

@@ -254,10 +254,7 @@ metadata:
   namespace: cockroach-ns
 ~~~
 
-The above configuration overrides the [default logging configuration]({% link {{ page.version.version }}/configure-logs.md %}#default-logging-configuration) and reflects our recommended Kubernetes logging configuration:
-
-- Save debug-level logs (the `DEV` [log channel]({% link {{ page.version.version }}/logging-overview.md %}#logging-channels)) to disk for troubleshooting.
-- Send operational- and security-level logs to a [network collector]({% link {{ page.version.version }}/logging-use-cases.md %}#network-logging), in this case [Fluentd]({% link {{ page.version.version }}/configure-logs.md %}#fluentd-logging-format).
+The above configuration overrides the [default logging configuration]({% link {{ page.version.version }}/configure-logs.md %}#default-logging-configuration) and saves debug-level logs (the `DEV` [log channel]({% link {{ page.version.version }}/logging-overview.md %}#logging-channels)) to disk for troubleshooting.
 
 The ConfigMap `name` must match the `cockroachdb.crdbCluster.loggingConfigMapName` object in the values file used to [deploy the cluster]({% link {{ page.version.version }}/deploy-cockroachdb-with-cockroachdb-operator.md %}#initialize-the-cluster):