README: clarify libweston purpose/goals.

v2: Rewrap, add a couple of missing words (Pekka).
v3: Use alternative wording (Yong).

Signed-off-by: Emil Velikov <emil.velikov@collabora.com>
Reviewed-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>

README

@@ -73,17 +73,17 @@ http://ometer.com/parallel.html
 Libweston design goals
 ----------------------
 
-The high-level goal of libweston is that what used to be shell plugins
+The high-level goal of libweston is to decouple the compositor from
-will be main executables. Instead of launching 'weston' with various
+the shell implementation (what used to be shell plugins).
-arguments to choose the shell, one would be launching
+
-'weston-desktop', 'weston-ivi', 'orbital', etc. The main executable
+Thus, instead of launching 'weston' with various arguments to choose the
-(the hosting program) links to libweston for a fundamental compositor
+shell, one would launch the shell itself, eg. 'weston-desktop',
-implementation. Libweston is also intended for use by other projects
+'weston-ivi', 'orbital',etc. The main executable (the hosting program)
-who want to create new "Wayland WMs".
+will implement the shell, while libweston will be used for a fundamental
-
+compositor implementation.
-The libweston API/ABI will be separating the shell logic and main
+
-program from the rest of the "Weston compositor" (libweston
+Libweston is also intended for use by other project developers who want
-internals).
+to create new "Wayland WMs".
 
 Details: