Modified to incorporated the feedback

Author: sushantjrao

articles/operator-nexus/TOC.yml

@@ -231,10 +231,10 @@
         - name: How to restrict serial port access and set timeout on terminal-server
           href: howto-restrict-serial-port-access-and-set-timeout-on-terminal-server.md
         - name: How to configure BGP prefix limit on Customer Edge (CE) devices for Azure Operator Nexus
-          href: howto-configure-bgp-prefix-limit-on-CE-devices.md
+          href: howto-configure-bgp-prefix-limit-on-ce-devices.md
         - name: BMP log streaming in Azure Operator Nexus Network Fabric 
           href: concepts-bmp-log-streaming.md
-        - name: How to enable \ disable BMP log streaming Azure Operator Nexus
+        - name: How to enable / disable BMP log streaming Azure Operator Nexus
           href: howto-enable-log-streaming.md
     - name: Cluster
       expanded: false

articles/operator-nexus/concepts-bmp-log-streaming.md

@@ -1,6 +1,6 @@
 ---
 title: BMP log streaming in Azure Operator Nexus Network Fabric 
-description: An overview of BGP Monitoring Protocol (BMP), its importance, and key components for effective log monitoring..
+description: An overview of BGP Monitoring Protocol (BMP), its importance, and key components for effective log monitoring.
 author: sushantjrao
 ms.author: sushrao
 ms.service: azure-operator-nexus
@@ -86,4 +86,4 @@ Nexus NF shall not support excluding the monitoring of peer-address of neighbor
 Nexus shall support a maximum of four Network Monitors (BMP Stations).
 
 ## Next steps
-[How to enable \ disable BMP log streaming](./howto-enable-log-streaming.md)
+[How to enable / disable BMP log streaming](./howto-enable-log-streaming.md)

articles/operator-nexus/howto-append-custom-suffix-to-interface-descriptions.md

@@ -31,7 +31,7 @@ az networkfabric interface show -g "example-rg" \
   --resource-name "example-interface" --query description
 ```
 
-### Parameter Details  
+#### Parameter details  
 
 | Parameter                     | Short Form | Description |
 |--------------------------------|-----------|-------------|
@@ -54,7 +54,7 @@ az networkfabric interface update --additional-description "example-description"
   --resource-name "example-interface"
 ```
 
-### Parameter Details  
+#### Parameter details  
 
 | Parameter                | Description                                      | Constraints |
 |--------------------------|--------------------------------------------------|-------------|
@@ -70,7 +70,7 @@ After updating the description, apply the changes to the Fabric:
 ```Azure CLI
 az networkfabric fabric commit-configuration --resource-group "example-rg" --resource-name "example-fabric"
 ```
-Parameter Details:
+#### Parameter details
 
 | Parameter            | Short Form | Description |
 |----------------------|-----------|-------------|
@@ -101,7 +101,7 @@ az networkfabric interface update --additional-description "example-description"
   --resource-name "example-interface"
 ```
 
-### Parameter Details  
+#### Parameter details  
 
 | Parameter                | Description                                      | Constraints |
 |--------------------------|--------------------------------------------------|-------------|
@@ -118,7 +118,7 @@ After removing the suffix, apply the changes to the Fabric:
 az networkfabric fabric commit-configuration --resource-group "example-rg" --resource-name "example-fabric"
 ```
 
-Parameter Details:
+#### Parameter details
 
 | Parameter            | Short Form | Description |
 |----------------------|-----------|-------------|
@@ -133,22 +133,22 @@ AR-CE2(Fab3-AR-CE2):Et1/1 to CR1-TOR1(Fab3-CP1-TOR1)-Port23
 
 ## Network interface updates
 
-Updates to network interface of a network device
+Updates have been made to the network interface of the network device to standardize the interface description. Additionally, these updates now link the interface to the ARM resource ID of the connected interface for better management and tracking.
 
-### Standardized Interface Descriptions
+### Standardized interface descriptions
 
 Interface descriptions follow a consistent format:
 
 Source Device to Destination Device (including hostname and interface name).
 
