Merge pull request #30171 from apinnick/bz1913075-mtc-ui-wording

BZ1913075:  Improve the wording of exposed image registry route in UI (1.4.2)

Author: apinnick

modules/migration-adding-cluster-to-cam.adoc

@@ -11,15 +11,16 @@ You can add a cluster to the {mtc-full} ({mtc-short}) web console.
 
 .Prerequisites
 
-* Optional: If you are using direct image migration, the source cluster must not have an HTTP proxy configured.
-* Optional: If you are using Azure snapshots to copy data:
-** You must specify the Azure resource group name for the source cluster.
-** The source and target clusters must be in the same Azure resource group and in the same location.
+* If you are using direct image migration, the source cluster must not have an HTTP proxy configured.
+* If you are using Azure snapshots to copy data:
+** You must specify the Azure resource group name for the cluster.
+** The clusters must be in the same Azure resource group.
+** The clusters must be in the same geographic location.
 
 .Procedure
 
 . Log in to the cluster.
-. Obtain the service account token:
+. Obtain the `migration-controller` service account token:
 +
 [source,terminal]
 ----
@@ -37,16 +38,17 @@ eyJhbGciOiJSUzI1NiIsImtpZCI6IiJ9.eyJpc3MiOiJrdWJlcm5ldGVzL3NlcnZpY2VhY2NvdW50Iiw
 . Click *Add cluster*.
 . Fill in the following fields:
 
-* *Cluster name*: May contain lower-case letters (`a-z`) and numbers (`0-9`). Must not contain spaces or international characters.
-* *Url*: URL of the cluster's API server, for example, `\https://<master1.example.com>:8443`.
-* *Service account token*: String that you obtained from the source cluster.
-* *Exposed route to image registry*: Optional. You can specify a route to the image registry of your source cluster to enable direct migration for images, for example, `docker-registry-default.apps.cluster.com`.
+* *Cluster name*: The cluster name can contain lower-case letters (`a-z`) and numbers (`0-9`). It must not contain spaces or international characters.
+* *URL*: Specify the API server URL, for example, `\https://<www.example.com>:8443`.
+* *Service account token*: Paste the `migration-controller` service account token.
+* *Exposed route host to image registry*: If you are using direct image migration, specify the exposed route to the image registry of the source cluster, for example, `www.example.apps.cluster.com`.
 +
-Direct migration is much faster than migration with a replication repository.
+You can specify a port. The default port is `5000`.
 
-* *Azure cluster*: Optional. Select it if you are using Azure snapshots to copy your data.
-* *Azure resource group*: This field appears if *Azure cluster* is checked.
-* If you use a custom CA bundle, click *Browse* and browse to the CA bundle file.
+* *Azure cluster*: You must select this option if you use Azure snapshots to copy your data.
+* *Azure resource group*: This field is displayed if *Azure cluster* is selected. Specify the Azure resource group.
+* *Require SSL verification*: Optional: Select this option to verify SSL connections to the cluster.
+* *CA bundle file*: This field is displayed if *Require SSL verification* is selected. If you created a custom CA certificate bundle file for self-signed certificates, click *Browse*, select the CA bundle file, and upload it.
 
 . Click *Add cluster*.
 +