corrected the blocking issues

Author: sushantjrao

articles/operator-nexus/TOC.yml

@@ -193,8 +193,8 @@
           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 setup break glass access
-          href: howto-setup-break-glass-access-.md
+        - name: How to set up break glass access
+          href: howto-set-up-break-glass-access.md
         - name: How to use-break-glass-access.md
           href: howto-use-break-glass-access.md
         - name: How to enable-Micro-BFD on CE and PE devices.md

articles/operator-nexus/howto-enable-micro-bfd.md

@@ -1,6 +1,6 @@
 ---
 title: How to enable Micro-BFD on CE and PE devices
-description: Process of enabling Micro-BFD On CE and PE devices .
+description: Process of enabling Micro-BFD On CE and PE devices.
 author: sushantjrao 
 ms.author: sushrao
 ms.service: azure-operator-nexus
@@ -15,13 +15,16 @@ Micro-BFD (Bidirectional Forwarding Detection) is a lightweight protocol designe
 
 ## Prerequisites
 
-Before enabling Micro-BFD, ensure the following:
+Before enabling Micro-BFD, perform the following steps:
 
 - Both CE and PE devices are configured with the required Micro-BFD settings.
 
-- The feature flag `MicroBFDEnabled` is turned off by default. To enable it, please contact Microsoft support through a support incident.
+- The feature flag `MicroBFDEnabled` is turned off by default.
 
-- Need to [put the device in maintenance mode](.\howto-put-device-in-maintenance-mode.md) for below configuration changes.
+> [!Note]
+> Contact Microsoft support through a support incident to enable the feature flag.
+
+- It is necessary to [put the device in maintenance mode](.\howto-put-device-in-maintenance-mode.md) to apply below the configuration changes. 
 
 ## Configuration steps
 

articles/operator-nexus/howto-setup-break-glass-access-.md renamed to articles/operator-nexus/howto-set-up-break-glass-access.md

@@ -17,30 +17,30 @@ For Network Fabric environments, the current break-glass model, known as Method
 
 - **Strict access control**: Customer administrators control access through individual assignments instead of shared accounts.
 
-- **Strong authentication**: Break-glass access is managed via Microsoft Entra with Multi-Factor Authentication (MFA) eliminating local account dependencies.
+- **Strong authentication**: Break-glass access is managed via Microsoft Entra with multifactor authentication (MFA) eliminating local account dependencies.
 
 - **Enhanced security**: All access attempts are logged for audit and investigation purposes.
 
 ## FIDO2 token 
 
-In the Method D v2.0 model, break-glass users uses a FIDO2 token to create and upload a public key linked to their Entra identity. This provides secure SSH access to Fabric devices. Entra RBAC manages authorization, allowing administrators to assign appropriate access levels to users.
+In the Method D v2.0 model, break-glass users uses a FIDO2 token to create and upload a public key linked to their Entra identity. This configuration provides secure SSH access to Fabric devices. Entra Role-Based Access Control (RBAC) manages authorization, allowing administrators to assign appropriate access levels to users.
 
 For offline accessibility, usernames, public keys, and permissions are pre-provisioned on all the Network Fabric devices, allowing break-glass SSH login without requiring an active Azure connection.
 
-Each FIDO2 token serves usually as a physical USB device, offering unphishable, multi-factor authentication through user presence and PIN verification.
+Each FIDO2 token serves usually as a physical USB device, offering unphishable, multifactor authentication through user presence and PIN verification.
 
 ## Method D v2.0 setup and operations
 
 This guide is divided into two sections 
 
-1.	**Method D v2.0 infrastructure setup** - Mandatory for both existing and new NF deployments running Runtime Fabric version 4.0.0. 
+1.	**Method D v2.0 infrastructure setup** - Mandatory for both existing and new Network Fabric (NF) deployments running Runtime Fabric version 4.0.0. 
 
-2. [**Using Method D v2.0 breakglass access**](howto-use-break-glass-access.md)
+2. [**Using Method D v2.0 break glass access**](howto-use-break-glass-access.md)
 
 
 ### Method D v2.0 infrastructure setup
 
-This guide provides an overview of the infrastructure setup mandatory for both existng and new deployments which will be using NF Runtime version 4.0.0.
+This guide provides an overview of the infrastructure setup that is mandatory for both existing and new deployments using NF Runtime version 4.0.0.
 
 #### Step 1: Register NexusIdentity Resource Provider
 

articles/operator-nexus/howto-use-break-glass-access.md

@@ -107,7 +107,7 @@ Once these roles are assigned, the corresponding username and public SSH key wil
 > [!Note]
 > break glass user accounts are reconciled every 4 hours. For immediate reconciliation, open a support ticket with the network fabric support team.
 
-## 3. Break-glass access to Network Fabric device
+## Break-glass access to Network Fabric device
 
 Once permissions are granted, users can access network fabric devices with their FIDO-2 hardware token (for example, YubiKey). Follow the steps below to use break glass access.