Some grammatical fixes to the index page

Author: allancaffee

index.html

@@ -100,7 +100,7 @@ <h2>
                 levels that affect scoring, analyzers can be used to
                 control how text gets tokenized into terms, certain
                 fields should not be analyzed at all, and so on... .
-                elasticsearch allows to completely control how a JSON
+                elasticsearch allows you to completely control how a JSON
                 document gets mapped into the search engine on a per
                 type and per index level.
             </p>
@@ -126,9 +126,9 @@ <h2>
             <p>
                 Indexing data is always done using a unique
                 identifier (at the type level). This is very handy
-                since many time we wish to update or delete the
+                since many times we wish to update or delete the
                 actual indexed data, or just GET it. Getting data
-                could not be simpler and all is needed is the index
+                could not be simpler and all that is needed is the index
                 name, the type and the id. What we get back is the
                 <b>actual JSON document</b> used to index the
                 specific data, but please, keep it secret and don't
@@ -324,7 +324,7 @@ <h2>
                 we want to restore to the latest state of the
                 cluster when it comes back up again.
                 elasticsearch provides the gateway module
-                allowing to do just that, think <b>Time
+                allowing you to do just that, think <b>Time
                 Machine for search</b>.
             </p>
 
@@ -333,11 +333,11 @@ <h2>
                 transaction log) can either be recreated from
                 each node local storage (the default), or
                 from a shared storage (like NFS or Amazon
-                S3). When using a shared storage, the state
+                S3). When using shared storage, the state
                 is <b>asynchronously</b> replicated to it.
             </p>
             <p>
-                Moreover, when using shared storage long term
+                Moreover, when using shared storage for long term
                 persistency, the index can be kept completely
                 in memory while still being able to perform
                 full recovery in the event of cluster