You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by je...@apache.org on 2021/11/03 21:30:13 UTC
[airflow] 14/17: Docs: Fix typo in ``dag-run.rst`` (#19340)
This is an automated email from the ASF dual-hosted git repository.
jedcunningham pushed a commit to branch v2-2-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
commit ee532d9f7f281cc63f63ffafb4f63a9d2a26e047
Author: axxe <ax...@users.noreply.github.com>
AuthorDate: Mon Nov 1 16:38:19 2021 +0100
Docs: Fix typo in ``dag-run.rst`` (#19340)
(cherry picked from commit d810eaf2d176282f57cd35a1fb97a0604a0cfd24)
---
docs/apache-airflow/dag-run.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/apache-airflow/dag-run.rst b/docs/apache-airflow/dag-run.rst
index 662ae1b..d4d2b77 100644
--- a/docs/apache-airflow/dag-run.rst
+++ b/docs/apache-airflow/dag-run.rst
@@ -76,7 +76,7 @@ of a DAG run, for example, denotes the start of the data interval, not when the
DAG is actually executed.
Similarly, since the ``start_date`` argument for the DAG and its tasks points to
-the same logical date, it marks the start of *the DAG's fist data interval*, not
+the same logical date, it marks the start of *the DAG's first data interval*, not
when tasks in the DAG will start running. In other words, a DAG run will only be
scheduled one interval after ``start_date``.
@@ -151,7 +151,7 @@ if your DAG performs catchup internally.
Backfill
---------
-There can be the case when you may want to run the dag for a specified historical period e.g.,
+There can be the case when you may want to run the DAG for a specified historical period e.g.,
A data filling DAG is created with ``start_date`` **2019-11-21**, but another user requires the output data from a month ago i.e., **2019-10-21**.
This process is known as Backfill.