GH#36067: clarifying domain/appsDomain per GH Issue confusion

Author: skrthomas

modules/nw-ingress-configuring-application-domain.adoc

@@ -8,7 +8,7 @@
 
 //OpenShift Dedicated or Amazon RH OpenShift cluster administrator
 
-As a cluster administrator, you can specify an alternative default domain for user-created routes by configuring `appsDomain` field. If you specify an alternative domain, it overrides the default cluster domain for the purpose of determining the default host for a new route.
+As a cluster administrator, you can specify an alternative to the default cluster domain for user-created routes by configuring the `appsDomain` field. The `appsDomain` field is an optional domain for AWS infrastructure to use instead of the default, which is specified in the `domain` field. If you specify an alternative domain, it overrides the default cluster domain for the purpose of determining the default host for a new route.
 
 For example, you can use the DNS domain for your company as the default domain for routes and ingresses for applications running on your cluster.
 
@@ -31,19 +31,21 @@ $ oc edit ingresses.config/cluster -o yaml
 +
 .. Edit the YAML file:
 +
-.Sample `appsDomain` configuration to `apps.acme.io`
+.Sample `appsDomain` configuration to `test.example.com`
 [source,yaml]
 ----
 apiVersion: config.openshift.io/v1
 kind: Ingress
 metadata:
   name: cluster
 spec:
-  domain: apps.<domain_url>
-  appsDomain: apps.acme.io
+  domain: apps.example.com            <1>
+  appsDomain: <test.example.com>      <2>
 ----
+<1> Default domain
+<2> Optional: Domain for AWS infrastructure to use for application routes. Instead of the default prefix, `apps`, you can use an alternative prefix like `test`.
 +
-. Verify that an existing route contains the new domain name by exposing the route and verifying the route domain change:
+. Verify that an existing route contains the domain name specified in the `appsDomain` field by exposing the route and verifying the route domain change:
 //+
 //.. Access the Ingress Controller Operator YAML file:
 //+
@@ -65,11 +67,12 @@ $ oc expose service hello-openshift
 route.route.openshift.io/hello-openshift exposed
 ----
 +
-.. Verify route domain change:
+.Example output:
 +
 [source,terminal]
 ----
 $ oc get routes
 NAME              HOST/PORT                                   PATH   SERVICES          PORT       TERMINATION   WILDCARD
-hello-openshift   hello-openshift-my-project.apps.acme.io          hello-openshift   8080-tcp                 None
+hello-openshift   hello_openshift-<my_project>.test.example.com
+hello-openshift   8080-tcp                 None
 ----