Edit intro etc. for clarity

At least I hope so.

site/getstarted.md

@@ -53,10 +53,11 @@ what we need to tell Flux so it can reach them.
 
 `fluxd` is a container that performs two functions:
 
-* It listens to a docker daemon running on the same host to find out
-when service containers are started and stopped.
-* It routes connections and requests from client containers on the same
-hosts to the appropriate service containers.
+* It listens to a docker daemon running on the host to find out when
+  containers that are service instances are started and stopped.
+
+* It routes connections and requests from client containers on the
+  host to service instances.
 
 It's necessary to pass a few options to `docker run` to give `fluxd`
 the privileges it needs.  If you were deploying flux as part of a

site/index.md

@@ -1,30 +1,30 @@
 ---
 layout: page
-title: Weave Flux Documentation
+title: Weave Flux documentation
 ---
 
-Flux is a service routing layer that lets you control how containers
-are accessed as services, without dictating how the containers are
-created, allocated to hosts, or otherwise orchestrated.
+Flux is a service routing layer for containers.
 
 Once upon a time, most web applications had a simple architecture: a
 load balancer relayed requests to a single uniform tier of application
 servers, which connected to a database.  Assembling the pieces of such
 an architecture and troubleshooting any problems was relatively
-straightforward.  These days, many projects are using microservices
-instead.  But the benefits of microservices come at the cost of a more
-complicated architecture.  Flux aims to help tame this complexity.
+straightforward.
 
-* When there's a problem, it can be hard to identify which
-microservice is at fault.  Flux can show you information about the
+These days, many projects are using microservices instead.  But the
+benefits of microservices come at the cost of a more complicated
+architecture.  Flux aims to help tame this complexity.
+
+*When there's a problem, it can be hard to identify which
+microservice is at fault*. Flux can show you information about the
 requests between microservices, to help isolate problems.
 
-* Flux provides lightweight client-side proxying, to load balance
-requests between microservices.  This avoids the additional latency or
+*Flux provides lightweight client-side proxying, to load balance
+requests between microservices*.  This avoids the additional latency or
 the configuration burden of using traditional load balancers for this
 task.
 
-* Flux is container-aware.  It integrates with Docker, and will
+*Flux is container-aware*.  It integrates with Docker, and will
 automatically reconfigure itself as containers are started and
 stopped.
 
@@ -35,7 +35,7 @@ With Flux's service routing layer, you can:
 
 * Do rolling upgrades and blue-green deployments of microservices
 
-* Automatically configure an ingress load balancer (currently nginx is
+* Automatically configure an ingress load balancer (currently Nginx is
   supported)
 
 Flux is not a platform, and does not require changes to your