fix links to renamed troubleshooting page

Author: robertstarling

articles/operator-nexus/TOC.yml

@@ -342,7 +342,7 @@
         - name: Troubleshoot Hardware Validation Failure
           href: troubleshoot-hardware-validation-failure.md
         - name: Troubleshoot Degraded status
-          href: troubleshoot-bmm-degraded.md
+          href: troubleshoot-bare-metal-machine-degraded.md
         - name: Troubleshoot Control Plane Quorum
           href: troubleshoot-control-plane-quorum.md
         - name: Troubleshoot Accepted Cluster Resource

articles/operator-nexus/troubleshoot-lacp-bonding.md

@@ -13,7 +13,7 @@ ms.date: 11/15/2024
 
 On physical host startup, the two Mellanox cards are bonded to a pair of Arista switches by the Link Aggregation Control Protocol (LACP). If LACP isn't properly negotiated between the server's cards and the switches, it can cause strange packet loss or load-balancing behavior. These errors might not be noticeable until a tenant workload attempts to pass traffic. They occur because of the hashing/load-balancing nature of LACP.
 
-If there's an issue with LACP bonding on a given host, an appropriate 'degraded' message is included in the 'Detailed status message' for the corresponding Bare Metal Machine (BMM) resource. For more information, see the [Troubleshoot Degraded status](./troubleshoot-bmm-degraded.md) guide.
+If there's an issue with LACP bonding on a given host, an appropriate 'degraded' message is included in the 'Detailed status message' for the corresponding Bare Metal Machine (BMM) resource. For more information, see the [Troubleshoot Degraded status](./troubleshoot-bare-metal-machine-degraded.md) guide.
 
 ## Diagnosis