kubev2v · RichardHoch · Sep 1, 2025 · anarnold97 · Sep 10, 2025 · RichardHoch
diff --git a/documentation/modules/accessing-default-validation-rules.adoc b/documentation/modules/accessing-default-validation-rules.adoc
@@ -20,7 +20,7 @@ Example: If a default rule contains the line `default valid_input = false` and y
 $ {oc} rsh <validation_pod>
 ----
 
-. Go to the OPA policies directory for your provider:
+. Go to the Open Policy Agent (OPA) policies directory for your provider:
 +
 [source,terminal]
 ----

diff --git a/documentation/modules/accessing-logs-cli.adoc b/documentation/modules/accessing-logs-cli.adoc
@@ -19,7 +19,7 @@ If you specify a non-existent resource in the filtered `must-gather` command, no
 .Prerequisites
 
 * You must be logged in to the {virt} cluster as a user with the `cluster-admin` role.
-* You must have the link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/cli_tools/openshift-cli-oc#cli-getting-started[{ocp} CLI (`oc`)] installed.
+* You must have the {ocp} CLI (`oc`) installed. For more information, see {ocp-doc}/cli_tools/openshift-cli-oc#cli-getting-started[Getting started with the {ocp-short} CLI].
 
 .Procedure
 

diff --git a/documentation/modules/adding-hook-using-cli.adoc b/documentation/modules/adding-hook-using-cli.adoc
@@ -31,7 +31,7 @@ You can retrieve additional information stored in a secret or in a `ConfigMap` b
 * VMs running on Microsoft Server only: Remote Execution enabled
 
 .Additional resources
-For instructions for creating a service account, see link:https://docs.openshift.com/container-platform/{ocp-version}/authentication/understanding-and-creating-service-accounts.html[Understanding and creating service accounts].
+For instructions for creating a service account, see {ocp-doc}/authentication_and_authorization/index#understanding-and-creating-service-accounts[Understanding and creating service accounts].
 
 .Procedure
 . If needed, create a Secret with an SSH private key for the VM.

diff --git a/documentation/modules/adding-hook-using-ui.adoc b/documentation/modules/adding-hook-using-ui.adoc
@@ -31,7 +31,7 @@ You can run one pre-migration hook, one post-migration hook, or one of each per
 * VMs running on Microsoft Server only: Remote Execution enabled
 
 .Additional resources
-For instructions for creating a service account, see link:https://docs.openshift.com/container-platform/{ocp-version}/authentication/understanding-and-creating-service-accounts.html[Understanding and creating service accounts].
+For instructions for creating a service account, see {ocp-doc}/authentication_and_authorization/index#understanding-and-creating-service-accounts[Understanding and creating service accounts].
 
 .Procedure
 

diff --git a/documentation/modules/adding-source-provider.adoc b/documentation/modules/adding-source-provider.adoc
@@ -93,7 +93,7 @@ ifdef::rhv[]
 endif::[]
 
 ifdef::dest_vmware,dest_rhv,dest_ostack,dest_ova,dest_cnv[]
-* You must have {a-virt} link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/authentication_and_authorization/using-service-accounts[service account token] with `cluster-admin` privileges.
+* You must have {a-virt} service account token with `cluster-admin` privileges. For more information on service account tokens, see {ocp-doc}/authentication_and_authorization/using-service-accounts#service-accounts-overview_using-service-accounts[Service accounts overview].
 endif::[]
 
 .Procedure

diff --git a/documentation/modules/common-attributes.adoc b/documentation/modules/common-attributes.adoc
@@ -11,6 +11,7 @@
 // when updating the ocp-version, update the ocp-y-version
 :ocp-version: 4.19
 :ocp-y-version: 4.19, 4.18, 4.17
+:ocp-doc: link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single
 :operator: mtv-operator
 :operator-name-ui: Migration Toolkit for Virtualization Operator
 :operator-name: MTV Operator

diff --git a/documentation/modules/creating-plan-wizard-290-cnv.adoc b/documentation/modules/creating-plan-wizard-290-cnv.adoc
@@ -115,7 +115,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 

diff --git a/documentation/modules/creating-plan-wizard-290-ostack.adoc b/documentation/modules/creating-plan-wizard-290-ostack.adoc
@@ -115,7 +115,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 

diff --git a/documentation/modules/creating-plan-wizard-290-ova.adoc b/documentation/modules/creating-plan-wizard-290-ova.adoc
@@ -115,7 +115,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 

diff --git a/documentation/modules/creating-plan-wizard-290-rhv.adoc b/documentation/modules/creating-plan-wizard-290-rhv.adoc
@@ -124,7 +124,7 @@ The transfer network is the network used to transfer the VMs to {virt}. This is
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 

diff --git a/documentation/modules/creating-plan-wizard-290-vmware.adoc b/documentation/modules/creating-plan-wizard-290-vmware.adoc
@@ -131,7 +131,7 @@ You do not need to enter the passphrases in a specific order. For each LUKS-encr
 ** To choose a different transfer network, select a different transfer network from the list.
 ** Optional: To configure another {ocp-short} network in the {ocp-short} web console, click *Networking > NetworkAttachmentDefinitions*.
 +
