Merge pull request #233386 from ShawnJackson/quickstarts-tenant-workload

[AQ] edit pass: Two workload deployment how-to articles

Author: ktoliver

articles/operator-nexus/howto-hybrid-aks.md

@@ -17,7 +17,7 @@ This document shows how to manage an AKS-Hybrid cluster that you use for CNF wor
 
 You need:
 
-1. You should have created an [AKS-Hybrid Cluster](./quickstarts-tenant-workload-deployment.md#section-k-how-to-create-aks-hybrid-cluster-for-deploying-cnf-workloads)
+1. You should have created an [AKS-Hybrid Cluster](./quickstarts-tenant-workload-deployment.md#create-aks-hybrid-clusters-for-cnf-workloads)
 2. <`YourAKS-HybridClusterName`>: the name of your previously created AKS-Hybrid cluster
 3. <`YourSubscription`>: your subscription name or ID where the AKS-Hybrid cluster was created
 4. <`YourResourceGroupName`>: the name of the Resource group where the AKS-Hybrid cluster was created

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: jaredr80 #Required; your GitHub user alias, with correct capitalization.
-ms.author: jaredro #Required; microsoft alias of author; optional team alias.
-ms.service: azure-operator-nexus #Required;
-ms.topic: include #Required; leave this attribute/value as-is.
-ms.date: 01/26/2023 #Required; mm/dd/yyyy format.
+title: "Azure Operator Nexus: Create an L2 isolation domain"
+description: Learn how to create an L2 isolation domain.
+author: jaredr80
+ms.author: jaredro
+ms.service: azure-operator-nexus
+ms.topic: include
+ms.date: 01/26/2023
 ---
 
-- Create a L2 isolation domain
+Create an 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 that you 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)
+Repeat, as needed, to create other L2 isolation domains.

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: jaredr80 #Required; your GitHub user alias, with correct capitalization.
-ms.author: jaredro #Required; microsoft alias of author; optional team alias.
-ms.service: azure-operator-nexus #Required;
-ms.topic: include #Required; leave this attribute/value as-is.
-ms.date: 01/26/2023 #Required; mm/dd/yyyy format.
+title: "Azure Operator Nexus: Create an L3 isolation domain"
+description: Learn how to create an L3 isolation domain.
+author: jaredr80
+ms.author: jaredro
+ms.service: azure-operator-nexus
+ms.topic: include
+ms.date: 01/26/2023
 ---
 
-- Create a L3 isolation domain
+Create an L3 isolation domain:
 
 ```azurecli
   az nf l3domain create \
@@ -19,12 +19,10 @@ 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 or subnet that you need to include in your L3 isolation domain.
 
 > [!NOTE]
-> The following example uses the minimal configuration you will need to create a valid internal network.
-> The optional parameters are not shown.
+> The following example uses the minimal configuration for creating a valid internal network. It doesn't show optional parameters.
 
 ```azurecli
   az nf internalnetwork create \
@@ -41,8 +39,9 @@ ms.date: 01/26/2023 #Required; mm/dd/yyyy format.
         "ipv4NeighborAddress":[{"address": "<YourSubetInfoHere> "}]}'
 ```
 
-- (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
+Repeat, as needed, for any other `internalnetwork` resources that you have to add to this L3 isolation domain.
+
+Enable the L3 isolation domain after you've created all `internalnetwork` resources.
 
 ```azurecli
   az nf l3domain update-admin-state \
@@ -52,4 +51,4 @@ ms.date: 01/26/2023 #Required; mm/dd/yyyy format.
     --state Enable
 ```
 
-- Repeat to create more L3 isolation domain(s).
+Repeat to create more L3 isolation domains.