Merge pull request #36535 from apinnick/mtc-1.6-compatibility

MTC 1.6 compatibility guidelines

Author: apinnick

modules/migration-compatibility-guidelines.adoc

@@ -10,9 +10,9 @@
 
 You must install the {mtc-full} ({mtc-short}) version that is compatible with your {product-title} version.
 
-// You cannot install {mtc-short} 1.6.x on {product-title} versions 3.7 to 4.5 because the custom resource definition API versions are incompatible.
-//
-// You can migrate workloads from a source cluster with {mtc-short} 1.5.1 to a target cluster with {mtc-short} 1.6 as long as the `MigrationController` custom resource and the {mtc-short} web console are running on the target cluster.
+You cannot install {mtc-short} 1.6.x on {product-title} versions 3.7 to 4.5 because the custom resource definition API versions are incompatible.
+
+You can migrate workloads from a source cluster with {mtc-short} 1.5.1 to a target cluster with {mtc-short} 1.6.x as long as the `MigrationController` custom resource and the {mtc-short} web console are running on the target cluster.
 
 [cols="1,1,2a", options="header"]
 .{product-title} and {mtc-short} compatibility
@@ -26,14 +26,8 @@ Installed manually with the `operator-3.7.yml` file.
 
 Installed manually with the `operator.yml` file.
 
-|4.6 and later versions |1.5.1 |{mtc-full} Operator.
+|4.6 and later |1.6.x^[1]^ |{mtc-full} Operator.
 
 Installed with the Operator Lifecycle Manager.
 |===
-
-// For OCP 4.9 and later
-// |4.9 |1.6.x^[1]^ |{mtc-full} Operator.
-//
-// Installed with the Operator Lifecycle Manager.
-// |===
-// ^1^ Latest z-stream release.
+^1^ Latest z-stream release.