This is an automated email from the ASF dual-hosted git repository.
jedcunningham pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 9bcf665570 Fix typos in overview.rst (#40061)
9bcf665570 is described below
commit 9bcf665570f3b87eeb5932500c1ae10391ef067d
Author: bangjiehan <[email protected]>
AuthorDate: Wed Jun 5 23:10:02 2024 +0800
Fix typos in overview.rst (#40061)
---
docs/apache-airflow/core-concepts/overview.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/apache-airflow/core-concepts/overview.rst
b/docs/apache-airflow/core-concepts/overview.rst
index 1b1eb8d10f..767b7e8990 100644
--- a/docs/apache-airflow/core-concepts/overview.rst
+++ b/docs/apache-airflow/core-concepts/overview.rst
@@ -52,7 +52,7 @@ A minimal Airflow installation consists of the following
components:
* A *webserver*, which presents a handy user interface to inspect, trigger and
debug the behaviour of
DAGs and tasks.
-* A folder of *DAG files* is read by the *scheduler* to figure out what tasks
to run and when and to
+* A folder of *DAG files*, which is read by the *scheduler* to figure out what
tasks to run and when to
run them.
* A *metadata database*, which airflow components use to store state of
workflows and tasks.
@@ -163,7 +163,7 @@ DAGs and tasks, but cannot author DAGs.
The *DAG files* need to be synchronized between all the components that use
them - *scheduler*,
*triggerer* and *workers*. The *DAG files* can be synchronized by various
mechanisms - typical
-ways how DAGs can be synchronized are described in
:doc:`helm-chart:manage-dags-files` ot our
+ways how DAGs can be synchronized are described in
:doc:`helm-chart:manage-dags-files` of our
Helm Chart documentation. Helm chart is one of the ways how to deploy Airflow
in K8S cluster.
.. image:: ../img/diagram_distributed_airflow_architecture.png
