Update 02_introduction.adoc

Modernized the features list, corrected some grammar

Author: rstafford

prj/docs/about/02_introduction.adoc

@@ -14,19 +14,19 @@ First and foremost, Coherence provides a fundamental service that is responsible
 common denominator / building block for all other Coherence services.
 This service, referred to as 'service 0' internally, ensures the mesh of members is maintained and responsive,
 taking action to collaboratively evict, shun, or in some cases voluntarily depart the cluster when deemed necessary.
-As members join and leave the cluster, other Coherence services are notified thus allows those services to react accordingly.
+As members join and leave the cluster, other Coherence services are notified thus allowing those services to react accordingly.
 
-NOTE: This part of the Coherence product has been in production for 10+ years, being the subject of some extensive and
+NOTE: This part of the Coherence product has been in production for 20+ years, and has been the subject of some extensive and
 imaginative testing.
 While it has been discussed here it certainly is not something that customers, generally, interact with directly but is
 valuable to be aware of.
 
-Coherence services build on top of the clustering service, with the key implementations to be aware of are
+Coherence services build on top of the clustering service, with the key implementations to be aware of being
 PartitionedService, InvocationService, and ProxyService.
 
 In the majority of cases customers will deal with caches;
 a cache will be represented by an implementation of `NamedCache<K,V>`.
-Cache is an unfortunate name, as many Coherence customers use Coherence as a system-of-record rather than a lossy store of data.
+Cache is an unfortunate name, as many customers use Coherence as a system-of-record rather than a lossy store of data.
 A cache is hosted by a service, generally the PartitionedService, and is the entry point to storing, retrieving,
 aggregating, querying, and streaming data.
 There are a number of features that caches provide:
@@ -42,11 +42,14 @@ There are a number of features that caches provide:
 * *Data local processing* - an ability to send a function to the relevant storage node to execute processing logic for the appropriate entries with exclusive access
 * *Partition local transactions* - an ability to perform scalable transactions by associating data (thus being on the same partition) and manipulating other entries on the same partition potentially across caches
 * *Non-blocking / async NamedCache API*
-* *C{pp} and .NET clients* - access the same NamedCache API from either C{pp} or .NET
+* *Polyglot clients* - access the same NamedCache API from C{pp}, Go, Java, JavaScript, .NET, or Python
 * *Portable Object Format* - optimized serialization format, with the ability to navigate the serialized form for optimized queries, aggregations, or data processing
 * *Integration with Databases* - Database & third party data integration with CacheStores including both synchronous or asynchronous writes
 * *CohQL* - ansi-style query language with a console for adhoc queries
 * *Topics* - distributed topics implementation offering pub/sub messaging with the storage capacity the cluster and parallelizable subscribers
+* *Repository API* - a framework implementing the Repository pattern from Domain-Driven Design, abstracting persistent storage implementation from application code, with advanced features like support for pagination, projections, streaming, and updating in-place
+* *Microservices integration* - broad and close integration with Helidon, Micronaut, and Spring for developing microservices applications using Coherence as a data source or cache
+* *coherence-concurrent* - Coherence-backed implementations of types from the `java.util.concurrent` package enabling distributed process coordination through the grid
 
 There are also a number of non-functional features that Coherence provides:
 
@@ -59,7 +62,7 @@ There are also a number of non-functional features that Coherence provides:
 * *Lossy redundancy* - ability to reduce the redundancy guarantee by making backups and/or persistence asynchronous from a client perspective
 * *Single Mangement View* - provides insight into the cluster  with a single JMX server that provides a view of all members of the cluster
 * *Management over REST* - all JMX data and operations can be performed over REST, including cluster wide thread dumps and heapdumps
-* *Non-cluster Access* - access to the cluster from the outside via proxies, for distant (high latency) clients and for non-java languages such as C{pp} and .NET
+* *Non-cluster Access* - access to the cluster from the outside via proxies, for distant (high latency) clients and for non-Java languages such as C{pp}, Go, JavaScript, .NET, and Python
 * *Kubernetes friendly* - seamlessly and safely deploy applications to k8s with our own https://github.com/oracle/coherence-operator[operator]