review feedback: docs

Author: adwk67

docs/modules/airflow/pages/getting_started/first_steps.adoc

@@ -60,18 +60,19 @@ include::example$getting_started/code/getting_started.sh[tag=install-airflow]
 
 Where:
 
-* `metadata.name` contains the name of the Airflow cluster.
-* `spec.clusterConfig.metadataDatabase` specifies one of the supported database types (in this case, `postgresql`) along with references to the host, database and the secret containing the connection credentials.
+* `metadata.name`: contains the name of the Airflow cluster.
+* `spec.clusterConfig.metadataDatabase`: specifies one of the supported database types (in this case, `postgresql`) along with references to the host, database and the secret containing the connection credentials.
 * the product version of the Docker image provided by Stackable must be set in `spec.image.productVersion`.
 * `spec.celeryExecutors`: deploy executors managed by Airflow's Celery engine.
 Alternatively you can use `kuberenetesExectors` that use Airflow's Kubernetes engine for executor management.
 For more information see https://airflow.apache.org/docs/apache-airflow/stable/executor/index.html#executor-types).
 * `spec.celeryExecutors.celeryResultBackend`: specifies one of the supported database types (in this case, `postgresql`) along with references to the host, database and the secret containing the connection credentials.
 * `spec.celeryExecutors.celeryBrokerUrl`: specifies one of the supported queue/broker types (in this case, `redis`) along with references to the host and the secret containing the connection credentials.
-* the `spec.clusterConfig.loadExamples` key is optional and defaults to `false`.
+* `spec.clusterConfig.loadExamples`: this key is optional and defaults to `false`.
 It is set to `true` here as the example DAGs are used when verifying the installation.
-* the `spec.clusterConfig.exposeConfig` key is optional and defaults to `false`. It is set to `true` only as an aid to verify the configuration and should never be used as such in anything other than test or demo clusters.
-* the secret containing the admin user information must be referenced in `spec.clusterConfig.credentialsSecret`.
+* `spec.clusterConfig.exposeConfig`: this key is optional and defaults to `false`.
+It is set to `true` only as an aid to verify the configuration and should never be used as such in anything other than test or demo clusters.
+* `spec.clusterConfig.credentialsSecret`: specifies the secret containing the Airflow admin user information.
 
 NOTE: The version you need to specify for `spec.image.productVersion` is the desired version of Apache Airflow.
 You can optionally specify the `spec.image.stackableVersion` to a certain release like `23.11.0` but it is recommended to leave it out and use the default provided by the operator.

docs/modules/airflow/pages/usage-guide/db-connect.adoc

@@ -3,7 +3,7 @@
 
 Airflow requires a metadata database for storing e.g. DAG, task and job data.
 The actual connection string is provided by the operator so that the user does not need to remember the exact structure.
-The same database can be accessed using different drivers: this is also handled by the operator, since the context is known (e.g. job metadata vs. queued job metadata) when parsing the resource file.
+The same database can be accessed using different drivers (e.g. job metadata vs. queued job metadata).
 
 == Typed connections