fixing as per comments

Author: surajmb

articles/operator-nexus/TOC.yml

@@ -13,6 +13,8 @@
       href: concepts-compute.md
     - name: Storage overview
       href: concepts-storage.md
+    - name: Network Fabric overview
+      href: concepts-network-fabric.md
     - name: Nexus Kubernetes
       href: concepts-nexus-kubernetes-cluster.md
     - name: Observability

articles/operator-nexus/concepts-networkfabric.md renamed to articles/operator-nexus/concepts-network-fabric.md

@@ -10,9 +10,9 @@ ms.custom: template-concept
 ---
 
 # Azure Operator Nexus - Network Fabric
-Azure Operator Nexus offers various capabilities to manage the lifecycle and configuration of the networking required to run the Operator's infrastucture and workloads. 
+Azure Operator Nexus offers various capabilities to manage the lifecycle and configuration of the networking required to run the Operator's infrastructure and workloads. 
 
-Operator Nexus enables you to -
+Operator Nexus enables you to:
 
 * Single pane of glass to manage your on-premises networking devices and their configuration.
 * Create infrastructure and workload networks which are isolated.
@@ -25,7 +25,7 @@ Operator Nexus enables you to -
 
 :::image type="content" source="media/networking-concepts-1.png" alt-text="Screenshot of Resource Types.":::
 
-Key capabilities offered in Azure Operator Nexus Network Fabric -
+Key capabilities offered in Azure Operator Nexus Network Fabric:
 
 * **Bootstrapping and lifecycle management** - Automated bootstrapping & provisioning of network fabric resources based on network function use-cases. It provides various controls to manage network devices in operator premises via Azure APIs.
 

articles/operator-nexus/concepts-resource-types.md

@@ -34,46 +34,43 @@ You can manage the lifecycle of a Network Fabric Controller via Azure using any
 
 ### Network Fabric
 
-Network Fabric (NF) is an Operator Nexus resource is a representation of your on-premises network topology in Azure. Every Network Fabric must be associated to and controlled by a Network Fabric Controller which is deployed in the same Azure region. You can associate multiple Network Fabric resources per Network Fabric Controller, see [Nexus Limits and Quotas](./reference-limits-and-quotas.md). A single deployment of Operator's infrastructure is considered a Network Fabric intance.
+Network Fabric (NF) resource is a representation of your on-premises network topology in Azure. Every Network Fabric must be associated to and controlled by a Network Fabric Controller which is deployed in the same Azure region. You can associate multiple Network Fabric resources per Network Fabric Controller, see [Nexus Limits and Quotas](./reference-limits-and-quotas.md). A single deployment of the your infrastructure is considered a Network Fabric instance.
 
-Operator Nexus allows you to create Network Fabrics based on specific SKU types, where each SKU represents the number of network racks and compute servers in each rack deployed on-premises. You can create Network Fabric of the following SKU types -
-
-* M4-A400-A100-C16-aa for up to four compute racks and 16 servers in each rack
-* M8-A400-A100-C16-aa for up to eight compute racks and 16 servers in each rack
+Operator Nexus allows you to create Network Fabrics based on specific SKU types, where each SKU represents the number of network racks and compute servers in each rack deployed on-premises.
 
 Each Network Fabric resource can contain a collection of network racks, network devices, isolation domains for their interconnections. Once a Network Fabric is created and you've validated that your network devices are connected, then it can be Provisioned. Provisioning a Network Fabric is the process of bootstrapping the Network Fabric instance to get the management network up.
 
 You can manage the lifecycle of a Network Fabric via Azure using any of the supported interfaces - Azure CLI, REST API, etc. See [how to create and provision a Network Fabric](./howto-configure-network-fabric.md) to learn more.
 
-### Network Racks
+### Network racks
 
 Network Rack resource is a representation of your on-premises Racks from the networking perspective. The number of network racks in an Operator Nexus instance depends on the Network Fabric SKU which was chosen while creation. In a multi-rack setup, you can create up to either 4 compute racks + 1 aggregate rack or 8 compute racks + 1 aggregate rack.
 
 Each network rack consists of Network Devices which are part of that rack. For example - Customer Edge (CE) routers, Top of Rack (ToR) Switches, Management Switches, Network Packet Brokers (NPB).
 
 The Network Rack also models the connectivity to the operator's Physical Edge switches (PEs) and the ToRs on the other Racks via Network to Network Interconnect (NNI) resource.
 
