[2/4] incubator-brooklyn git commit: Updates to "Quick Overview of Concepts page" following Richard Downer's comments in https://github.com/apache/incubator-brooklyn/pull/966.

[he...@apache.org]

Updates to "Quick Overview of Concepts page" following Richard Downer's comments in https://github.com/apache/incubator-brooklyn/pull/966.


Project: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/commit/28eed640
Tree: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/tree/28eed640
Diff: http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/diff/28eed640

Branch: refs/heads/master
Commit: 28eed6404a340718767e605ddc09889f75db4c58
Parents: 477da36
Author: Geoff Macartney <ge...@cloudsoftcorp.com>
Authored: Mon Oct 19 18:13:38 2015 +0100
Committer: Geoff Macartney <ge...@cloudsoftcorp.com>
Committed: Mon Oct 19 18:13:38 2015 +0100

----------------------------------------------------------------------
 docs/guide/start/concept-quickstart.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-brooklyn/blob/28eed640/docs/guide/start/concept-quickstart.md
----------------------------------------------------------------------
diff --git a/docs/guide/start/concept-quickstart.md b/docs/guide/start/concept-quickstart.md
index 5ef6477..0e862a0 100644
--- a/docs/guide/start/concept-quickstart.md
+++ b/docs/guide/start/concept-quickstart.md
@@ -4,12 +4,12 @@ layout: website-normal
 menu_parent: index.md
 ---
 
-The following section gives a quick summary of the main Brooklyn concepts you will encounter in Getting Started.  For later investigation of these concepts see [The Theory Behind Brookln]({{site.path.website}}/learnmore/theory.html), and the detailed description in [Brooklyn Concepts]({{site.path.guide}}/concepts/).
+The following section gives a quick summary of the main Brooklyn concepts you will encounter in Getting Started.  For later investigation of these concepts see [The Theory Behind Brooklyn]({{site.path.website}}/learnmore/theory.html), and the detailed description in [Brooklyn Concepts]({{site.path.guide}}/concepts/).
 
 Having examined the concepts below, get started by **[installing and launching](running.html)** Brooklyn.
 
 
-***Deployment and Management*** Brooklyn is built for agile deployment of applications across cloud and other targets, and real-time autonomic management. "Autonomics" is the concept of components looking after themselves where possible (self-healing, self-optimizing, etc).
+***Deployment and Management*** Brooklyn is built for agile deployment of applications across cloud and other targets, and real-time autonomic management. "Autonomic computing" is the concept of components looking after themselves where possible (self-healing, self-optimizing, etc).
 
 ***Blueprints***  A blueprint defines an application by specifying its components, such as processes, or combinations of processes across multiple machines and services. The blueprint also specifies the inter-relationships between the configurations of the components.
 
@@ -19,9 +19,9 @@ Having examined the concepts below, get started by **[installing and launching](
 
 ***Configuration*** Entities can have arbitrary configuration values, which get inherited by their child entities. You can set global (Brooklyn-wide) properties in (``~/.brooklyn/brooklyn.properties``).  Common configuration keys have convenient aliases called "flags".
 
-***Sensors*** are the mechanism for entities to expose information for other entities to see.  Sensors from an entity can be subscribed to by other entities to track changes in the entity’s activity.
+***Sensors*** are the mechanism for entities to expose information for other entities to see.  Sensors from an entity can be subscribed to by other entities to track changes in the entity’s activity. Sensors can be updated, potentially frequently, by the entity or associated tasks.
 
-***Effectors*** are the mechanism for entities to expose the operations that can be invoked on it by other entities.  The invoker is able to track the execution of that effector. 
+***Effectors*** are the mechanism for entities to expose the operations that can be invoked on it by other entities.  The invoker is able to track the execution of that effector with tasks. 
 
 
 ***Lifecycle*** The management context of Brooklyn associates a "lifecycle" with Brooklyn entities.  Common operations are start, stop, and restart (whose meaning differs slightly for applications and processes; the details are in the concepts guide linked above).  Starting an application results in the start() operation being performed recursively (typically in parallel) on the application's children.
@@ -29,7 +29,8 @@ Having examined the concepts below, get started by **[installing and launching](
 ***Tasks*** Lifecycle and other operations in Brooklyn are tracked as tasks. This allows current and past processing to be observed by operators, and processing to be managed across multiple management nodes.
 
 
-***Locations*** can be defined in order to specify where the processes of an application will run.  Brooklyn supports different cloud providers and pre-prepared machines, known as "BYON" (Bring Your Own Nodes).
+***Locations*** can be defined in order to specify where the processes of an application will run.  Brooklyn supports different cloud providers and pre-prepared machines (including localhost), known as "BYON" (Bring Your Own Nodes).
 
 ***Policies*** Policies perform the active management enabled by Brooklyn. Entities can have  Policy instances attached to them, which can subscribe to sensors from other entities or run periodically.  When they run they can perform calculations, look up other values, invoke effectors or emit sensor values from the entity with which they are associated.
 
+***Enrichers*** These are mechanisms that subscribe to a sensor, or multiple sensors, and output a new sensor. For example, the enricher which sums a sensor across multiple entities (used to get the total requests-per-second for all the web servers in a cluster), and the enricher which calculates a 60-second rolling average.
\ No newline at end of file