Merge pull request #231903 from joharder/main

Update howto-custom-dns.md

Author: prmerger-automator[bot]

articles/openshift/howto-custom-dns.md

@@ -1,14 +1,14 @@
 ---
-title: Configure custom DNS resources in an Azure Red Hat OpenShift (ARO) cluster
-description: Discover how to add a custom DNS server on all of your nodes in Azure Red Hat OpenShift (ARO).
+title: Configure a custom DNS resolver in an Azure Red Hat OpenShift (ARO) cluster
+description: Discover how to add a custom DNS resolver on all of your nodes in Azure Red Hat OpenShift (ARO).
 author: johnmarco
 ms.author: johnmarc
 ms.service: azure-redhat-openshift
 ms.topic: article
 ms.date: 06/02/2021
 #Customer intent: As an operator or developer, I need a custom DNS configured for an Azure Red Hat OpenShift cluster
 ---
-# Configure custom DNS for your Azure Red Hat OpenShift (ARO) cluster
+# Configure a custom DNS resolver for your Azure Red Hat OpenShift (ARO) cluster
 
 This article provides the necessary details that allow you to configure your Azure Red Hat OpenShift cluster (ARO) to use a custom DNS server. It contains the cluster requirements for a basic ARO deployment.
 
@@ -140,7 +140,7 @@ Create the worker restart file, this example calls the file `worker-restarts.yml
 machineconfig.machineconfiguration.openshift.io/25-machineconfig-worker-reboot created
 ```
 
-The MCO will move workloads and then reboot each node one at a time. Once the workers have come back online, we will follow the same procedure to reboot the master nodes. You can verify the status of the workers by querying the nodes and validate they are all in the `Ready` state.
+The MCO moves workloads and then reboots each node one at a time. Once the workers have come back online, we'll follow the same procedure to reboot the master nodes. You can verify the status of the workers by querying the nodes and validate they're all in the `Ready` state.
 
 >[!NOTE]
 > Depending on the size of the workload the cluster has, it can take several minutes for each node to reboot.