-### Example:
+### Example
 AR-CE2 (Fab3-AR-CE2): Et1/1 to CR1-TOR1 (Fab3-CP1-TOR1) - Port23
 
 ### connectedTo property
 
 The `connectedTo` property returns the ARM resource ID of the connected interface, where available.
 
-### Comparison of Old and New Values:
+### Comparison of old and new values
 
 | Example | Previous Value | New Value |
 |---------|---------------|-----------|
@@ -166,4 +166,4 @@ All the above features are available for the following interface types:
 - **NPB Device**  
 
 > [!Note]  
->For non-NF managed devices for e.g., PE \ Storage Device the `connectedTo` property will continue to reflect value as a `string` with no active link.
+> For non-NF managed devices, such as PE \ Storage Device, the `connectedTo` property will continue to reflect value as a `string` with no active link.

articles/operator-nexus/howto-configure-bgp-prefix-limit-on-CE-devices.md

@@ -3,7 +3,7 @@ title: How to configure BGP prefix limit on Customer Edge (CE) devices for Azure
 description: Learn the process for configuring BGP prefix limit on Customer Edge (CE) devices for Azure Operator Nexus
 author: sushantjrao 
 ms.author: sushrao
-ms.date: 06/11/2023
+ms.date: 04/02/2025
 ms.topic: how-to
 ms.service: azure-operator-nexus
 ms.custom: template-how-to, devx-track-azurecli
@@ -34,11 +34,11 @@ To configure **BGP Prefix Limit** on **Customer Edge (CE)** devices for **Azure
 
 ### Prerequisites
 
-1. Ensure that the **Network Fabric (NF)** is upgraded to the supported version or later.
+- Ensure that the **Network Fabric (NF)** is upgraded to the supported version or later.
 
-2. Verify that your **Customer Edge (CE)** devices are running on compatible software.
+- Verify that your **Customer Edge (CE)** devices are running on compatible software.
 
-3. Check that the **peer groups** for both **IPv4** and **IPv6** address-families are properly set up for internal networks.
+- Check that the **peer groups** for both **IPv4** and **IPv6** address-families are properly set up for internal networks.
 
 ### Steps to configure BGP prefix limits
 
@@ -139,25 +139,25 @@ This configuration generates a warning once the prefix count reaches a certain p
 
 You can use Azure CLI commands to apply the BGP prefix limits to the external network configuration for Nexus.
 
-1. **With Automatic Restart**:
+- **With Automatic Restart**:
 
    ```bash
    az networkfabric externalnetwork create --resource-group <resource-group> --fabric-name <fabric-name> --network-name <network-name> --prefix-limits '{"maximumRoutes": 5000, "threshold": 80, "idleTimeExpiry": 100}'
    ```
 
-2. **Without Automatic Restart**:
+- **Without Automatic Restart**:
 
    ```bash
    az networkfabric externalnetwork create --resource-group <resource-group> --fabric-name <fabric-name> --network-name <network-name> --prefix-limits '{"maximumRoutes": 5000, "threshold": 80}'
    ```
 
-3. **Hard-Limit Drop BGP Sessions**:
+- **Hard-Limit Drop BGP Sessions**:
 
    ```bash
    az networkfabric externalnetwork create --resource-group <resource-group> --fabric-name <fabric-name> --network-name <network-name> --prefix-limits '{"maximumRoutes": 5000}'
    ```
 
