minor

Author: RichardHoch

documentation/modules/new-features-and-enhancements-2-10.adoc

@@ -22,7 +22,8 @@ By disabling VBS on target VMs during the migration of Windows VMs that do not n
 [NOTE]
 ====
 After you migrate your VMs to {virt}, you can re-enable VBS by running the following YAML:
-[source, YAML]
+
+[source,yaml,subs="attributes+"]
 ----
 apiVersion: kubevirt.io/v1
 kind: VirtualMachine
@@ -38,8 +39,6 @@ spec:
               policy: optional
             - name: svm
               policy: optional
-         ... 
-         rest of domain spec
 ----         
 ====
 +

documentation/modules/rn-2-10-6-resolved-issues.adoc

@@ -10,7 +10,7 @@
 Review the resolved issues in this release of {project-short}.
 
 XFSv4 migrations failed::
-{project-short} 2.10.1 was rebased to {rhel-first} 10, which does not support XFS version 4 (XFSv4). As a result, XFSv4 migrations failed for {project-short} 2.10.1-2.10.5. With this release, a new `spec:xfsCompatibility` option is available on the migration plan. When set to `false`, the default setting, the plan uses the standard conversion image. When set to `true`, the plan uses the XFS-compatible conversion image instead of the standard conversion image. 
+{project-short} 2.10.1 was rebased to {rhel-first} 10, which does not support XFS version 4 (XFSv4). As a result, XFSv4 migrations failed for {project-short} 2.10.1-2.10.5. With this release, a new `spec.xfsCompatibility` option is available on the migration plan. When set to `false`, the default setting, the plan uses the standard conversion image. When set to `true`, the plan uses the XFS-compatible conversion image instead of the standard conversion image. 
 +
 [WARNING]
 ====