-To learn more about the different types of networks {ocp-short} supports, see link:https://docs.redhat.com/en/documentation/openshift_container_platform/{ocp-version}/html-single/networking/index#additional-networks-provided_understanding-multiple-networks[Additional Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
-To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
-To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
+To learn more about the different types of networks {ocp-short} supports, see {ocp-doc}/multiple_networks/understanding-multiple-networks#additional-networks-provided_understanding-multiple-networks[Secondary Networks in OpenShift Container Platform].
 
 ** To adjust the maximum transmission unit (MTU) of the {ocp-short} transfer network, you must also change the MTU of the VMware migration network. For more information, see xref:selecting-migration-network-for-vmware-source-provider_vmware[Selecting a migration network for a VMware source provider].
 

diff --git a/documentation/modules/creating-validation-rule.adoc b/documentation/modules/creating-validation-rule.adoc
@@ -40,7 +40,7 @@ You create a link:https://www.openpolicyagent.org/docs/latest/policy-language/[R
 
 .Procedure
 
-. Create a config map CR according to the following example:
+. Create a config map custom resource (CR) according to the following example:
 +
 [source,yaml,subs="attributes+"]
 ----

diff --git a/documentation/modules/creating-vddk-image.adoc b/documentation/modules/creating-vddk-image.adoc
@@ -25,7 +25,7 @@ Storing the VDDK image in a public registry might violate the {vmw} license term
 
 .Prerequisites
 
-* link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/registry/setting-up-and-configuring-the-registry#configuring-registry-storage-baremetal[{ocp} image registry].
+* {ocp} image configured for bare metal. For more information, see {ocp-doc}/registry/setting-up-and-configuring-the-registry#configuring-registry-storage-baremetal[Configuring the registry for bare metal].
 * `podman` installed.
 * You are working on a file system that preserves symbolic links (symlinks).
 * If you are using an external registry, {virt} must be able to access it.
@@ -42,11 +42,6 @@ $ mkdir /tmp/<dir_name> && cd /tmp/<dir_name>
 . In a browser, navigate to the link:https://developer.vmware.com/web/sdk/8.0/vddk[VMware VDDK version 8 download page].
 . Select version 8.0.1 and click *Download*.
 
-[NOTE]
-====
-In order to migrate to {virt} 4.12, download VDDK version 7.0.3.2 from the link:https://developer.vmware.com/web/sdk/7.0/vddk[VMware VDDK version 7 download page].
-====
-
 . Save the VDDK archive file in the temporary directory.
 . Extract the VDDK archive:
 +

diff --git a/documentation/modules/error-messages.adoc b/documentation/modules/error-messages.adoc
@@ -19,6 +19,6 @@ To resolve this problem, delete some of the CBT snapshots from the VM and restar
 [id="unable-resize-disk-image_{context}"]
 == Unable to resize disk image to required size
 
-The `Unable to resize disk image to required size` error message is displayed when migration fails because a virtual machine on the target provider uses persistent volumes with an EXT4 file system on block storage. The problem occurs because the default overhead that is assumed by CDI does not completely include the reserved place for the root partition.
+The `Unable to resize disk image to required size` error message is displayed when migration fails because a virtual machine on the target provider uses persistent volumes with an EXT4 file system on block storage. The problem occurs because the default overhead that is assumed by Containerized Data Importer (CDI) does not completely include the reserved place for the root partition.
 
 To resolve this problem, increase the file system overhead in CDI to more than 10%.
diff --git a/documentation/modules/network-prerequisites.adoc b/documentation/modules/network-prerequisites.adoc
@@ -11,7 +11,7 @@ The following network prerequisites apply to all migrations:
 
 * IP addresses, VLANs, and other network configuration settings must not be changed before or during migration. The MAC addresses of the virtual machines are preserved during migration.
 * The network connections between the source environment, the {virt} cluster, and the replication repository must be reliable and uninterrupted.
-* If you are mapping more than one source and destination network, you must create a link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/virtualization/virtual-machines#virt-creating-network-attachment-definition[network attachment definition] for each additional destination network.
+* If you are mapping more than one source and destination network, you must create a network attachment definition for each additional destination network. For more information, see {ocp-doc}/virtualization/index#virt-creating-vms-from-rh-images-overview[Creating virtual machines from Red Hat images overview].
 
 [id="ports_{context}"]
 == Ports

diff --git a/documentation/modules/status-vms-warm-migration.adoc b/documentation/modules/status-vms-warm-migration.adoc
@@ -28,7 +28,7 @@ A VM can support up to 28 CBT snapshots. If the source VM has too many CBT snaps
 The precopy stage runs until the cutover stage is started manually or is scheduled to start.
 
 [id="status-vms-warm-migration-cutover_{context}"]
