Merge pull request #39723 from adellape/fqdn

Author: adellape

modules/connected-to-disconnected-mirror-images.adoc

@@ -7,7 +7,7 @@
 
 After the cluster is properly configured, you can mirror the images from your external repositories to the mirror repository.
 
-.Procedure 
+.Procedure
 
 . Mirror the Operator Lifecycle Manager (OLM) images:
 // copied from olm-mirroring-catalog.adoc
@@ -21,7 +21,7 @@ $ oc adm catalog mirror registry.redhat.io/redhat/redhat-operator-index:v{produc
 where:
 
 `product-version`:: Specifies the tag that corresponds to the version of {product-title} to install, such as `4.8`.
-`mirror_registry`:: Specifies the target registry and namespace to mirror the Operator content to, where `<namespace>` is any existing namespace on the registry.
+`mirror_registry`:: Specifies the fully qualified domain name (FQDN) for the target registry and namespace to mirror the Operator content to, where `<namespace>` is any existing namespace on the registry.
 `reg_creds`:: Specifies the location of your modified `.dockerconfigjson` file.
 --
 +
@@ -42,8 +42,8 @@ $ oc adm catalog mirror <index_image> <mirror_registry>:<port>/<namespace> -a <r
 --
 where:
 
-`index_image`:: Specifies the index image for the catalog you want to mirror. For example, this might be a pruned index image that you created previously, or one of the source index images for the default catalogs, such as `{index-image-pullspec}`. 
-`mirror_registry`:: Specifies the target registry and namespace to mirror the Operator content to, where `<namespace>` is any existing namespace on the registry.
+`index_image`:: Specifies the index image for the catalog you want to mirror. For example, this might be a pruned index image that you created previously, or one of the source index images for the default catalogs, such as `{index-image-pullspec}`.
+`mirror_registry`:: Specifies the FQDN for the target registry and namespace to mirror the Operator content to, where `<namespace>` is any existing namespace on the registry.
 `reg_creds`:: Optional: Specifies the location of your registry credentials file, if required.
 --
 +

modules/olm-mirroring-catalog-airgapped.adoc

@@ -72,7 +72,7 @@ $ oc adm catalog mirror \
     --index-filter-by-os='<platform>/<arch>' <.>
 ----
 <.> Specify the `file://` path from the previous command output.
-<.> Specify the target registry and namespace to mirror the Operator contents to, where `<namespace>` is any existing namespace on the registry. For example, you might create an `olm-mirror` namespace to push all mirrored content to.
+<.> Specify the fully qualified domain name (FQDN) for the target registry and namespace to mirror the Operator contents to, where `<namespace>` is any existing namespace on the registry. For example, you might create an `olm-mirror` namespace to push all mirrored content to.
 <.> Optional: If required, specify the location of your registry credentials file.
 <.> Optional: If you do not want to configure trust for the target registry, add the `--insecure` flag.
 <.> Optional: Specify which platform and architecture of the index image to select when multiple variants are available. Images are specified as `'<platform>/<arch>[/<variant>]'`. This does not apply to images referenced by the index. Valid values are `linux/amd64`, `linux/ppc64le`, `linux/s390x`, and `.*`

modules/olm-mirroring-catalog-colocated.adoc

@@ -38,7 +38,7 @@ $ oc adm catalog mirror \
     [--manifests-only] <.>
 ----
 <1> Specify the index image for the catalog that you want to mirror. For example, this might be a pruned index image that you created previously, or one of the source index images for the default catalogs, such as `{index-image-pullspec}`.
-<2> Specify the target registry and namespace to mirror the Operator contents to, where `<namespace>` is any existing namespace on the registry. For example, you might create an `olm-mirror` namespace to push all mirrored content to.
+<2> Specify the fully qualified domain name (FQDN) for the target registry and namespace to mirror the Operator contents to, where `<namespace>` is any existing namespace on the registry. For example, you might create an `olm-mirror` namespace to push all mirrored content to.
 <3> Optional: If required, specify the location of your registry credentials file.
 `{REG_CREDS}` is required for `registry.redhat.io`.
 <4> Optional: If you do not want to configure trust for the target registry, add the `--insecure` flag.