update with CQA DITA compliance

Author: jldohmann

modules/images-triggering-updates-imagestream-changes-kubernetes-about.adoc

@@ -6,6 +6,9 @@
 [id="images-triggering-updates-imagestream-changes-kubernetes-about_{context}"]
 = Triggering Kubernetes resources
 
+[role="_abstract"]
+To enable Kubernetes resources, such as `Deployments` and `StatefulSets`, to seamlessly consume new image versions, configure image stream change triggers in {product-title}. This ensures your application deployments are automatically updated when the associated image stream detects a change.
+
 Kubernetes resources do not have fields for triggering, unlike deployment and build configurations, which include as part of their API definition a set of fields for controlling triggers. Instead, you can use annotations in {product-title} to request triggering.
 
 The annotation is defined as follows:
@@ -20,22 +23,24 @@ metadata:
       [
        {
          "from": {
-           "kind": "ImageStreamTag", <1>
-           "name": "example:latest", <2>
-           "namespace": "myapp" <3>
+           "kind": "ImageStreamTag",
+           "name": "example:latest",
+           "namespace": "myapp"
          },
-         "fieldPath": "spec.template.spec.containers[?(@.name==\"web\")].image", <4>
-         "paused": false <5>
+         "fieldPath": "spec.template.spec.containers[?(@.name==\"web\")].image",
+         "paused": false
        },
       # ...
       ]
 # ...
 ----
-<1> Required: `kind` is the resource to trigger from must be `ImageStreamTag`.
-<2> Required: `name` must be the name of an image stream tag.
-<3> Optional: `namespace` defaults to the namespace of the object.
-<4> Required: `fieldPath` is the JSON path to change. This field is limited and accepts only a JSON path expression that precisely matches a container by ID or index. For pods, the JSON path is `spec.containers[?(@.name='web')].image`.
-<5> Optional: `paused` is whether or not the trigger is paused, and the default value is `false`. Set `paused` to `true` to temporarily disable this trigger.
+where:
+
+`kind`:: Specifies the resource to trigger from, and must have the value `ImageStreamTag`.
+`name`:: Specifies the name of an image stream tag.
+`namespace`:: Specifies the namespace of the object. This field is optional.
+`fieldPath`:: Specifies the JSON path to change. This field is limited and accepts only a JSON path expression that precisely matches a container by ID or index. For pods, the JSON path is `spec.containers[?(@.name='web')].image`.
+`paused`:: Specifies whether or not the trigger is paused. This field is optional, and defaults to the value `false`. Set the value to `true` to temporarily disable this trigger.
 
 When one of the core Kubernetes resources contains both a pod template and this annotation, {product-title} attempts to update the object by using the image currently associated with the image stream tag that is referenced by trigger. The update is performed against the `fieldPath` specified.
 

modules/images-triggering-updates-imagestream-changes-kubernetes-cli.adoc

@@ -7,6 +7,9 @@
 [id="images-triggering-updates-imagestream-changes-kubernetes-cli_{context}"]
 = Setting the image trigger on Kubernetes resources
 
+[role="_abstract"]
+To enable automatic updates for your deployed applications managed by Kubernetes, use the command-line interface (CLI) to set an image stream change trigger on Kubernetes resources. This ensures that resources, like `Deployments` and `StatefulSets`, are automatically invoked when a new version of an upstream image is available.
+
 When adding an image trigger to deployments, you can use the `oc set triggers` command. For example, the sample command in this procedure adds an image change trigger to the deployment named `example` so that when the `example:latest` image stream tag is updated, the `web` container inside the deployment updates with the new image value. This command sets the correct `image.openshift.io/triggers` annotation on the deployment resource.
 
 .Procedure