DITA migration changes (2.6): CAG Ch 16

downstream/assemblies/platform/assembly-controller-awx-manage-utility.adoc

@@ -8,13 +8,16 @@ Use the `awx-manage` utility to access detailed internal information of {Control
 Commands for `awx-manage` must run as the `awx` user only.
 
 include::platform/ref-controller-inventory-import.adoc[leveloffset=+1]
+
 include::platform/ref-controller-cleanup-old-data.adoc[leveloffset=+1]
+
 include::platform/ref-controller-cluster-management.adoc[leveloffset=+1]
+
 //include::platform/ref-controller-token-session-management.adoc[leveloffset=+1]
 //include::platform/ref-controller-create-oauth2-token.adoc[leveloffset=+2]
 //include::platform/ref-controller-revoke-oauth2-token.adoc[leveloffset=+2]
 //include::platform/ref-controller-clear-tokens.adoc[leveloffset=+2]
 //include::platform/ref-controller-expire-sessions.adoc[leveloffset=+2]
 //include::platform/ref-controller-clear-sessions.adoc[leveloffset=+2]
-include::platform/ref-controller-analytics-gathering.adoc[leveloffset=+1]
 
+include::platform/ref-controller-analytics-gathering.adoc[leveloffset=+1]

downstream/modules/platform/ref-controller-cleanup-old-data.adoc

@@ -7,16 +7,10 @@
 `awx-manage` has a variety of commands used to clean old data from {ControllerName}. 
 {ControllerNameStart} administrators can use the {ControllerName} *Management Jobs* interface for access or use the command line.
 
-[literal, options="nowrap" subs="+attributes"]
-----
-awx-manage cleanup_jobs [--help]
-----
+* `awx-manage cleanup_jobs [--help]`
 
 This permanently deletes the job details and job output for jobs older than a specified number of days.
 
-[literal, options="nowrap" subs="+attributes"]
-----
-awx-manage cleanup_activitystream [--help]
-----
+* `awx-manage cleanup_activitystream [--help]`
 
 This permanently deletes any [Activity stream] data older than a specific number of days.

downstream/modules/platform/ref-controller-cluster-management.adoc

@@ -4,7 +4,7 @@
 
 = Cluster management
 
-For more information about the `awx-manage provision_instance` and `awx-manage deprovision_instance` commands, see xref:controller-clustering[Clustering].
+For more information about the `awx-manage provision_instance` and `awx-manage deprovision_instance` commands, see link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.6/html/configuring_automation_execution/controller-clustering[Clustering].
 
 [NOTE]
 ====

downstream/modules/platform/ref-controller-inventory-import.adoc

@@ -10,19 +10,13 @@ To use `awx-manage` properly, you must first create an inventory in {ControllerN
 
 For help with `awx-manage`, run the following command: 
 
-[literal, options="nowrap" subs="+attributes"]
-----
-awx-manage inventory_import [--help]
-----
+`awx-manage inventory_import [--help]`
 
 The `inventory_import` command synchronizes an {ControllerName} inventory object with a text-based inventory file, dynamic inventory script, or a directory of one or more, as supported by core Ansible.
 
 When running this command, specify either an `--inventory-id` or `--inventory-name`, and the path to the Ansible inventory source (`--source`).
 
-[literal, options="nowrap" subs="+attributes"]
-----
-awx-manage inventory_import --source=/ansible/inventory/ --inventory-id=1 
-----
+`awx-manage inventory_import --source=/ansible/inventory/ --inventory-id=1` 
 
 By default, inventory data already stored in {ControllerName} blends with data from the external source. 
 
@@ -32,10 +26,7 @@ To specify that any existing hosts get variable data exclusively from the `--sou
 
 The default behavior adds any new variables from the external source, overwriting keys that already exist, but preserving any variables that were not sourced from the external data source.
 
-[literal, options="nowrap" subs="+attributes"]
-----
-awx-manage inventory_import --source=/ansible/inventory/ --inventory-id=1 --overwrite
-----
+`awx-manage inventory_import --source=/ansible/inventory/ --inventory-id=1 --overwrite`
 
 [NOTE]
 ====