Merge pull request #87485 from DCChadwick/ocpbugs20186

OCPBUGS-20186: Clarify documentation about host parameters in a route

Author: skrthomas

modules/nw-creating-a-route.adoc

@@ -13,7 +13,6 @@ The following procedure describes how to create a simple HTTP-based route to a w
 
 .Prerequisites
 
-
 * You installed the OpenShift CLI (`oc`).
 * You are logged in as an administrator.
 * You have a web application that exposes a port and a TCP endpoint listening for traffic on the port.
@@ -66,15 +65,15 @@ kind: Route
 metadata:
   name: hello-openshift
 spec:
-  host: hello-openshift-hello-openshift.<Ingress_Domain> <1>
+  host: www.example.com <1>
   port:
     targetPort: 8080 <2>
   to:
     kind: Service
     name: hello-openshift
 ----
-<1> `<Ingress_Domain>` is the default ingress domain name. The `ingresses.config/cluster` object is created during the installation and cannot be changed. If you want to specify a different domain, you can specify an alternative cluster domain using the `appsDomain` option.
-<2> `targetPort` is the target port on pods that is selected by the service that this route points to.
+<1> The `host` field is an alias DNS record that points to the service. This field can be any valid DNS name, such as `www.example.com`. The DNS name must follow DNS952 subdomain conventions. If not specified, a route name is automatically generated. 
+<2> The `targetPort` field is the target port on pods that is selected by the service that this route points to.
 
 +
 [NOTE]