review feedback

Author: adwk67

docs/modules/demos/pages/airflow-scheduled-job.adoc

@@ -164,7 +164,15 @@ kubectl exec -n airflow-demo kafka-broker-default-0 -c kafka -- bash -c \
   --producer.config /stackable/config/client.properties'
 ----
 
-The triggerer logs will show that this DAG was fired (logging out the message that we wrote to the topic above):
+The triggerer logs will show that this DAG was fired (logging out the message that we wrote to the topic above).
+You can do this by either displaying the pod logs directly (e.g. if you are using k9s) or by issuing:
+
+[source,bash]
+----
+kubectl logs -n airflow-demo airflow-triggerer-default-0 --tail=30
+----
+
+The logs show that our message was detected, triggering the job:
 
 image::airflow-scheduled-job/airflow_13.png[]
 
@@ -217,7 +225,7 @@ image::airflow-scheduled-job/opa_01.png[]
 Log back into the UI as `admin`.
 The demo also created a third DAG in the ConfigMap, called `dag_factory.py`, which was not mounted to the cluster and therefore does not appear in the UI.
 This DAG can be used to create a number of individual DAGs on-the-fly, thus allowing a certain degree of stress-testing of the DAG scan/register steps (the generated DAGs themselves are trivial and so this approach will not really increase the burden of DAG _parsing_).
-To include this in the list of DAGs (without removing the existing ones), an extra volumeMount is needed, as shown below.
+To show these individual DAGs in the overall list (and to remove the existing ones), adjust the volumeMounts as shown below.
 The patch also sets some environment variables that can be used to change the frequency of certain operations. The descriptions can be found here: https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html[window=_blank].
 
 [source,yaml]