clarifies that Weave Cloud is not just the UI for Flux

site/how-it-works.md

@@ -3,8 +3,8 @@ title: How Weave Flux Works
 menu_order: 20
 ---
 
-This page describes the goals of flux, how it achieves them and 
-significant architectural decisions. It is intentionally high level 
+This page describes the goals of flux, how it achieves them and
+significant architectural decisions. It is intentionally high level
 to prevent it from being out of date too quickly.
 
 # Goals
@@ -23,9 +23,9 @@ with an orchestrator (which is a common source of accidental failure) or
 with the systems that ensure that the orchestrator is in a working
 state.
 
-Flux also provides a CLI and a UI (in Weave Cloud) to perform these
-operations manually. Flux is flexible enough to fit into any development
-process.
+Flux provides a CLI (`fluxctl`) and a UI (as a compoent of Weave Cloud)
+to perform these operations manually. Flux is flexible enough to fit
+into any development process.
 
 # Implementation Overview
 
@@ -70,10 +70,10 @@ In order to access private registries, credentials may be required.
 
 ## Deployment of Images
 
-Flux will only deploy different images. It will not re-deploy images 
+Flux will only deploy different images. It will not re-deploy images
 with the same tag.
 
-Once a list of new images have been established, it will alter the 
+Once a list of new images have been established, it will alter the
 configuration of the cluster to deploy the new images.
 
 Images can be "locked" to a specific version. "locked" images won't be