use desc list for ts content

Author: jeana-redhat

modules/ts-capi-cli-reference-intended-objects.adoc

@@ -11,27 +11,24 @@ For clusters that use the Cluster API, {oc-first} commands prioritize Cluster AP
 This behavior impacts any `oc` command that acts upon any object that is represented in both the Cluster API and the Machine API.
 This explanation uses the `oc delete machine` command, which deletes a machine, as an example.
 
-[discrete]
-=== Cause
+Cause::
 
 When you run an `oc` command, `oc` communicates with the Kube API server to determine which objects to act upon.
 The Kube API server uses the first installed custom resource definition (CRD) it encounters alphabetically when an `oc` command is run.
-
++
 CRDs for Cluster API objects are in the `cluster.x-k8s.io` group, while CRDs for Machine API objects are in the `machine.openshift.io` group.
 Because the letter `c` precedes the letter `m` alphabetically, the Kube API server matches on the Cluster API object CRD.
 As a result, the `oc` command acts upon Cluster API objects.
 
-[discrete]
-=== Consequences
+Consequence::
 
 Due to this behavior, the following unintended outcomes can occur on a cluster that uses the Cluster API:
 
 * For namespaces that contain both types of objects, commands such as `oc get machine` return only Cluster API objects.
 
 * For namespaces that contain only Machine API objects, commands such as `oc get machine` return no results.
 
-[discrete]
-=== Workaround
+Workaround::
 
 You can ensure that `oc` commands act on the type of objects you intend by using the corresponding fully qualified name.