making fixes per review

Sakthi Vetrivel · Sakthi Vetrivel · commit 2ecf2cda5c21 · 2020-04-27T13:19:46.000-07:00
diff --git a/articles/openshift/aro4x-support-policies.md b/articles/openshift/aro4x-support-policies.md
@@ -19,11 +19,11 @@ This article outlines configuration requirements for Azure Red Hat OpenShift 4 c
 
 * All OpenShift Cluster operators must remain in a managed state. The list of cluster operators can be returned by running `oc get clusteroperators`.
 * The cluster Prometheus and Alertmanager services must not be removed or modified.  Service Alertmanager rules must not be removed.
-* The ARO service sets the OpenShift cluster version.  It must not be modified.
-* ARO service logging (mdsd pods) must not be removed or modified.
+* The Azure Red Hat OpenShift service sets the OpenShift cluster version.  It must not be modified.
+* Azure Red Hat OpenShift service logging (mdsd pods) must not be removed or modified.
 * The 'arosvc.azurecr.io' cluster pull secret must not be removed or modified.
 * All cluster virtual machines must have outbound internet access, at least to the Azure Resource Manager (ARM) and service logging (Geneva) endpoints.
-* The ARO service accesses your cluster via Private Link Service.  Service access must not be removed or modified.
+* The Azure Red Hat OpenShift service accesses your cluster via Private Link Service.  Service access must not be removed or modified.
 * Non-RHCOS compute nodes are not supported. For example, you cannot use a RHEL compute node.
 
 ## Supported virtual machine sizes
diff --git a/articles/openshift/configure-azure-ad-cli.md b/articles/openshift/configure-azure-ad-cli.md
@@ -89,7 +89,7 @@ cat > manifest.json<< EOF
   "source": null,
   "essential": false,
   "additionalProperties": []
-}
+}]
 EOF
 ```
 
diff --git a/articles/openshift/dns-forwarding.md b/articles/openshift/dns-forwarding.md
@@ -9,7 +9,7 @@ ms.date: 04/24/2020
 ---
 # Configure DNS Forwarding on an Azure Red Hat OpenShift 4 Cluster
 
-To configure DNS Forwarding on an ARO 4.3 cluster, you'll need to modify the DNS Operator in Azure Red Hat OpenShift 4. This modification will allow your application pods running inside the ARO 4.3 cluster to resolve names hosted on a private DNS server outside the cluster. These steps are documented for OpenShift 4.3 [here](https://docs.openshift.com/container-platform/4.3/networking/dns-operator.html).
+To configure DNS Forwarding on an Azure Red Hat OpenShift cluster, you'll need to modify the DNS Operator. This modification will allow your application pods running inside the cluster to resolve names hosted on a private DNS server outside the cluster These steps are documented for OpenShift 4.3 [here](https://docs.openshift.com/container-platform/4.3/networking/dns-operator.html).
 
 For example, if you want to forward all DNS requests for *.example.com to be resolved by a DNS server 192.168.100.10, you can edit the operator configuration by running:
  
diff --git a/articles/openshift/toc.yml b/articles/openshift/toc.yml
@@ -15,8 +15,6 @@
 - name: How-to guides
   expanded: true
   items:
-    - name: Create a Azure Red Hat OpenShift 4 cluster 
-      href: howto-using-azure-redhat-openshift.md
     - name: Create a private Azure Red Hat OpenShift 4 cluster 
       href: create-private-cluster.md
     - name: Configure DNS Forwarding for an Azure Red Hat OpenShift 4 cluster
diff --git a/articles/openshift/tutorial-connect-cluster.md b/articles/openshift/tutorial-connect-cluster.md
@@ -11,15 +11,15 @@ ms.date: 04/24/2020
 
 # Tutorial: Connect to an Azure Red Hat OpenShift 4 cluster
 
-In this tutorial, part two of three, you will connect to an Azure Red Hat OpenShift (ARO) cluster running OpenShift 4 as the kubeadmin user through the OpenShift web console. You learn how to:
+In this tutorial, part two of three, you will connect to an Azure Red Hat OpenShift cluster running OpenShift 4 as the kubeadmin user through the OpenShift web console. You learn how to:
 > [!div class="checklist"]
 > * Obtain `kubeadmin` credentials for your cluster
 > * Install the OpenShift CLI
-> * Connect to an ARO cluster using the OpenShift CLI
+> * Connect to an Azure Red Hat OpenShift cluster using the OpenShift CLI
 
 ## Before you begin
 
-In previous tutorials, an ARO cluster was created. If you have not done these steps, and would like to follow along, start with [Tutorial 1 - Create an Azure Red Hat Openshift 4 Cluster.](tutorial-create-cluster.md)
+In previous tutorials, an Azure Red Hat OpenShift cluster was created. If you have not done these steps, and would like to follow along, start with [Tutorial 1 - Create an Azure Red Hat Openshift 4 Cluster.](tutorial-create-cluster.md)
 
 If you choose to install and use the CLI locally, this tutorial requires that you are running the Azure CLI version 2.0.75 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest).
 
@@ -29,8 +29,8 @@ You can log into the cluster using the `kubeadmin` user.  Run the following comm
 
 ```azurecli-interactive
 az aro list-credentials \
