Rename file ("into" -> "to") to avoid case-sensitive issues

Author: adellape

_topic_maps/_topic_map.yml

@@ -525,10 +525,10 @@ Topics:
 - Name: Configuring multi-architecture compute machines on an OpenShift cluster
   Dir: configuring-multi-arch-compute-machines
   Distros: openshift-enterprise
-  Topics: 
-  - Name: About clusters with multi-architecture compute machines 
+  Topics:
+  - Name: About clusters with multi-architecture compute machines
     File: multi-architecture-configuration
-  - Name: Creating a cluster with multi-architecture compute machines on Azure 
+  - Name: Creating a cluster with multi-architecture compute machines on Azure
     File: creating-multi-arch-compute-nodes-azure
   - Name: Creating a cluster with multi-architecture compute machines on AWS
     File: creating-multi-arch-compute-nodes-aws
@@ -3757,7 +3757,7 @@ Topics:
     - Name: Cloning a virtual machine by using a data volume template
       File: virt-cloning-vm-using-datavolumetemplate
     - Name: Cloning a virtual machine disk into a new block storage persistent volume claim
-      File: virt-cloning-vm-disk-into-new-block-storage-pvc
+      File: virt-cloning-vm-disk-to-new-block-storage-pvc
 #A BETTER NAME THAN 'STORAGE 4 U'
   - Name: Virtual machine disks
     Dir: virtual_disks

modules/virt-about-block-pvs.adoc

@@ -2,7 +2,7 @@
 //
 // * virt/virtual_machines/virtual_disks/virt-uploading-local-disk-images-block.adoc
 // * virt/virtual_machines/importing_vms/virt-importing-virtual-machine-images-datavolumes.adoc
-// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-block-storage-pvc.adoc
+// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-to-new-block-storage-pvc.adoc
 
 :_content-type: CONCEPT
 [id="virt-about-block-pvs_{context}"]

modules/virt-about-datavolumes.adoc

@@ -8,7 +8,7 @@
 // * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-datavolume.adoc
 // * virt/virtual_machines/cloning_vms/virt-cloning-vm-using-datavolumetemplate.adoc
 // * virt/virtual_machines/cloning_vms/virt-enabling-user-permissions-to-clone-datavolumes.adoc
-// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-block-storage-pvc.adoc
+// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-to-new-block-storage-pvc.adoc
 // * virt/virtual_machines/importing_vms/virt-importing-virtual-machine-images-datavolumes.adoc
 
 

modules/virt-cdi-supported-operations-matrix.adoc

@@ -5,7 +5,7 @@
 // * virt/virtual_machines/virtual_disks/virt-preparing-cdi-scratch-space.adoc
 // * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-datavolume.adoc
 // * virt/virtual_machines/cloning_vms/virt-cloning-vm-using-datavolumetemplate.adoc
-// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-block-storage-pvc.adoc
+// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-to-new-block-storage-pvc.adoc
 // * virt/virtual_machines/importing_vms/virt-importing-virtual-machine-images-datavolumes.adoc
 // * virt/virtual_machines/importing_vms/virt-importing-virtual-machine-images-datavolumes-block.adoc
 // * virt/virtual_machines/virtual_disks/virt-uploading-local-disk-images-web.adoc

modules/virt-cloning-pvc-of-vm-disk-into-new-datavolume.adoc

@@ -1,9 +1,9 @@
 // Module included in the following assemblies:
 //
 // * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-datavolume.adoc
-// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-block-storage-pvc.adoc
+// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-to-new-block-storage-pvc.adoc
 
-// `blockstorage` conditionals are used (declared in the "*-block" assembly) to separate content 
+// `blockstorage` conditionals are used (declared in the "*-block" assembly) to separate content
 
 :_content-type: PROCEDURE
 [id="virt-cloning-pvc-of-vm-disk-into-new-datavolume_{context}"]
@@ -35,7 +35,7 @@ endif::[]
 namespace of the associated PVC.
 
 . Create a YAML file for a data volume that specifies the name of the
-new data volume, the name and namespace of the source PVC, 
+new data volume, the name and namespace of the source PVC,
 ifdef::blockstorage[]
 `volumeMode: Block` so that an available block PV is used,
 endif::[]

modules/virt-creating-local-block-pv.adoc

@@ -2,7 +2,7 @@
 //
 // * virt/virtual_machines/virtual_disks/virt-uploading-local-disk-images-block.adoc
 // * virt/virtual_machines/importing_vms/virt-importing-virtual-machine-images-datavolumes.adoc
-// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-into-new-block-storage-pvc.adoc
+// * virt/virtual_machines/cloning_vms/virt-cloning-vm-disk-to-new-block-storage-pvc.adoc
 
 :_content-type: PROCEDURE
 [id="virt-creating-local-block-pv_{context}"]