[airflow] 06/23: FIx formatting of Dataset inlet/outlet note in TaskFlow concepts (#29678)

[ep...@apache.org]

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

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

commit 18bda7a70f183c2e28b2781abc622faba4da7cf8
Author: Josh Fell <48...@users.noreply.github.com>
AuthorDate: Tue Feb 21 16:37:31 2023 -0500

    FIx formatting of Dataset inlet/outlet note in TaskFlow concepts (#29678)
    
    (cherry picked from commit 9de301da2a44385f57be5407e80e16ee376f3d39)
---
 docs/apache-airflow/core-concepts/taskflow.rst | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/docs/apache-airflow/core-concepts/taskflow.rst b/docs/apache-airflow/core-concepts/taskflow.rst
index 97847455ab..40fe72dda0 100644
--- a/docs/apache-airflow/core-concepts/taskflow.rst
+++ b/docs/apache-airflow/core-concepts/taskflow.rst
@@ -91,9 +91,10 @@ need to be able to be serialized. Airflow out of the box supports all built-in t
 supports objects that are decorated with ``@dataclass`` or ``@attr.define``. The following example shows the use of
 a ``Dataset``, which is ``@attr.define`` decorated, together with TaskFlow.
 
-::
+.. note::
+
+    An additional benefit of using ``Dataset`` is that it automatically registers as an ``inlet`` in case it is used as an input argument. It also auto registers as an ``outlet`` if the return value of your task is a ``dataset`` or a ``list[Dataset]]``.
 
-  Note: An additional benefit of using ``Dataset`` is that it automatically registers as an ``inlet`` in case it is used as an input argument. It also auto registers as an ``outlet`` if the return value of your task is a ``dataset`` or a ``list[Dataset]]``.
 
 .. code-block:: python