format change to existing content

Author: jeana-redhat

modules/ts-capi-migrate-unsupported-features.adoc

@@ -17,7 +17,10 @@ Attempting to use the following configurations might cause a migration to fail o
 This list might not be exhaustive.
 ====
 
-.General limitations
+[id="ts-capi-migrate-unsupported-features-general_{context}"]
+== General limitations
+
+The following limitations apply to all clusters:
 
 * Machine API compute machines cannot migrate to the Cluster API unless the `NodeDeletionTimeout` field uses the Cluster API default value of `10s`.
 
@@ -37,9 +40,12 @@ This list might not be exhaustive.
 * The Cluster API does not support propagating labels or taints from machines to nodes.
 //OCPCLOUD-2861
 
-.{aws-first} limitations
+[id="ts-capi-migrate-unsupported-features-aws_{context}"]
+== {aws-first} limitations
+
+The following limitations apply to {aws-short} clusters:
 
-* Machine API compute machines cannot use {aws-short} load balancers. 
+* Machine API compute machines cannot use {aws-short} load balancers.
 //OCPCLOUD-2709
 
 * The Machine API does not support using the following Amazon EC2 Instance Metadata Service (IMDS) configuration options:
@@ -53,8 +59,8 @@ This list might not be exhaustive.
 If you migrate a Cluster API machine template that uses IMDS configuration options to a Machine API compute machine set, expect the following behaviors:
 +
 --
-** Any machines that the migrated Machine API machine set creates will not have these fields. 
-The underlying instances will not use these settings. 
+** Any machines that the migrated Machine API machine set creates will not have these fields.
+The underlying instances will not use these settings.
 ** Any existing machines that the migrated machine set manages will retain these fields.
 The underlying instances will continue to use these settings.
 --