Merge pull request #32249 from bmcelvee/BZ1957244

Bug 1957244 update Ingress configuration description for OpenShift API Server Operator

Author: bmcelvee

modules/nw-installation-ingress-config-asset.adoc

@@ -6,8 +6,7 @@
 [id="nw-installation-ingress-config-asset_{context}"]
 = The Ingress configuration asset
 
-The installation program generates an asset with an `Ingress` resource in the
-`config.openshift.io` API group, `cluster-ingress-02-config.yml`.
+The installation program generates an asset with an `Ingress` resource in the `config.openshift.io` API group, `cluster-ingress-02-config.yml`.
 
 .YAML Definition of the `Ingress` resource
 [source,yaml]
@@ -20,14 +19,8 @@ spec:
   domain: apps.openshiftdemos.com
 ----
 
-The installation program stores this asset in the
-`cluster-ingress-02-config.yml` file in
-the `manifests/` directory. This `Ingress` resource defines the cluster-wide
-configuration for Ingress. This Ingress configuration is used as follows:
+The installation program stores this asset in the `cluster-ingress-02-config.yml` file in the `manifests/` directory. This `Ingress` resource defines the cluster-wide configuration for Ingress. This Ingress configuration is used as follows:
 
-* The Ingress Operator uses the domain from the cluster Ingress configuration as
-the domain for the default Ingress Controller.
+* The Ingress Operator uses the domain from the cluster Ingress configuration as the domain for the default Ingress Controller.
 
-* The OpenShift API server operator uses the domain from the cluster Ingress
-configuration as the domain used when generating a default host for a `Route`
-resource that does not specify an explicit host.
+* The OpenShift API Server Operator uses the domain from the cluster Ingress configuration. This domain is also used when generating a default host for a `Route` resource that does not specify an explicit host.