Merge pull request #97767 from openshift-cherrypick-robot/cherry-pick-97626-to-enterprise-4.20

[enterprise-4.20] OSDOCS-15854 lines 38-39 of the Route configuration CQA

modules/nw-enabling-hsts.adoc

@@ -3,6 +3,7 @@
 // * networking/configuring-routing.adoc
 // * microshift_networking/microshift-configuring-routes.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="nw-enabling-hsts_{context}"]
 = HTTP Strict Transport Security
 

modules/nw-http-header-configuration.adoc

@@ -6,6 +6,7 @@
 :_mod-docs-content-type: CONCEPT
 [id="nw-http-header-configuration_{context}"]
 = HTTP header configuration
+
 ifndef::microshift[]
 {product-title} provides different methods for working with HTTP headers. When setting or deleting headers, you can use specific fields in the Ingress Controller or an individual route to modify request and response headers. You can also set certain headers by using route annotations. The various ways of configuring headers can present challenges when working together.
 endif::microshift[]

modules/nw-ingress-sharding-route-configuration.adoc

@@ -7,12 +7,10 @@
 [id="nw-ingress-sharding-route-configuration_{context}"]
 = Creating a route for Ingress Controller sharding
 
-A route allows you to host your application at a URL. In this case, the hostname is not set and the route uses a subdomain instead. When you specify a subdomain, you automatically use the domain of the Ingress Controller that exposes the route. For situations where a route is exposed by multiple Ingress Controllers, the route is hosted at multiple URLs.
+A route allows you to host your application at a URL. Ingress Controller sharding helps balance incoming traffic load among a set of Ingress Controllers. It can also isolate traffic to a specific Ingress Controller. For example, company A goes to one Ingress Controller and company B to another.
 
 The following procedure describes how to create a route for Ingress Controller sharding, using the `hello-openshift` application as an example.
 
-Ingress Controller sharding is useful when balancing incoming traffic load among a set of Ingress Controllers and when isolating traffic to a specific Ingress Controller. For example, company A goes to one Ingress Controller and company B to another.
-
 .Prerequisites
 
 * You installed the OpenShift CLI (`oc`).
@@ -106,6 +104,6 @@ status:
     routerCanonicalHostname: router-sharded.<apps-sharded.basedomain.example.net> <2>
     routerName: sharded <3>
 ----
-<1> The hostname the Ingress Controller, or router, uses to expose the route. The value of the `host` field is automatically determined by the Ingress Controller, and uses its domain. In this example, the domain of the Ingress Controller is `<apps-sharded.basedomain.example.net>`.
-<2> The hostname of the Ingress Controller.
+<1> The hostname the Ingress Controller, or router, uses to expose the route. The value of the `host` field is automatically determined by the Ingress Controller, and uses its domain. In this example, the domain of the Ingress Controller is `<apps-sharded.basedomain.example.net>`. 
+<2> The hostname of the Ingress Controller. If the hostname is not set, the route can use a subdomain instead. When you specify a subdomain, you automatically use the domain of the Ingress Controller that exposes the route. When a route is exposed by multiple Ingress Controllers, the route is hosted at multiple URLs.
 <3> The name of the Ingress Controller. In this example, the Ingress Controller has the name `sharded`.

modules/nw-path-based-routes.adoc

@@ -2,6 +2,7 @@
 // Module included in the following assemblies:
 // * networking/routes/route-configuration.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="nw-path-based-routes_{context}"]
 = Path-based routes
 

modules/nw-route-specific-annotations.adoc

@@ -2,6 +2,7 @@
 //
 // * networking/routes/route-configuration.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="nw-route-specific-annotations_{context}"]
 = Route-specific annotations
 

modules/nw-using-cookies-keep-route-statefulness.adoc

@@ -7,6 +7,7 @@
 // * networking/configuring-routing.adoc
 // * microshift_networking/microshift-configuring-routes.adoc
 
+:_mod-docs-content-type: CONCEPT
 [id="nw-using-cookies-keep-route-statefulness_{context}"]
 = Using cookies to keep route statefulness