You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by jo...@apache.org on 2022/06/15 19:24:45 UTC

[airflow] 01/01: Small cleanup of ``get_current_context()`` chapter

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

joshfell pushed a commit to branch josh-fell-patch-1
in repository https://gitbox.apache.org/repos/asf/airflow.git

commit a6d65159553acbfa10a70e767d1a98e59ab6778a
Author: Josh Fell <48...@users.noreply.github.com>
AuthorDate: Wed Jun 15 15:24:21 2022 -0400

    Small cleanup of ``get_current_context()`` chapter
---
 docs/apache-airflow/tutorial_taskflow_api.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/apache-airflow/tutorial_taskflow_api.rst b/docs/apache-airflow/tutorial_taskflow_api.rst
index 8305010a86..00b3e43a2a 100644
--- a/docs/apache-airflow/tutorial_taskflow_api.rst
+++ b/docs/apache-airflow/tutorial_taskflow_api.rst
@@ -451,9 +451,9 @@ With kwargs:
        ti = kwargs["ti"]
        next_ds = kwargs["next_ds"]
 
-Also sometimes you might want to access the context somewhere deep the stack - and you do not want to pass
-the context variables from the task callable. You can do it via ``get_current_context``
-method of the Python operator.
+Also, sometimes you might want to access the context somewhere deep in the stack, but you do not want to pass
+the context variables from the task callable. You can still access execution context via the ``get_current_context``
+method.
 
 .. code-block:: python