ephraimbuddy commented on a change in pull request #17927:
URL: https://github.com/apache/airflow/pull/17927#discussion_r701692314



##########
File path: docs/apache-airflow/concepts/tasks.rst
##########
@@ -56,10 +56,10 @@ Option 3: The @task decorator provided by TaskFlow API, see 
:ref:`concepts:taskf
     def first_task():
         ...
         
-    second_task(first_task()))
+    second_task(first_task())
     
 
-The former two do exactly the same thing and work on any type of Operator, but 
in general we recommend you use the bitshift operators, as they are easier to 
read in most cases. The TaskFlow API likewise connects dependencies between 
tasks, but is tailored to python functions written with the @task-decorator, 
note that the functions here are not executed inline, rather they are converted 
to tasks to be scheduled and sent to Executors, for more information see see 
:ref:`concepts:taskflow`.
+The former two do exactly the same thing and work on any type of Operator, but 
in general we recommend you use the bitshift operators, as they are easier to 
read in most cases. The TaskFlow API likewise connects dependencies between 
tasks, but is tailored to python functions written with the @task-decorator, 
note that the functions here are not executed inline, rather they are converted 
to tasks to be scheduled and sent to Executors, for more information see see 
:ref:`TaskFlow <concepts:taskflow>`.

Review comment:
       ```suggestion
   The former two do exactly the same thing and work on any type of Operator, 
but in general we recommend you use the bitshift operators, as they are easier 
to read in most cases. The TaskFlow API likewise connects dependencies between 
tasks, but is tailored to python functions written with the @task-decorator, 
note that the functions here are not executed inline, rather they are converted 
to tasks to be scheduled and sent to Executors, for more information see 
:ref:`TaskFlow <concepts:taskflow>`.
   ```




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to