brooklyn-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From henev...@apache.org
Subject [6/6] brooklyn git commit: Typo: "logic groupings" -> "logical groupings"
Date Mon, 01 Feb 2016 17:31:21 GMT
Typo: "logic groupings" -> "logical groupings"


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

Branch: refs/heads/0.6.0
Commit: 99cce005d05779c41c18ce69b47114cfa2af071a
Parents: b9ef19f
Author: David Toy <d@vidtoy.co.uk>
Authored: Thu Apr 18 19:52:26 2013 +0100
Committer: David Toy <d@vidtoy.co.uk>
Committed: Thu Apr 18 19:52:26 2013 +0100

----------------------------------------------------------------------
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/brooklyn/blob/99cce005/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index 2cdc47a..35bfb06 100644
--- a/README.md
+++ b/README.md
@@ -25,7 +25,7 @@ In DevOps fashion, Brooklyn allows applications and roll-outs to be version
cont
 
 Brooklyn enables [autonomic management](http://en.wikipedia.org/wiki/Autonomic_computing)
of applications. (i.e. many small, local, distributed control loops).
 
-Management policies can be attached to every component part in an application, and to logic
groupings of components (clusters, fabrics). Policies can implement both technical and non-technical
(business) requirements.
+Management policies can be attached to every component part in an application, and to logical
groupings of components (clusters, fabrics). Policies can implement both technical and non-technical
(business) requirements.
 
 At runtime, policies have access to all aspects of the deployment, including deployment topology
(hierarchical) and locations (machines, PaaSes, and jurisdictions), as well as scripts, instrumentation,
and operational goals and constraints. This means that once the application is launched, the
policies are all set to keep the application running optimally, based on whatever optimally
means in that context.
 


Mime
View raw message