-The lifecycle of Network Rack resources are tied to the Network Fabric resource. The Network Racks are automatically created when you create the Network Fabric and the number of racks depends on the SKU which was chosen. When the Network Fabric resource is deleted, all the associated Network Racks are also deleted along with it.
+The lifecycle of Network Rack resources is tied to the Network Fabric resource. The Network Racks are automatically created when you create the Network Fabric and the number of racks depends on the SKU which was chosen. When the Network Fabric resource is deleted, all the associated Network Racks are also deleted along with it.
 
-### Network Devices
+### Network devices
 
 Network Devices represent the Customer Edge (CE) routers, Top of Rack (ToR) Switches, Management Switches, Network Packet Brokers (NPB) which are deployed as part of the Network Fabric instance. Each Network Device resource is associated to a specific Network Rack where it is deployed.
 
 Each network device resource has a SKU, Role, Host Name, and Serial Number as properties, and can have multiple network interfaces associated. Network Interfaces contain the IPv4 and IPv6 addresses, physical identifier, interface type, and the associated connections. Network Interfaces also has the administrativeState property which indicates whether the interface is enabled or disabled.
 
 The lifecycle of the Network Interface depends on the Network Device and can exist as long as the parent network device resource exists. However, you can perform certain operations on a network interface resource like enable/disable the administrativeState via Azure using any of the supported interfaces - Azure CLI, REST API, etc.
 
-The lifecycle of the Network Device resources depend on the network rack resource and will exist as long as the parent Network Fabric resource exists. However, before provisioning the Network Fabric, you can perform certain operations on a network device like setting a custom hostname and updating the serial number of the device via Azure using any of the supported interfaces - Azure CLI, REST API, etc.
+The lifecycle of the Network Device resources depends on the network rack resource and will exist as long as the parent Network Fabric resource exists. However, before provisioning the Network Fabric, you can perform certain operations on a network device like setting a custom hostname and updating the serial number of the device via Azure using any of the supported interfaces - Azure CLI, REST API, etc.
 
-### Isolation Domains
+### Isolation domains
 
 Isolation Domains enable east-west or north-south connectivity across Operator Nexus instance. They provide the required network connectivity between infrastructure components and also workload components. In principle, there are two types of networks which are established by isolation domains - management network and workload or tenant network. 
 
 Management network is the private connectivity that enables communication between the Network Fabric instance which is deployed on-premises and Azure Virtual Network. You can create workload or tenant networks to enable communication between the workloads which are deployed across the Operator Nexus instance.
 
 Each isolation domain is associated to a specific Network Fabric resource and has the option to be enabled/disabled. Only when an isolation domain is enabled, it's configured on the network devices and the configuration is removed once the isolation domain is removed.
 
-Primarily, there are two types of isolation domains -
+Primarily, there are two types of isolation domains:
 
 * Layer 2 or L2 Isolation Domains
 * Layer 3 or L3 Isolation Domains
@@ -82,7 +79,7 @@ Layer 2 isolation domains enable your infrastructure and workloads communicate w
 
 Layer 3 isolation domains enable your infrastructure and workloads communicate with each other within or across racks over a Layer 3 network. Layer 3 networks enable east-west and north-south communication within and outside your Operator Nexus instance.
 
-There are two types of Layer 3 networks that you can create -
+There are two types of Layer 3 networks that you can create:
 
 * Internal Network
 * External Network
@@ -112,7 +109,7 @@ Storage Appliances represent storage arrays used for persistent data storage in
 ### Bare Metal Machine
 
 Bare Metal Machines represent the physical servers in a rack. They're lifecycle managed by the Cluster Manager.
-Bare Metal Machines are used by workloads to host Virtual Machines and Kubetnetes clusters.
+Bare Metal Machines are used by workloads to host Virtual Machines and Kubernetes clusters.
 
 ## Workload components
 
@@ -129,7 +126,7 @@ There are five Network resource types that represent a network attachment to an
 
 - **Layer 3 Network Resource**: facilitate "North-South" communication between your VMs/tenant clusters and the external network.
 
-- **Trunked Network Resource**: provides a VM or an tenant cluster access to multiple layer 3 networks and/or multiple layer 2 networks.
+- **Trunked Network Resource**: provides a VM or a tenant cluster access to multiple layer 3 networks and/or multiple layer 2 networks.
 
 ### Virtual machine
 

articles/operator-nexus/reference-limits-and-quotas.md

@@ -9,7 +9,7 @@ ms.date: 06/28/2023
 ms.custom: template-reference
 ---
 
-# Nexus Limits and Quotas
+# Azure Operator Nexus limits and quotas
 
 This document provides an overview of the resource limits that apply to the components used in the Nexus solution, encompassing the resources created within Azure cloud and in on-premises instance. It outlines the specific limitations and restrictions that operators should be aware of when deploying and managing the Nexus instance across these environments.