fix: configuring custom che hostname

modules/installation-guide/partials/proc_configuring-che-hostname.adoc

@@ -5,14 +5,14 @@
 
 :context: customize-chehost
 
-This procedure describes how to configure {prod} to use custom hostname.
+This procedure describes how to configure {prod-short} to use custom hostname.
 
 .Prerequisites
 
 * The `{orch-cli}` tool is available.
 * The certificate and the private key files are generated.
 
-IMPORTANT: To generate the pair of private key and certificate the same CA must be used as for other {prod} hosts.
+IMPORTANT: To generate the pair of a private key and certificate, the same certification authority (CA) must be used as for other {prod-short} hosts.
 
 IMPORTANT: Ask a DNS provider to point the custom hostname to the cluster ingress.
 
@@ -51,18 +51,6 @@ spec:
 <1> Custom {prod} server hostname
 <2> The TLS secret name
 
-pass:[<!-- vale Vale.Spelling = NO -->]
-
-pass:[<!-- vale Vale.Terms = NO -->]
-
-. If {prod-short} has been already deployed and {prod-short} reconfiguring to use a new {prod-short} hostname is required, log in using {identity-provider} and select the `{prod-deployment}-public` client in the `{prod-short}` realm and update `Validate Redirect URIs` and `Web Origins` fields with the value of the {prod-short} hostname.
-+
-image::keycloak/keycloak_che_public_client.png[]
-+
-For logging in to {identity-provider}, follow the xref:setting-up-the-keycloak-che-username-readonly-theme-for-the-eclipse-che-login-page.adoc#logging-in-to-identity-provider_{context}[Logging in to {identity-provider}] procedure.
-
-pass:[<!-- vale Vale.Spelling = YES -->]
-
-pass:[<!-- vale Vale.Terms = YES -->]
+. If {prod-short} has been already deployed, wait until the rollout of all {prod-short} components finishes.
 
 :context: {parent-context-of-customize-chehost}