~

README.md

 glngn server is a business process as a service rapid development system. Conceptually similar to
-Microsoft Access or Apple FileMaker (but scalable) for event sourced business services. In addition
-to a library, a standalone application is provided that is useful with minimal ceremony. This can be
-customized with a simple API. As well as deployed to a kubernetes cluster should those advantages be
-required.
+Microsoft Access or Apple FileMaker (but scalable!) for event sourced business services. A standalone
+application is provided that is useful with minimal ceremony. In addition to an approachable,
+incremental extension API.  With a bit more ceremony these solution can be deployed to a kubernetes
+cluster, should those advantages be required.
 
-The implementation and APIs might be familiar to Scala service developers. To a large degree, glngn
-server is a friendly, constrained, pre-configured typed akka plus ZIO server.
+The implementation and extension API might be familiar to Scala service developers. To a large
+degree, glngn server is a friendly, constrained, pre-configured typed akka plus ZIO server.
 
-- support available from the [DogHeadBone LLC](mailto:support@dogheadbone.com) company
-- Painlessly capture business process data
+- Support available from the [DogHeadBone LLC](mailto:support@dogheadbone.com) company
+- Painlessly capture events
 - Plain, typed akka and zio runtimes are provided. Use whichever suites your domain
-- Simplified event persistence
+- Simplified persistence
 - Simplified Kubernetes (k8s) cluster deployments. In addition to some custom automation, the akka
-  management tools are included
-- automatic OpenAPI schema
+  management tools are included. OpenShift is also supported.
+- Friendly REST interace with an OpenAPI schema
 
-Sound good so far? Cool! Let's start with basic, interactive usage of the standalone server.
+Sound good so far? Cool! Let's start with basic, interactive usage of the standalone application.
 
-To start with running a customized server skip to [customization](#customization).
+To start with the extension API and running a customized server skip to
+[customization](#customization).
 
-# Standalone
+# Standalone Application
 
 prerequisites:
 
@@ -138,7 +139,7 @@ TODO: show dynamic instantiation of a service fragment under a group
 
 # Customization
 
-glngn server provided a programmable application experience: All dynamic 
+glngn server provided a programmable application experience: All dynamic
 operations described above can also be declared via Scala code. New service
 fragments can be added as well.
 
@@ -146,12 +147,12 @@ fragments can be added as well.
 
 The default build uses an assembly, non-modular, glngn server library. This
 provides a low complexity build for extensions that only need the included
-libraries. See [the API documentation here](http://docs.glngn.com/latest/api/) 
+libraries. See [the API documentation here](http://docs.glngn.com/latest/api/)
 for reference.
 
-Assembly distributions are considered "a headache the moment your users step 
+Assembly distributions are considered "a headache the moment your users step
 outside of Hello World". However, with glngn server those simple cases are often
-useful and the convinience is valuable. 
+useful and the convinience is valuable.
 
 In addition, the provided glngn server assembly has a high degree of assurance
 that is difficult to provide with a modular build (at this time). The
@@ -164,8 +165,8 @@ invalidates the prior assurances to a degree.
 
 ## Using sbt-glngn plugin
 
-Using scalac directly is nice but the recommendation is to use the `sbt-glngn` 
-sbt plugin. Very little code is required to start using this plugin. The 
+Using scalac directly is nice but the recommendation is to use the `sbt-glngn`
+sbt plugin. Very little code is required to start using this plugin. The
 interfaces provided also support easily moving to the modular build.
 
 When the additional complexity of a modular build is appropriate, of course. :)