TELCODOCS-430: Updated to reflect support of multiple simultaneous patch (x.y.z) versions of Release/OS images

Author: kdrake20

modules/ztp-ai-install-ocp-clusters-on-bare-metal.adoc

@@ -71,7 +71,7 @@ spec:
 <2> Volume size for the `filesystemStorage` field, for example `20Gi`.
 <3> Volume size for the `imageStorage` field, for example `2Gi`.
 <4> List of OS image details, for example a single {product-title} OS version.
-<5> {product-title} version to install, for example, `"4.8"`.
+<5> {product-title} version to install, in either "x.y" (major.minor) or "x.y.z" (major.minor.patch) formats.
 <6> Specific install version, for example, `47.83.202103251640-0`.
 <7> ISO url, for example, `https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.7/4.7.7/rhcos-4.7.7-x86_64-live.x86_64.iso`.
 <8> Root FS image URL, for example `https://mirror.openshift.com/pub/openshift-v4/dependencies/rhcos/4.7/4.7.7/rhcos-live-rootfs.x86_64.img`.

modules/ztp-creating-siteconfig-custom-resources.adoc

@@ -71,8 +71,7 @@ spec:
    releaseImage: quay.io/openshift-release-dev/ocp-release:4.10.0-x86_64 <2>
 ----
 <1> The descriptive version that you want to deploy.
-<2> Points to the specific release image to deploy.
-
+<2> Specifies the `releaseImage` to deploy and determines the OS Image version. The discovery ISO is based on an OS image version as the `releaseImage`, or latest if the exact version is unavailable.
 
 . Create the `Namespace` definition for the managed cluster:
 +