[incubator-wayang-website] branch asf-site updated: Lastest site built on successful travis build 36 auto-pushed to github

[be...@apache.org]

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

bertty pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-wayang-website.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 78065d0  Lastest site built on successful travis build 36 auto-pushed to github
78065d0 is described below

commit 78065d05f89de10499e40cd8f30e7375ad3fbdd7
Author: Travis CI User <tr...@example.org>
AuthorDate: Mon Aug 23 09:00:27 2021 +0000

    Lastest site built on successful travis build 36 auto-pushed to github
---
 index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/index.html b/index.html
index 7724328..5efd45b 100644
--- a/index.html
+++ b/index.html
@@ -333,12 +333,12 @@ DATA PROCESSING SYSTEM
 </section>
 <section class="container-fluid p-0 mt-n3 mb-n3" style="background-color:#ffffff !important ">
     <div class="container">
-        <div class="d-flex justify-content-center tx-shadow">
+        <div class="d-flex justify-content-center">
             <p class="display-4 p-2">
                 Why is Apache Wayang faster as other, modern frameworks?
             </p>
         </div>
-        <div class="d-flex justify-content-center tx-shadow">
+        <div class="d-flex justify-content-center">
             <p class="lead p-2">
                 <strong>
                     Apache Wayang uses internal optimization patterns to detect the best possible combination of computation and nodes. We know, just adding more nodes into a cluster doesn't mean more speed; each additional node has several tradeoffs, be it shuffle or communication bottlenecks.