This is an automated email from the ASF dual-hosted git repository.

potiuk 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 b03aa6caa0 Fix grammar in dags.rst (#40085)
b03aa6caa0 is described below

commit b03aa6caa076171337054c3adafe74e775d92453
Author: bangjiehan <bangjie...@gmail.com>
AuthorDate: Thu Jun 6 16:03:50 2024 +0800

    Fix grammar in dags.rst (#40085)
    
    * Fix grammer dags.rst
    
    To say "add Operator/Task to the DAG" even though DAG is an argument of 
Operator constructor, and use the word "with statement" explicitly instead of 
context manger to be friendly to Python beginner.
    
    * Fix grammer in dags.rst
    
    Because there is a direction in relationship, it's somehow confuse to say 
that they depend on each other.
    
    * Fix grammer in dags.rst
---
 docs/apache-airflow/core-concepts/dags.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/apache-airflow/core-concepts/dags.rst 
b/docs/apache-airflow/core-concepts/dags.rst
index cd7c199723..70d5663729 100644
--- a/docs/apache-airflow/core-concepts/dags.rst
+++ b/docs/apache-airflow/core-concepts/dags.rst
@@ -34,8 +34,8 @@ The DAG itself doesn't care about *what* is happening inside 
the tasks; it is me
 Declaring a DAG
 ---------------
 
-There are three ways to declare a DAG - either you can use a context manager,
-which will add the DAG to anything inside it implicitly:
+There are three ways to declare a DAG - either you can use ``with`` statement 
(context manager),
+which will add anything inside it to the DAG implicitly:
 
 .. code-block:: python
    :emphasize-lines: 6-10
@@ -108,7 +108,7 @@ Or, you can also use the more explicit ``set_upstream`` and 
``set_downstream`` m
     first_task.set_downstream([second_task, third_task])
     third_task.set_upstream(fourth_task)
 
-There are also shortcuts to declaring more complex dependencies. If you want 
to make two lists of tasks depend on all parts of each other, you can't use 
either of the approaches above, so you need to use ``cross_downstream``::
+There are also shortcuts to declaring more complex dependencies. If you want 
to make a list of tasks depend on another list of tasks, you can't use either 
of the approaches above, so you need to use ``cross_downstream``::
 
     from airflow.models.baseoperator import cross_downstream
 

Reply via email to