-4. **Hard-Limit Warning Only**:
+- **Hard-Limit Warning Only**:
 
    ```bash
    az networkfabric externalnetwork create --resource-group <resource-group> --fabric-name <fabric-name> --network-name <network-name> --prefix-limits '{"maximumRoutes": 8000, "threshold": 75, "warning-only": true}'
@@ -181,15 +181,15 @@ Look for the session states and the number of prefixes advertised by each peer.
 
 ## Handling BGP Prefix Limits for Different Networks
 
-### Internal network:
+### Internal network
 
 The platform supports Layer 3 Isolation Domain (L3IsolationDomain) for tenant workloads. It performs device programming on Nexus instances and Arista devices with peer groups for both IPv4 and IPv6 address families.
 
-### External network Option B (PE):
+### External network Option B (PE)
 
 For external network configuration, only the **hard-limit warning-only** option is supported. Nexus supports this configuration via the ARM API under the **NNI optionBlayer3Configuration** with the `maximumRoutes` parameter.
 
-### NNI Option A:
+### NNI Option A
 
 For NNI Option A, only a single peer group is allowed. IPv4 over IPv6 and vice versa aren't supported. Warning-only mode is available for handling prefix limits.
 

articles/operator-nexus/howto-enable-log-streaming.md

@@ -1,6 +1,6 @@
 ---
-title: How to enable \ disable BMP log streaming Azure Operator Nexus
-description: Instructions on enabling \ disabling BMP log streaming various Network Fabric resources.
+title: How to enable / disable BMP log streaming Azure Operator Nexus
+description: Instructions on enabling / disabling BMP log streaming various Network Fabric resources.
 ms.service: azure-operator-nexus
 ms.custom: template-how-to, devx-track-azurecli
 ms.topic: how-to
@@ -11,7 +11,7 @@ ms.author: sushrao
 
 # BMP log streaming
 
-This guide provides you with instructions on enabling \ disabling BMP log streaming various Network Fabric resources.. 
+This guide provides you with instructions on enabling \ disabling BMP log streaming various Network Fabric resources.
 
 ## Enabling BMP log streaming for the new deployment
 
@@ -22,21 +22,19 @@ This guide provides you with instructions on enabling \ disabling BMP log stream
 - **Create NNI with BMP configuration:** Create a Network-to-Network Interface (NNI) by associating it with the NF Resource ID. 
 
 > [!Note]
-> Refer to the below detailed ARM API payload guide for more information
+> Refer to the below detailed Azure Resource Manager (ARM) API payload guide for more information.
 
 - **Provision Network Fabric:** Provision the Network Fabric to apply the configurations and make the network operational.
 
 - **Generate BMP stations configuration** The Nexus NF generates the BMP stations configuration on the Customer Edge (CE) devices only.
 
 ## Enabling BMP log streaming for the existing deployment
 
-This case involves enabling BMP log streaming on NF, which is already deployed using the supported NF Version. Since this approach is based on an ARM API user-driven input, the supported NF Version also supports BMP Log Streaming through the NF Patch Update workflow.
+This case involves enabling BMP log streaming on NF, which is already deployed using the supported NF Version. Since this approach is based on an Azure Resource Manager (ARM) API user-driven input, the supported NF Version also supports BMP Log Streaming through the NF Patch Update workflow.
 
 - **Create Network Fabric resource:** Start by creating the Network Fabric (NF) resource using the latest supported version. If the NF is outdated, upgrade it to the supported version.
 
-- **Create Network Monitor resource:**
-
-To ensure proper monitoring, create a Network Monitor resource and link the Scope ID to the NF Resource ID.
+- **Create Network Monitor resource:** To ensure proper monitoring, create a Network Monitor resource and link the Scope ID to the NF Resource ID.
 
 - **Perform Patch on NNI:** Update the Network-to-Network Interface (NNI) by applying a patch. Select `bmpConfiguration` under `OptionBLayerConfiguration` and set `configurationState` to "Enabled" for BMP logging of the NNI peer-group neighbor address.
 

articles/operator-nexus/howto-reboot-network-device.md

@@ -148,7 +148,7 @@ az networkfabric device reboot --network-device-name <DeviceName> --resource-gro
 ```
 
 >[!Note] 
-> After an ungraceful reboot into ZTP mode, the device must be manually placed into maintenance mode. This functionality will be automated in a future release. 
+> After an ungraceful reboot into ZTP mode, the device must be manually placed into maintenance mode.
 
 >[!Note]
 > Rebooting into ZTP mode does not preserve the read-write (RW) configuration. The device will boot in ZTP mode, ready for bootstrapping via the Terminal Server.