fixing private cluster for 4 TOC

Author: Sakthi Vetrivel

articles/openshift/howto-create-private-cluster.md

@@ -12,19 +12,13 @@ keywords: aro, openshift, private cluster, red hat
 
 # Create a private cluster with Azure Red Hat OpenShift 3.11
 
-> [!IMPORTANT]
-> Azure Red Hat OpenShift (ARO) private clusters are currently only available in private preview in East US 2. Private preview acceptance is by invitation only. Please be sure to register your subscription before attempting to enable this feature.
-
 Private clusters provide the following benefits:
 
 * Private clusters don't expose cluster control plane components (such as the API servers) on a public IP address.
 * The virtual network of a private cluster is configurable by customers, allowing you to set up networking to allow peering with other virtual networks, including ExpressRoute environments. You can also configure custom DNS on the virtual network to integrate with internal services.
 
 ## Before you begin
 
-> [!NOTE]
-> This feature requires version 2019-10-27-preview of the ARO HTTP API. It is not yet supported in the Azure CLI.
-
 The fields in the following configuration snippet are new and must be included in your cluster configuration. `managementSubnetCidr` must be within the cluster virtual network and is used by Azure to manage the cluster.
 
 ```json

articles/openshift/toc.yml

@@ -18,7 +18,7 @@
     - 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: howto-create-private-cluster.md
+      href: create-private-cluster.md
     - name: Configure DNS Forwarding for an Azure Red Hat OpenShift 4 cluster
       href: dns-forwarding.md
     - name: Configure Azure Active Directory authentication for Azure Red Hat OpenShift 4 cluster