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 2023/03/08 01:27:57 UTC

[airflow] 03/04: Replace blockquote + Note: with RST note in docs (#29709)

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

jedcunningham pushed a commit to branch v2-5-test
in repository https://gitbox.apache.org/repos/asf/airflow.git

commit c18727327a0307806129f2ef24c30bfa132530e4
Author: Vladimir Mikhaylov <38...@users.noreply.github.com>
AuthorDate: Thu Feb 23 11:21:54 2023 +0000

    Replace blockquote + Note: with RST note in docs (#29709)
    
    (cherry picked from commit feb4f40db0170e0711234076adf45753d65aed2f)
---
 docs/apache-airflow/core-concepts/taskflow.rst | 4 ++--
 docs/apache-airflow/core-concepts/xcoms.rst    | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/apache-airflow/core-concepts/taskflow.rst b/docs/apache-airflow/core-concepts/taskflow.rst
index 40fe72dda0..c12ed36c4a 100644
--- a/docs/apache-airflow/core-concepts/taskflow.rst
+++ b/docs/apache-airflow/core-concepts/taskflow.rst
@@ -179,9 +179,9 @@ It is good practice to version the objects that will be used in serialization. T
 so that a version 2 is able to deserialize a version 1. In case you need custom logic
 for deserialization ensure that ``deserialize(data: dict, version: int)`` is specified.
 
-::
+.. note::
 
-  Note: Typing of ``version`` is required and needs to be ``ClassVar[int]``
+  Typing of ``version`` is required and needs to be ``ClassVar[int]``
 
 
 Sensors and the TaskFlow API
diff --git a/docs/apache-airflow/core-concepts/xcoms.rst b/docs/apache-airflow/core-concepts/xcoms.rst
index 3a6dedea28..8cc3ebaf4b 100644
--- a/docs/apache-airflow/core-concepts/xcoms.rst
+++ b/docs/apache-airflow/core-concepts/xcoms.rst
@@ -38,9 +38,9 @@ You can also use XComs in :ref:`templates <concepts:jinja-templating>`::
 
 XComs are a relative of :doc:`variables`, with the main difference being that XComs are per-task-instance and designed for communication within a DAG run, while Variables are global and designed for overall configuration and value sharing.
 
-::
+.. note::
 
-  Note: If the first task run is not succeeded then on every retry task XComs will be cleared to make the task run idempotent.
+  If the first task run is not succeeded then on every retry task XComs will be cleared to make the task run idempotent.
 
 Custom XCom Backends
 --------------------