[airflow-site] 01/01: Fix newlines on 2.2.0 blog post

[je...@apache.org]

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

jedcunningham pushed a commit to branch fix_2.2.0_blog_post
in repository https://gitbox.apache.org/repos/asf/airflow-site.git

commit e3db328ca64f366341e821cc17ee3724046e3e18
Author: Jed Cunningham <66...@users.noreply.github.com>
AuthorDate: Wed Oct 27 10:55:21 2021 -0600

    Fix newlines on 2.2.0 blog post
---
 landing-pages/site/content/en/blog/airflow-2.2.0/index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/landing-pages/site/content/en/blog/airflow-2.2.0/index.md b/landing-pages/site/content/en/blog/airflow-2.2.0/index.md
index 61632ea..4b564aa 100644
--- a/landing-pages/site/content/en/blog/airflow-2.2.0/index.md
+++ b/landing-pages/site/content/en/blog/airflow-2.2.0/index.md
@@ -29,8 +29,8 @@ To provide more scheduling flexibility, determining when a DAG should run is now
 
 `execution_date` has long been confusing to new Airflowers, so as part of this change a new concept has been added to Airflow to replace it named `data_interval`, which is the period of data that a task should operate on. The following are now available:
 
-`logical_date` (aka `execution_date`)
-`data_interval_start` (same value as `execution_date` for cron)
+`logical_date` (aka `execution_date`) \
+`data_interval_start` (same value as `execution_date` for cron) \
 `data_interval_end` (aka `next_execution_date`)
 
 If you write your own timetables, keep in mind they should be idempotent and fast as they are used in the scheduler to create DagRuns.