DOC: minor wording improvements

doc/design/application/ApplicationStart.txt

@@ -23,8 +23,8 @@ related to configuration, interdependency and lifecyle.
 
 The Vessel
 ----------
-So we treat all these concerns within a small and self contained structure, called the
-»**Vessel**«, and clearly set apart from all the other layers, services and subsystems.
+So we treat all these concerns within a focused and self contained structure, called
+the »**Vessel**«, and clearly set apart from all the other layers, services and subsystems.
 This dedicated _Application Realm_ is organised around the ``Application main object''.footnote:[
   This is the singleton `vessel::Voyage`, which is triggered by the `main` function
   of the Lumiera Application. The sourcecode is kept in a separate folder 'src/vessel'

doc/design/application/index.txt

@@ -22,7 +22,7 @@ called the »**Vessel**«:
 - it can be invoked from a `main()` function, with an argument parser
 - at source code level, it provides all the types and definitions
   required to express the _binding_ between components
-- _conceptually,_ all layers are encased in the application Vessel
+- _conceptually,_ all layers are encased in the _application vessel_
 - and while the Vessel can not just ``control'' the configuration of parts
   on upper layers, it has to bootstrap their ability to adapt to circumstances.
 

doc/user/intro/intro.txt

@@ -116,7 +116,7 @@ hidden restrictions.
 However, the application strives for a certain degree of internal coherence. +
 Lumiera is not a set of Lego bricks allowing you to build ``just anything''
 (in a clumsy way) -- nor is it the next universal programming platform or
-application framework driven by finite high-level usage stories, where you
+application framework driven by pre-canned success stories, where you
 ``just push the button'' and magic does the rest.