Fixed review comments - 6/26/2023

Author: dramasamy

articles/operator-nexus/includes/kubernetes-cluster/quickstart-cleanup.md

@@ -1,3 +1,11 @@
+---
+author: dramasamy
+ms.author: dramasamy
+ms.date: 06/26/2023
+ms.topic: include
+ms.service: azure-operator-nexus
+---
+
 When no longer needed, delete the resource group. The resource group and all the resources in the resource group are deleted.
 
 ### [Azure CLI](#tab/azure-cli)

articles/operator-nexus/includes/kubernetes-cluster/quickstart-cluster-connect.md

@@ -1,3 +1,11 @@
+---
+author: dramasamy
+ms.author: dramasamy
+ms.date: 06/26/2023
+ms.topic: include
+ms.service: azure-operator-nexus
+---
+
 Now that the Nexus Kubernetes cluster has been successfully created and connected to Azure Arc, you can easily connect to it using the cluster connect feature. Cluster connect allows you to securely access and manage your cluster from anywhere, making it convenient for interactive development, debugging, and cluster administration tasks.
 
 > [!NOTE]

articles/operator-nexus/includes/kubernetes-cluster/quickstart-nextsteps.md

@@ -1 +1,9 @@
+---
+author: dramasamy
+ms.author: dramasamy
+ms.date: 06/26/2023
+ms.topic: include
+ms.service: azure-operator-nexus
+---
+
 You can now deploy the CNFs either directly via [cluster connect](../../../azure-arc/kubernetes/cluster-connect.md) or via Azure Operator Service Manager (AOSM).

articles/operator-nexus/includes/kubernetes-cluster/quickstart-prereq.md

@@ -1,3 +1,11 @@
+---
+author: dramasamy
+ms.author: dramasamy
+ms.date: 06/26/2023
+ms.topic: include
+ms.service: azure-operator-nexus
+---
+
 [!INCLUDE [quickstarts-free-trial-note](../../../../includes/quickstarts-free-trial-note.md)]
 
 [!INCLUDE [azure-cli-prepare-your-environment-no-header.md](~/articles/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]

articles/operator-nexus/includes/kubernetes-cluster/quickstart-review-deployment-cli.md

@@ -1,3 +1,11 @@
+---
+author: dramasamy
+ms.author: dramasamy
+ms.date: 06/26/2023
+ms.topic: include
+ms.service: azure-operator-nexus
+---
+
 After the deployment finishes, you can view the resources using the CLI or the Azure portal.
 
 To view the details of the ```myNexusAKSCluster``` cluster in the ```myResourceGroup``` resource group, execute the following Azure CLI command:

articles/operator-nexus/includes/kubernetes-cluster/quickstart-review-nodepool.md

@@ -1,3 +1,11 @@
+---
+author: dramasamy
+ms.author: dramasamy
+ms.date: 06/26/2023
+ms.topic: include
+ms.service: azure-operator-nexus
+---
+
 > [!NOTE]
 > You can add multiple agent pools during the initial creation of your cluster itself by using the initial agent pool configurations. However, if you want to add agent pools after the initial creation, you can utilize the above command to create additional agent pools for your Nexus Kubernetes cluster.
 

articles/operator-nexus/quickstarts-kubernetes-cluster-deployment-arm.md

@@ -68,7 +68,7 @@ Once you have reviewed and saved the template file named ```kubernetes-add-agent
 
 :::code language="json" source="includes/kubernetes-cluster/quickstart-add-node-pool-params.json":::
 
-3. Deploy the template.
+2. Deploy the template.
 
 ```azurecli
     az deployment group create \

articles/operator-nexus/quickstarts-kubernetes-cluster-deployment-bicep.md

@@ -65,7 +65,7 @@ Once you have reviewed and saved the template file named ```kubernetes-add-agent
 
 :::code language="json" source="includes/kubernetes-cluster/quickstart-add-node-pool-params.json":::
 
-3. Deploy the template.
+2. Deploy the template.
 
 ```azurecli
     az deployment group create \