Merge pull request #229369 from jaredr80/NexusUpdates-0302

Nexus updates 0302

Author: v-dirichards

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

@@ -20,22 +20,21 @@ Figure: Resource model
 
 ## Platform components
 
-Your Operator Nexus Cluster (or simply instance) platform components include the infrastructure resources and the platform software resources used to manage these infrastructure resources.
+The Operator Nexus Cluster (or Instance) platform components include the infrastructure and the platform components used to manage these infrastructure resources.
 
-### Network fabric controller
+### Network Fabric controller
 
 The Network fabric Controller (NFC) is a resource that automates the life cycle management of all network devices deployed in an Operator Nexus instance.
-The NFC resource is created in the Resource group specified by you in your Azure subscription.
 NFC is hosted in a [Microsoft Azure Virtual Network](/azure/virtual-network/virtual-networks-overview) in an Azure region.
 The region should be connected to your on-premises network via [Microsoft Azure ExpressRoute](/azure/expressroute/expressroute-introduction).
-An NFC can manage the network fabric of many (subject to limits) Operator Nexus on-premises instances.
+An NFC can manage the network fabric of many (subject to limits) Operator Nexus instances.
 
 ### Network fabric
 
 The Network fabric resource models a collection of network devices, compute servers, and storage appliances, and their interconnections. The network fabric resource also includes the networking required for your Network Functions and workloads. Each Operator Nexus instance has one Network fabric.
 
 The Network fabric Controller (NFC) performs the lifecycle management of the network fabric.
-It configures and bootstraps the network fabric resources. 
+It configures and bootstraps the network fabric resources.
 
 ### Cluster manager
 

articles/operator-nexus/includes/create-l2-isolation-domain.md

@@ -1,8 +1,8 @@
 ---
 title: "Azure Operator Nexus: Creation of L2 isolation-domain"
 description: Learn how create L2 isolation-domain.
-author: jwheeler60 #Required; your GitHub user alias, with correct capitalization.
-ms.author: johnwheeler #Required; microsoft alias of author; optional team alias.
+author: jaredr80 #Required; your GitHub user alias, with correct capitalization.
+ms.author: jaredro #Required; microsoft alias of author; optional team alias.
 ms.service: azure #Required;
 ms.topic: include #Required; leave this attribute/value as-is.
 ms.date: 01/26/2023 #Required; mm/dd/yyyy format.

articles/operator-nexus/includes/enable-l2-isolation-domain.md

@@ -1,8 +1,8 @@
 ---
 title: "Azure Operator Nexus: Creation of L2 isolation-domain"
 description: Learn how create L2 isolation-domain.
-author: jwheeler60 #Required; your GitHub user alias, with correct capitalization.
-ms.author: johnwheeler #Required; microsoft alias of author; optional team alias.
+author: jaredr80 #Required; your GitHub user alias, with correct capitalization.
+ms.author: jaredro #Required; microsoft alias of author; optional team alias.
 ms.service: azure #Required;
 ms.topic: include #Required; leave this attribute/value as-is.
 ms.date: 01/26/2023 #Required; mm/dd/yyyy format.

articles/operator-nexus/includes/l2-isolation-domain.md

@@ -1,14 +1,14 @@
 ---
-title: "Azure Operator Nexus: Creation of L2 isolation-domain"
-description: Learn how create L2 isolation-domain.
-author: jwheeler60 #Required; your GitHub user alias, with correct capitalization.
-ms.author: johnwheeler #Required; microsoft alias of author; optional team alias.
+title: "Azure Operator Nexus: Creation of L2 isolation domain"
+description: Learn how create L2 isolation domain.
+author: jaredr80 #Required; your GitHub user alias, with correct capitalization.
+ms.author: jaredro #Required; microsoft alias of author; optional team alias.
 ms.service: azure #Required;
 ms.topic: include #Required; leave this attribute/value as-is.
 ms.date: 01/26/2023 #Required; mm/dd/yyyy format.
 ---
 
-- Create a L2 isolation-domain
+- Create a L2 isolation domain
 
 ```azurecli
   az nf l2domain create --resource-name "<YourL2IsolationDomainName>" \
@@ -20,7 +20,7 @@ ms.date: 01/26/2023 #Required; mm/dd/yyyy format.
     --mtu "<MtuOfThisNetwork>
 ```
 
-- Enable the L2 isolation-domain after it's created
+- Enable the L2 isolation domain after it's created
 
 ```azurecli
   az managednetworkfabric l2isolationdomain update-administrative-state \
@@ -30,4 +30,4 @@ ms.date: 01/26/2023 #Required; mm/dd/yyyy format.
     --state Enable
 ```
 
-- (Optional) Repeat, as needed, to create other L2 isolation-domain(s)
+- (Optional) Repeat, as needed, to create other L2 isolation domain(s)

articles/operator-nexus/includes/l3-isolation-domain.md

@@ -1,14 +1,14 @@
 ---
-title: "Azure Operator Nexus: Creation of L3 isolation-domain"
-description: Learn how create L3 isolation-domain.
-author: jwheeler60 #Required; your GitHub user alias, with correct capitalization.
-ms.author: johnwheeler #Required; microsoft alias of author; optional team alias.
+title: "Azure Operator Nexus: Creation of L3 isolation domain"
+description: Learn how create L3 isolation domain.
+author: jaredr80 #Required; your GitHub user alias, with correct capitalization.
+ms.author: jaredro #Required; microsoft alias of author; optional team alias.
 ms.service: azure #Required;
 ms.topic: include #Required; leave this attribute/value as-is.
 ms.date: 01/26/2023 #Required; mm/dd/yyyy format.
 ---
 
-- Create a L3 isolation-domain
+- Create a L3 isolation domain
 
 ```azurecli
   az nf l3domain create \
@@ -19,9 +19,8 @@ ms.date: 01/26/2023 #Required; mm/dd/yyyy format.
     --location "<ClusterAzureRegion>"
 ```
 
-- Create an `internalnetwork` resource for every VLAN/subnet that you need to include in your L3 isolation-domain
+- Create an `internalnetwork` resource for every VLAN/subnet that you need to include in your L3 isolation domain
 
-L3 isolation-domain, you'll need to create an `internalnetwork` resource
 
 > [!NOTE]
 > The following example uses the minimal configuration you will need to create a valid internal network.
@@ -42,7 +41,7 @@ L3 isolation-domain, you'll need to create an `internalnetwork` resource
         "ipv4NeighborAddress":[{"address": "<YourSubetInfoHere> "}]}'
 ```
 
-- (Optional) Repeat, as needed, for any other `internalnetwork(s)` that have to be added to this L3 isolation-domain
+- (Optional) Repeat, as needed, for any other `internalnetwork(s)` that have to be added to this L3 isolation domain
 - Enable the L3 isolation-domain after all `internalnetworks` have been created
 
 ```azurecli
@@ -53,4 +52,4 @@ L3 isolation-domain, you'll need to create an `internalnetwork` resource
     --state Enable
 ```
 
-- Repeat to create more L3 isolation-domain(s).
+- Repeat to create more L3 isolation domain(s).