-==Cutover stage
+== Cutover stage
 
 The VMs are shut down during the cutover stage, and the remaining data is migrated. Data stored in RAM is not migrated.
 

diff --git a/documentation/modules/storage-support.adoc b/documentation/modules/storage-support.adoc
@@ -61,7 +61,7 @@
 
 [NOTE]
 ====
-If the {virt} storage does not support link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/storage/dynamic-provisioning[dynamic provisioning], you must apply the following settings:
+If the {virt} storage does not support {ocp-doc}/storage/dynamic-provisioning#dynamic-provisioning[dynamic provisioning], you must apply the following settings:
 
 * `Filesystem` volume mode
 +
@@ -70,7 +70,7 @@ If the {virt} storage does not support link:https://access.redhat.com/documentat
 +
 `ReadWriteOnce` access mode does not support live virtual machine migration.
 
-See link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/virtualization/virtual-machines#virt-customizing-storage-profile_virt-creating-data-volumes[Enabling a statically-provisioned storage class] for details on editing the storage profile.
+See {ocp-doc}/virtualization/storage#virt-configuring-storage-profile[Configuring storage profiles] for details on applying settings to a storage profile.
 ====
 
 [NOTE]

diff --git a/documentation/modules/upgrading-mtv-ui.adoc b/documentation/modules/upgrading-mtv-ui.adoc
@@ -15,10 +15,10 @@ You can upgrade the {operator-name} by using the {ocp} web console to install th
 . Change the update channel to the correct release.
 +
 ifeval::["{build}" == "upstream"]
-See link:https://docs.okd.io/latest/operators/admin/olm-upgrading-operators.html#olm-changing-update-channel_olm-upgrading-operators[Changing update channel] in the {ocp} documentation.
+See link:https://docs.okd.io/latest/operators/admin/olm-upgrading-operators.html#olm-changing-update-channel_olm-upgrading-operators[Updating installed Operators] in the {ocp} documentation.
 endif::[]
 ifeval::["{build}" == "downstream"]
-See link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/operators/administrator-tasks#olm-changing-update-channel_olm-upgrading-operators[Changing update channel] in the {ocp} documentation.
+See {ocp-doc}/operators/administrator-tasks#olm-changing-update-channel_olm-upgrading-operators[Changing the update channel for an Operator] in the {ocp} documentation.
 endif::[]
 
 . Confirm that *Upgrade status* changes from *Up to date* to *Upgrade available*. If it does not, restart the `CatalogSource` pod:
@@ -45,12 +45,8 @@ If you set *Update approval* on the *Subscriptions* tab to *Automatic*, the upgr
 . If you set *Update approval* on the *Subscriptions* tab to *Manual*, approve the upgrade.
 +
 ifeval::["{build}" == "upstream"]
-See link:https://docs.okd.io/latest/operators/admin/olm-upgrading-operators.html#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending upgrade] in the {ocp} documentation.
+See link:https://docs.okd.io/latest/operators/admin/olm-upgrading-operators.html#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending Operator upgrade] in the {ocp} documentation.
 endif::[]
 ifeval::["{build}" == "downstream"]
-See link:https://access.redhat.com/documentation/en-us/openshift_container_platform/{ocp-version}/html/operators/administrator-tasks#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending upgrade] in the {ocp} documentation.
+See {ocp-doc}/operators/administrator-tasks#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending upgrade] in the {ocp} documentation.
 endif::[]
-
-. If you are upgrading from {project-short} 2.2 and have defined VMware source providers, edit the VMware provider by adding a VDDK `init` image. Otherwise, the update will change the state of any VMware providers to `Critical`. For more information, see link:https://access.redhat.com/documentation/en-us/migration_toolkit_for_virtualization/2.4/html/installing_and_using_the_migration_toolkit_for_virtualization/migrating-vms-web-console#adding-source-provider_vmware[Adding a VMSphere source provider].
-
-. If you mapped to NFS on the {ocp} destination provider in {project-short} 2.2, edit the `AccessModes` and `VolumeMode` parameters in the NFS storage profile. Otherwise, the upgrade will invalidate the NFS mapping. For more information, see link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.9/html-single/virtualization/index#virt-customizing-storage-profile_virt-creating-data-volumes[Customizing the storage profile].
diff --git a/documentation/modules/using-must-gather.adoc b/documentation/modules/using-must-gather.adoc
@@ -19,7 +19,7 @@ If you specify a non-existent resource in the filtered `must-gather` command, no
 .Prerequisites
 
 * You must be logged in to the {virt} cluster as a user with the `cluster-admin` role.
-* You must have the link:https://docs.openshift.com/container-platform/{ocp-version}/cli_reference/openshift_cli/getting-started-cli.html[{ocp} CLI (`oc`)] installed.
+* You must have the {ocp} CLI (`oc`) installed. For more information, see {ocp-doc}/cli_tools/openshift-cli-oc#cli-getting-started[Getting started with the {ocp-short} CLI].
 
 .Procedure