You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ignite.apache.org by dm...@apache.org on 2019/01/24 21:03:20 UTC

svn commit: r1852073 - /ignite/site/trunk/provenusecases.html

Author: dmagda
Date: Thu Jan 24 21:03:20 2019
New Revision: 1852073

URL: http://svn.apache.org/viewvc?rev=1852073&view=rev
Log:
fixed typo

Modified:
    ignite/site/trunk/provenusecases.html

Modified: ignite/site/trunk/provenusecases.html
URL: http://svn.apache.org/viewvc/ignite/site/trunk/provenusecases.html?rev=1852073&r1=1852072&r2=1852073&view=diff
==============================================================================
--- ignite/site/trunk/provenusecases.html (original)
+++ ignite/site/trunk/provenusecases.html Thu Jan 24 21:03:20 2019
@@ -299,7 +299,7 @@ under the License.
                         explains why Yahoo! Japan chose Apache Ignite as their solution for a highly scalable caching system that
                         can process tens of thousands requests per second. SQL queries were performed via thin clients since they do not require a standard
                         topology join and therefore are easier to be handled through container services. After a successful POC, Ignite fully met their
-                        requirements and was quicly rolled into production.
+                        requirements and was quickly rolled into production.
                     </p>
                 </div>
                 <p>&nbsp;</p>