updated

Author: sushantjrao

articles/operator-nexus/.openpublishing.redirection.operator-nexus.json

@@ -42,7 +42,7 @@
     },
     {
       "source_path": "howto-replace-a-device-in-azure-operator-nexus-network-fabric.md",
-      "redirect_url": "howto-replace-a-device-in-azure-operator-nexus-network-fabric",
+      "redirect_url": "howto-replace-network-devices",
       "redirect_document_id": false
     },
     {

articles/operator-nexus/TOC.yml

@@ -217,8 +217,6 @@
           href: howto-delete-layer-3-isolation-domains.md
         - name: Cross-subscription deployments and required RBAC for Network Fabric
           href: concepts-cross-subscription-deployments-required-rbac-for-network-fabric.md
-        - name: How to replace network devices in Azure Operator Nexus Network Fabric
-          href: howto-replace-network-devices.md
         - name: How to put a device into maintenance mode
           href: howto-put-device-in-maintenance-mode.md
         - name: How to set up break glass access

articles/operator-nexus/concepts-commit-workflow-v2.md

@@ -56,7 +56,7 @@ The Commit Workflow version supported depends on the combination of Fabric runti
 
 ### Required versions
 
-If you're unsure which Commit Workflow version applies to your setup, refer to the [Commit Workflow Version Matrix](#commit-workflow-version-matrix).
+If you're unsure which Commit Workflow version applies to your setup, refer to the [Commit workflow compatible versions](#Commit-workflow-comaptible-versions).
 
 * **Runtime version**: `5.0.1` or later is required for Commit Workflow v2.