-  --name aro-cluster \
-  --resource-group aro-rg
+  --name $CLUSTER \
+  --resource-group $RESOURCEGROUP
 ```
 
 The following example output shows the password will be in `kubeadminPassword`.
@@ -46,8 +46,8 @@ You can find the cluster console URL by running the following command, which wil
 
 ```azurecli-interactive
  az aro show \
-    --name aro-cluster \
-    --resource-group aro-rg \
+    --name $CLUSTER \
+    --resource-group $RESOURCEGROUP \
     --query "consoleProfile.url" -o tsv
 ```
 
@@ -79,7 +79,7 @@ echo 'export PATH=$PATH:~/openshift' >> ~/.bashrc && source ~/.bashrc
 Retrieve the API server's address.
 
 ```azurecli-interactive
-apiServer=$(az aro show -g aro-rg -n aro-cluster --query apiserverProfile.url -o tsv)
+apiServer=$(az aro show -g $RESOURCEGROUP -n $CLUSTER --query apiserverProfile.url -o tsv)
 ```
 
 Login to the OpenShift cluster's API server using the following command. Replace **\<kubeadmin password>** with the password you just retrieved.
@@ -94,7 +94,7 @@ In this part of the tutorial, you learned how to:
 > [!div class="checklist"]
 > * Obtain `kubeadmin` credentials for your cluster
 > * Install the OpenShift CLI
-> * Connect to an ARO cluster using the OpenShift CLI
+> * Connect to an Azure Red Hat OpenShift cluster using the OpenShift CLI
 
 Advance to the next tutorial:
 > [!div class="nextstepaction"]
diff --git a/articles/openshift/tutorial-delete-cluster.md b/articles/openshift/tutorial-delete-cluster.md
@@ -11,15 +11,15 @@ ms.date: 04/24/2020
 
 # Tutorial: Delete an Azure Red Hat OpenShift 4 cluster
 
-In this tutorial, part three of three, an Azure Red Hat OpenShift (ARO) cluster running OpenShift 4 is deleted. You learn how to:
+In this tutorial, part three of three, an Azure Red Hat OpenShift cluster running OpenShift 4 is deleted. You learn how to:
 
 > [!div class="checklist"]
 > * Delete an Azure Red Hat OpenShift cluster
 
 
 ## Before you begin
 
-In previous tutorials, an ARO cluster was created and connected to using the OpenShift web console. If you have not done these steps, and would like to follow along, start with [Tutorial 1 - Create an Azure Red Hat Openshift 4 Cluster.](tutorial-create-cluster.md)
+In previous tutorials, an Azure Red Hat OpenShift cluster was created and connected to using the OpenShift web console. If you have not done these steps, and would like to follow along, start with [Tutorial 1 - Create an Azure Red Hat Openshift 4 Cluster.](tutorial-create-cluster.md)
 
 If you choose to install and use the CLI locally, this tutorial requires that you are running the Azure CLI version 2.0.75 or later. Run `az --version` to find the version. If you need to install or upgrade, see [Install Azure CLI](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest).
 
