Apply suggestions from code review

Co-authored-by: Andrew Kenworthy <[email protected]>

Author: maltesander

docs/modules/demos/pages/argo-cd-git-ops.adoc

@@ -19,7 +19,7 @@ GitOps provides a reliable way to manage infrastructure and applications declara
 and changes are automatically synchronized. This tutorial demonstrates how to deploy Stackable operators and products using {argo-cd}[ArgoCD],
 following Infrastructure-as-Code (IaC) and GitOps principles.
 
-By the end, you will learn how to:
+You will learn how to:
 * Deploy Stackable operators and products via Git-managed manifests.
 * Use Sealed Secrets to securely manage sensitive credentials.
 * Update Airflow DAGs or modify deployments simply by committing to Git.
@@ -33,9 +33,9 @@ All products and manifests are synced and deployed via ArgoCD (except ArgoCD its
 == System requirements
 
 To run this demo, ensure you have the following prerequisites:
-* Kubernetes Cluster (e.g., Kind, Minikube, or managed services like EKS, GKE, AKS)
+* a Kubernetes Cluster (e.g., Kind, Minikube, or managed services like EKS, GKE, AKS).
 * `kubectl`: Installed and configured to access your cluster.
-* Optional: GitHub Account - Required for forking and interacting with the demo repository.
+* Optional: a GitHub account - required for forking and interacting with the demo repository.
 
 Resource requirements for this demo:
 * 15 {k8s-cpu}[cpu units] (core/hyperthread)
@@ -291,24 +291,26 @@ The log files contained in the single folders are the same as the logs shown abo
 
 == Conclusion
 
-This demo illustrates a repeatable blueprint for managing complex data platform components with ArgoCD and GitOps. 
+This demo acts as a blueprint for showing how complex data platform components can be managed with ArgoCD and GitOps. 
 Once familiar with this pattern, you can extend it to multi-cluster environments, add CI/CD pipelines for automated manifest testing, 
-or integrate external secret stores like HashiCorp Vault for production use. This setup lays the foundation for a fully automated, scalable, and secure Kubernetes-based data platform.
+or integrate external secret stores like HashiCorp Vault for production use.
+This setup lays the foundation for a fully automated, scalable, and secure Kubernetes-based data platform.
 
-This tutorial demonstrates how ArgoCD and Stackable integrate to deliver a streamlined GitOps experience:
+This tutorial demonstrates how ArgoCD and Stackable can be combined to deliver a streamlined GitOps experience:
 * All cluster resources and workloads are managed declaratively via Git.
 * ArgoCD continuously ensures the cluster state matches Git.
 * Sealed Secrets provide secure and auditable secret management.
 * Airflow DAG updates occur automatically by committing code to the repository.
 
-This approach scales naturally across environments—development, staging, and production—while reducing manual operations, improving visibility, 
-and enforcing consistency. By adopting GitOps with ArgoCD and Stackable, teams gain a clear, auditable, and automated path from code to production.
+This approach scales naturally across environments - development, staging, and production - while reducing manual operations, improving visibility, 
+and enforcing consistency.
+By adopting GitOps with ArgoCD and Stackable, teams gain a clear, auditable, and automated path from code to production.
 
 Next steps:
 * Explore multi-cluster ApplicationSet deployments to target multiple Kubernetes clusters.
 * Integrate CI workflows to automatically validate and merge manifest updates.
 * Expand beyond Airflow to manage additional Stackable components (e.g., Kafka, Trino, Superset).
-* Experiment with DataOps (e.g., Airflow and Trino)
+* Experiment with DataOps (e.g., Airflow and Trino).
 
 [#interact-with-git-repository]
 == How to interact with ArgoCD, Airflow and the Git repository
@@ -361,7 +363,8 @@ In the `demos/argo-cd-git-ops/manifests/airflow/airflow.yaml` manifest you have
 ----
 
 After adding a new DAG to the folder `demos/argo-cd-git-ops/dags/`, Airflow should pick up the new DAG via git-sync and display it in the UI.
-This may take a while for the syncing process. Refreshing the Airflow UI might help if no DAGs show up.
+This may take a while for the syncing process.
+Refreshing the Airflow UI might help if no DAGs show up.
 
 The synchronisation status of the DAGs can be monitored in via the Airflow scheduler: