Update typos

Author: rbygrave

docs/features/elasticsearch/index.html

@@ -163,7 +163,7 @@ <h4>Provides something like DB materialised views</h4>
     For example, product pricing might be refreshed every midnight.
   </p>
   <p>
-    ElasticSearch indexes can viewed in a similar way to DB materialised views. They represent
+    ElasticSearch indexes can be viewed in a similar way to DB materialised views. They represent
     a materialised (document orientated) view of the data which can be updated in near real time with each commit
     or updated in a more periodic batch fashion.
   </p>

docs/features/l2cache/index.html

@@ -235,7 +235,7 @@ <h2 id="read-consistency">Eventual consistency</h2>
   <p>
     This means it operates a bit like "replication lag". Data returned from the L2 cache can be (milliseconds) out
     of date. Changes will be made to the cache in a relatively short time (milliseconds) but there isn't the
-    gauruntee of read consistency that our transactional database provides.
+    guarantee of read consistency that our transactional database provides.
   </p>
   <p>
     With Ebean L2 caching there is no attempt to provide transactional read consistency.