Editing controller files for DITA (ansible#3811) (ansible#3812)

Using automation execution UI and modular compliance chapter 27

https://issues.redhat.com/browse/AAP-45161

Affects `titles/controller-user-guide`

Author: EMcWhinn

downstream/assemblies/platform/assembly-ug-controller-work-with-webhooks.adoc

@@ -1,11 +1,13 @@
+:_mod-docs-content-type: ASSEMBLY
+
 [id="controller-work-with-webhooks"]
 
 = Working with Webhooks
 
-A Webhook enables you to execute specified commands between applications over the web. 
+Use webhooks to run specified commands between applications over the web. 
 {ControllerNameStart} currently provides webhook integration with GitHub and GitLab. 
 
-Set up a webhook using the following services:
+Set up a webhook by using the following services:
 
 * xref:controller-set-up-github-webhook[Setting up a GitHub webhook]
 * xref:controller-set-up-gitlab-webhook[Setting up a GitLab webhook]
@@ -17,5 +19,7 @@ Receiving another kind of event results in messages such as the following in the
 `awx.main.models.mixins Webhook event did not have a status API endpoint associated, skipping.`
 
 include::platform/proc-controller-set-up-github-webhook.adoc[leveloffset=+1]
+
 include::platform/proc-controller-set-up-gitlab-webhook.adoc[leveloffset=+1]
+
 include::platform/proc-controller-view-payload-output.adoc[leveloffset=+1]

downstream/modules/platform/proc-controller-set-up-github-webhook.adoc

@@ -1,3 +1,5 @@
+:_mod-docs-content-type: PROCEDURE
+
 [id="controller-set-up-github-webhook"]
 
 = Setting up a GitHub webhook
@@ -12,7 +14,7 @@ If you do not need {ControllerName} to post job statuses back to the webhook ser
 .. In the profile settings of your GitHub account, select *Settings*.
 .. From the navigation panel, select menu:<> Developer Settings[].
 .. On the *Developer Settings* page, select *Personal access tokens*.
-.. Select *Tokens(classic)*
+.. Select *Tokens (classic)*
 .. From the *Personal access tokens* screen, click btn:[Generate a personal access token].
 .. When prompted, enter your GitHub account password to continue.
 .. In the *Note* field, enter a brief description about what this PAT is used for.
@@ -60,4 +62,4 @@ Click a webhook, to go to the *Manage webhook* screen.
 . Scroll to view the delivery attempts made to your webhook and whether they succeeded or failed.
 
 .Additional resources
-For more information, see the link:https://docs.github.com/en/webhooks[Webhooks documentation].
+* link:https://docs.github.com/en/webhooks[Webhooks documentation]

downstream/modules/platform/proc-controller-set-up-gitlab-webhook.adoc

@@ -1,3 +1,5 @@
+:_mod-docs-content-type: PROCEDURE
+
 [id="controller-set-up-gitlab-webhook"]
 
 = Setting up a GitLab webhook
@@ -51,4 +53,4 @@ To have job status (pending, error, success) sent back to GitLab, you must selec
 Testing a webhook event displays the results on each page whether it succeeded or failed.
 
 .Additional resources
-For more information, see link:https://docs.gitlab.com/ee/user/project/integrations/webhooks.html[Webhooks].
+* link:https://docs.gitlab.com/ee/user/project/integrations/webhooks.html[Webhooks]

downstream/modules/platform/proc-controller-view-payload-output.adoc

@@ -1,3 +1,5 @@
+:_mod-docs-content-type: PROCEDURE
+
 [id="controller-view-payload-output"]
 
 = Viewing the payload output
@@ -10,6 +12,6 @@ You can view the entire payload exposed as an extra variable.
 . Select the job template with the webhook enabled.
 . Select the *Details* tab.
 . In the *Extra Variables* field, view the payload output from the `awx_webhook_payload` variable, as shown in the following example:
-
++
 image::ug-webhooks-jobs-extra-vars-payload.png[Webhooks extra variables payload]
 image::ug-webhooks-jobs-extra-vars-payload-expanded.png[Webhook extra variables payload expanded]