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 2022/01/21 00:07:09 UTC

[airflow] 17/23: Fix typo in docs (#20371)

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 330c3657922cbabc8ca096fc0ad29f2f5bf42a99
Author: Daniel van der Ende <da...@gmail.com>
AuthorDate: Fri Dec 17 13:38:19 2021 +0100

    Fix typo in docs (#20371)
    
    Minor typo in the task decorator documentation
    
    (cherry picked from commit 7f6ab06d218973900ead79b74b7c9dca4734ee06)
---
 docs/apache-airflow/howto/create-custom-decorator.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/apache-airflow/howto/create-custom-decorator.rst b/docs/apache-airflow/howto/create-custom-decorator.rst
index b6a9a7b..ebb6c15 100644
--- a/docs/apache-airflow/howto/create-custom-decorator.rst
+++ b/docs/apache-airflow/howto/create-custom-decorator.rst
@@ -53,7 +53,7 @@ tasks. The steps to create and register ``@task.foo`` are:
 
 3. Register your new decorator in get_provider_info of your provider
 
-    Finally, add a key-value ``task-decortor`` to the dict returned from the provider entrypoint. This should be
+    Finally, add a key-value ``task-decorators`` to the dict returned from the provider entrypoint. This should be
     a list with each item containing ``name`` and ``class-name`` keys. When Airflow starts, the
     ``ProviderManager`` class will automatically import this value and ``task.foo`` will work as a new decorator!