merged Prachi's edits for the front and IMC pages

git-svn-id: https://svn.apache.org/repos/asf/ignite/site/branches/ignite-redisign@1875665 13f79535-47bb-0310-9956-ffa450edef68
diff --git a/in-memory-computing.html b/in-memory-computing.html
index 639d91b..51243ae 100644
--- a/in-memory-computing.html
+++ b/in-memory-computing.html
@@ -68,22 +68,17 @@
             store with APIs and libraries designed and optimized for high-performance data processing. Each cluster node
             (physical or virtual machine) contributes its available memory space with CPU cores to the total capacity of
             the cluster. An application interacts with the cluster as a single unit letting the latter shield and manage
-            all the internals related to inter-nodes communication, data distribution and queries processing. The
+            all the internals related to inter-nodes communication, data distribution, and queries processing. The
             cluster
             scales linearly and horizontally to meet the application's data volume and throughput goals.
         </p>
         <p>
             Apache Ignite is a horizontally scalable, fault-tolerant distributed in-memory computing platform used to
-            build
-            real-time applications processing terabytes of data with in-memory speed. Ignite's distributed multi-tier
-            storage
-            scales up and out across available memory and disk resources and can be configured to function as an
-            in-memory
-            cache, in-memory data grid, or in-memory databases. It's compute and data processing APIs are capable of
-            handling
-            large data sets with minimal or no network utilization by applying affinity co-location techniques for data
-            and
-            compute logic.
+            build real-time applications processing terabytes of data with in-memory speed. Ignite's distributed multi-tier
+            storage scales up and out across available memory and disk resources and can be configured to function as an
+            in-memory cache, in-memory data grid, or in-memory database. Its compute and data processing APIs are capable of
+            handling large data sets with minimal or no network utilization by applying affinity co-location techniques for data
+            and compute logic.
         </p>
 
         <div class="jumbotron jumbotron-fluid">
diff --git a/index.html b/index.html
index 377b9ea..7ad8c08 100644
--- a/index.html
+++ b/index.html
@@ -243,7 +243,7 @@
                         </svg>
                         <h3>In-Memory Database</span></h3>
                         <p>
-                            Scale out and up across RAM, NVRAM, Flash and disk with Ignite as an
+                            Scale out and up across RAM, NVRAM, Flash, and disk with Ignite as an
                             in-memory database with distributed multi-tier storage.
                         </p>
                     </a>
@@ -267,8 +267,7 @@
                         <h3>Applications Acceleration & Data Caching</h3>
                         <p>
                             Gain up to 100x acceleration for existing services, applications, and APIs using Apache
-                            Ignite
-                            as a distributed high-performance in-memory layer. Keep underlying databases in sync,
+                            Ignite as a distributed high-performance in-memory layer. Keep underlying databases in sync,
                             using Ignite as an in-memory data grid.
                         </p>
 
@@ -297,11 +296,9 @@
                         <h3>Digital Integration Hub</h3>
                         <p>
                             Consolidate multiple internal systems and external data silos with Apache Ignite as a
-                            low-latency,
-                            high-performance shared data store. Apache Ignite is used to cache and persist data sets
-                            dispersed
-                            across many disjointed external databases and systems providing developers with functionally
-                            rich, unified and consistent APIs.
+                            low-latency, high-performance shared data store. Use Apache Ignite to cache and persist data sets
+                            dispersed across multiple disjointed external databases and systems providing developers with
+                            functionally rich, unified and consistent APIs.
                         </p>
 
                         <a href="/use-cases/dih.html" class="btn btn-primary"
@@ -376,7 +373,7 @@
                             </svg>
                             <h3>Distributed <span>Key-Value</span></h3>
                             <p>
-                                Read, write, transact with high-performant key-value APIs that support JCache
+                                Read, write, and transact with high-performant key-value APIs that support JCache
                                 specification.
                             </p>
                         </a>
@@ -391,7 +388,7 @@
                             <h3>ACID <span>Transactions</span></h3>
 
                             <p>
-                                Execute distributed ACID transactions across memory and disk tiers including relational
+                                Execute distributed ACID transactions across memory and disk tiers, including relational
                                 databases.
                             </p>
                         </a>
@@ -406,7 +403,7 @@
                             <h3>Co-located <span>Processing</span></h3>
 
                             <p>
-                                Eliminate data shuffling by running data- and compute-intensive calculations on
+                                Eliminate data shuffling by running data-intensive and compute-intensive calculations on
                                 cluster nodes.
                             </p>
                         </a>