docs(demo/airflow-scheduled-job): Update instructions (#378)

* docs(demo/airflow-scheduled-job): Simplify install

Otherwise it makes the rest of the demo confusing

* docs(demo/airflow-scheduled-job): Update instructions

Author: NickLarsenNZ

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

@@ -3,12 +3,11 @@
 
 Install this demo on an existing Kubernetes cluster:
 
-[source,console]
-----
-$ stackablectl demo install airflow-scheduled-job
-----
-
-You can also deploy it to a specific namespace (the namespace `airflow-demo` will be assumed in this guide):
+[NOTE]
+====
+The namespace `airflow-demo` will be assumed in this guide.
+It will be created if it doesn't exist.
+====
 
 [source,console]
 ----
@@ -225,7 +224,7 @@ image::airflow-scheduled-job/airflow_17.png[]
 
 Click on the DAG, switching to the task view.
 This DAG uses a deferrable operator which, in conjunction with the triggerer process, "offloads" the DAG from its worker for a specfic period of time, before being picked up and again and executed.
-You will see the task cycle through the following states:
+From the Task Instances view (under Dags), you will see the task cycle through the following states:
 
 image::airflow-scheduled-job/deferrable_01_running.png[]
 image::airflow-scheduled-job/deferrable_02_queued.png[]
@@ -315,13 +314,15 @@ spec:
         envOverrides: *envOverrides
 ----
 
-THe patch can be applied like this:
+The patch can be applied like this:
 
 [source,console]
 ----
 kubectl patch airflowcluster airflow --type="merge" --patch-file stacks/airflow/patch_airflow.yaml -n airflow-demo
 ----
 
+Wait for Airflow to come back up, and you should now see the generated DAGs.
+
 [NOTE]
 ====
 The scheduled job runs every minute and so an instance of it may be running while the scheduler is being re-started as a result of the patch, in which case that instance may fail.