Merge pull request #69254 from tiraboschi/doc_bandwidthPerMigration

CNV-35286: fix bandwidthPerMigration documentation

Author: ousleyp

modules/virt-configuring-live-migration-limits.adoc

@@ -35,7 +35,7 @@ spec:
     parallelOutboundMigrationsPerNode: 2 <4>
     progressTimeout: 150 <5>
 ----
-<1> Bandwidth limit of each migration, in MiB/s or GiB/s. Default: `0`, which is unlimited.
+<1> Bandwidth limit of each migration, where the value is the quantity of bytes per second. For example, a value of `2048Mi` means 2048 MiB/s. Default: `0`, which is unlimited.
 <2> The migration is canceled if it has not completed in this time, in seconds per GiB of memory. For example, a VM with 6GiB memory times out if it has not completed migration in 4800 seconds. If the `Migration Method` is `BlockMigration`, the size of the migrating disks is included in the calculation.
 <3> Number of migrations running in parallel in the cluster. Default: `5`.
 <4> Maximum number of outbound migrations per node. Default: `2`.
@@ -44,4 +44,4 @@ spec:
 [NOTE]
 ====
 You can restore the default value for any `spec.liveMigrationConfig` field by deleting that key/value pair and saving the file. For example, delete `progressTimeout: <value>` to restore the default `progressTimeout: 150`.
-====
+====