You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by po...@apache.org on 2021/11/29 17:03:58 UTC

[airflow-site] branch main updated: Fix typo on in Dish use case. (#521)

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

potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 1da8006  Fix typo on in Dish use case. (#521)
1da8006 is described below

commit 1da800628faab964a475df2b7c1e70a33f473f87
Author: Shannon Bradshaw <sh...@arrikto.com>
AuthorDate: Mon Nov 29 12:02:04 2021 -0500

    Fix typo on in Dish use case. (#521)
    
    fix typo
---
 landing-pages/site/content/en/use-cases/dish.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/landing-pages/site/content/en/use-cases/dish.md b/landing-pages/site/content/en/use-cases/dish.md
index 86b0c61..18a4ecc 100644
--- a/landing-pages/site/content/en/use-cases/dish.md
+++ b/landing-pages/site/content/en/use-cases/dish.md
@@ -14,4 +14,4 @@ We faced increasing complexity managing lengthy crontabs with scheduling being a
 Relying on community built and existing hooks and operators to the majority of cloud services we use has allowed us to focus on business outcomes rather than operations.
 
 ##### What are the results?
-Airflow helps us manage many of our pain-points, letting us benefit from the overall ecosystem and community.  We are able to reduce time-to-end delivery of data products by being event-driven in our processing flows (in our first usage, for example, we were able to take out over 2 hours - on average - of various waiting between stages).  Furthermore, we are able to arrive at and iterate on products quicker as a result of not needing as much custom or roll-our-own solutions.  For Our cod [...]
+Airflow helps us manage many of our pain-points, letting us benefit from the overall ecosystem and community.  We are able to reduce time-to-end delivery of data products by being event-driven in our processing flows (in our first usage, for example, we were able to take out over 2 hours - on average - of various waiting between stages).  Furthermore, we are able to arrive at and iterate on products quicker as a result of not needing as much custom or roll-our-own solutions.  Our code ba [...]