Delete the duplicate monitoring topic for K8s Shadowing (#1526)

Co-authored-by: Michele Cyran <[email protected]>

Author: JakeSCahill

modules/ROOT/nav.adoc

@@ -138,7 +138,7 @@
 *** xref:manage:kubernetes/k-remote-read-replicas.adoc[Remote Read Replicas]
 *** xref:manage:kubernetes/shadowing/index.adoc[Shadowing]
 **** xref:manage:kubernetes/shadowing/k-shadow-linking.adoc[Configure Shadowing]
-**** xref:manage:kubernetes/monitoring/k-monitor-shadowing.adoc[Monitor]
+**** xref:manage:kubernetes/shadowing/k-monitor-shadowing.adoc[Monitor]
 **** xref:manage:kubernetes/shadowing/k-failover-runbook.adoc[Failover Runbook]
 *** xref:manage:kubernetes/k-manage-resources.adoc[Manage Pod Resources]
 *** xref:manage:kubernetes/k-scale-redpanda.adoc[Scale]

modules/get-started/pages/release-notes/operator.adoc

@@ -22,4 +22,4 @@ Redpanda Operator v25.3.x introduces the ShadowLink custom resource for managing
 * **Status monitoring**: View shadow link health and replication status directly from Kubernetes.
 * **Integrated failover**: Delete the ShadowLink resource to fail over all topics.
 
-See xref:manage:kubernetes/shadowing/k-shadow-linking.adoc[Shadow Linking in Kubernetes] for setup and xref:manage:kubernetes/monitoring/k-monitor-shadowing.adoc[monitoring] documentation.
+See xref:manage:kubernetes/shadowing/k-shadow-linking.adoc[Shadow Linking in Kubernetes] for setup and xref:manage:kubernetes/shadowing/k-monitor-shadowing.adoc[monitoring] documentation.

modules/manage/pages/disaster-recovery/shadowing/monitor.adoc

@@ -14,7 +14,7 @@ endif::[]
 Monitor your xref:manage:disaster-recovery/shadowing/setup.adoc[shadow links] to ensure proper replication performance and understand your disaster recovery readiness. Use `rpk` commands, metrics, and status information to track shadow link health and troubleshoot issues.
 
 ifndef::env-cloud[]
-NOTE: If you're running Redpanda in Kubernetes, see xref:manage:kubernetes/monitoring/k-monitor-shadowing.adoc[] for Kubernetes-specific monitoring procedures.
+NOTE: If you're running Redpanda in Kubernetes, see xref:manage:kubernetes/shadowing/k-monitor-shadowing.adoc[].
 endif::[]
 
 include::manage:partial$shadowing/emergency-shadowing-callout.adoc[]

modules/manage/pages/kubernetes/monitoring/k-monitor-redpanda.adoc

@@ -17,6 +17,6 @@ include::manage:partial$monitor-health.adoc[]
 
 include::shared:partial$suggested-reading.adoc[]
 
-* xref:manage:kubernetes/monitoring/k-monitor-shadowing.adoc[Monitor Shadow Links]
+* xref:manage:kubernetes/shadowing/k-monitor-shadowing.adoc[Monitor Shadow Links]
 
 * https://killercoda.com/redpanda/scenario/redpanda-k8s-day2[Monitoring Redpanda in Kubernetes(Day 2 Ops)^]

modules/manage/pages/kubernetes/monitoring/k-monitor-shadowing.adoc

@@ -33,7 +33,7 @@ NAME   SYNCED
 link   True
 ----
 
-A healthy shadow link shows `True` for SYNCED. If SYNCED is `False`, use `kubectl describe` to investigate the issue.
+The synced status is `True` for a healthy shadow link. If the synced status is `False`, use `kubectl describe` to investigate the issue.
 
 To view detailed shadow link status and configuration:
 
@@ -147,9 +147,9 @@ Name: inventory, State: ACTIVE
 
 Key indicators:
 
-* **STATE: ACTIVE**: Shadow link is replicating
-* **Tasks: ACTIVE**: All replication tasks are running
-* **LAG**: Message count difference between source and shadow (lower is better)
+* **State: active**: Shadow link is replicating
+* **Tasks: active**: All replication tasks are running
+* **Lag**: Message count difference between source and shadow (lower is better)
 
 For troubleshooting specific issues, you can use command options to show individual status sections. See xref:reference:rpk/rpk-shadow/rpk-shadow-status.adoc[`rpk shadow status`] for available status options.
 --