Merge pull request #6502 from ahardin-rh/custom-route-followup

Follow-up edits to PR#5084

Author: ahardin-rh

dev_guide/routes.adoc

@@ -338,16 +338,13 @@ $ oc get route/<route-name>
 
 Custom certificates are permitted in {product-title} Pro. In {product-title}
 Starter, only unencrypted routes, edge routes using the default certificate, and
-passthrough routes work. Edge routes with custom certificates and re-encrypt
-routes (which necessarily have custom certificates) do not work in
-{product-title} Starter.
-
-These restrictions are enforced in the router. Inspecting the route in the
-console or using `oc get routes` displays the host and certificates specified by
-the user. The status of the route indicates if the route is restricted. However,
-custom hosts are not respected in {product-title} Starter, and routes with
-custom certificates do not work. In {product-title} Pro, a default host is
-provided if the user does not specify a custom host.
+passthrough routes work. Edge and re-encrypt routes with custom certificates do
+not work in {product-title} Starter.
+
+These restrictions are enforced by the API.  Attempts to create routes with
+custom hosts or certificates will be rejected in {product-title} Starter. In
+{product-title} Pro, a default host is provided if the user does not specify a
+custom host.
 
 Once your custom route is created in in {product-title} Pro, you must update
 your DNS provider by creating a canonical name (CNAME) record. Your CNAME record