fix

kubev2v · Oct 29, 2024 · 68908e2 · 68908e2
1 parent 0d5d145
commit 68908e2
Show file tree

Hide file tree

Showing 3 changed files with 6 additions and 6 deletions.
diff --git a/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc b/documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc
@@ -192,8 +192,8 @@ You can create a migration plan by using the {ocp} web console to specify a sour
 
 For your convenience, there are two procedures to create migration plans, starting with either a source provider or with specific VMs:
 
-* To start with a source provider, see xref:creating-migration-plan_provider[Creating a migration plan starting with a source provider].
-* To start with specific VMs, see xref:creating-migration-plan_vms[Creating a migration plan starting with specific VMs].
+* To start with a source provider, see xref:creating-migration-plan-2-7_provider[Creating a migration plan starting with a source provider].
+* To start with specific VMs, see xref:creating-migration-plan-2-7_vms[Creating a migration plan starting with specific VMs].
 
 [WARNING]
 ====
@@ -208,12 +208,12 @@ include::modules/snip_plan-limits.adoc[]
 :context: provider
 :provider:
 
-include::modules/creating-migration-plan.adoc[leveloffset=+3]
+include::modules/creating-migration-plan-2-7.adoc[leveloffset=+3]
 
 :provider!:
 :context: vms
 :vms:
-include::modules/creating-migration-plan.adoc[leveloffset=+3]
+include::modules/creating-migration-plan-2-7.adoc[leveloffset=+3]
 
 :vms!:
 :context: mtv

diff --git a/...tion/modules/creating-migration-plan.adoc → .../modules/creating-migration-plan-2-7.adoc b/...tion/modules/creating-migration-plan.adoc → .../modules/creating-migration-plan-2-7.adoc
@@ -1,7 +1,7 @@
 // * documentation/doc-Migration_Toolkit_for_Virtualization/master.adoc
 
 :_mod-docs-content-type: PROCEDURE
-[id="creating-migration-plan_{context}"]
+[id="creating-migration-plan-2-7_{context}"]
 ifdef::provider[]
 = Creating a migration plan starting with a source provider
 

diff --git a/documentation/modules/snip-mtu-value.adoc b/documentation/modules/snip-mtu-value.adoc
@@ -2,5 +2,5 @@
 
 [NOTE]
 ====
-If you input any value of maximum transmission unit (MTU) besides the default value in your migration network, you must also input the same value in the {ocp-short} transfer network that you use For more information about the {ocp-short} transfer network, see xref:creating-migration-plan_provider[Creating a migration plan starting with a source provider] or xref:creating-migration-plan_vms[Creating a migration plan starting with specific VMs].
+If you input any value of maximum transmission unit (MTU) besides the default value in your migration network, you must also input the same value in the {ocp-short} transfer network that you use For more information about the {ocp-short} transfer network, see xref:creating-migration-plan-2-7_provider[Creating a migration plan starting with a source provider] or xref:creating-migration-plan-2-7_vms[Creating a migration plan starting with specific VMs].
 ====
-Original file line number
+Diff line change
@@ Expand Up / @@ -2,5 +2,5 @@ @@
     [NOTE]
     ====
-    If you input any value of maximum transmission unit (MTU) besides the default value in your migration network, you must also input the same value in the {ocp-short} transfer network that you use For more information about the {ocp-short} transfer network, see xref:creating-migration-plan_provider[Creating a migration plan starting with a source provider] or xref:creating-migration-plan_vms[Creating a migration plan starting with specific VMs].
+    If you input any value of maximum transmission unit (MTU) besides the default value in your migration network, you must also input the same value in the {ocp-short} transfer network that you use For more information about the {ocp-short} transfer network, see xref:creating-migration-plan-2-7_provider[Creating a migration plan starting with a source provider] or xref:creating-migration-plan-2-7_vms[Creating a migration plan starting with specific VMs].
     ====