[34/50] brooklyn-server git commit: Updates to wording of Deployment section.

[he...@apache.org]

Updates to wording of Deployment section.


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

Branch: refs/heads/0.5.0
Commit: bfa0de2f08c26328e19eee64018c6025268d7d1f
Parents: 1e29159
Author: David Toy <d...@vidtoy.co.uk>
Authored: Thu Apr 18 17:05:07 2013 +0100
Committer: David Toy <d...@vidtoy.co.uk>
Committed: Mon Apr 22 12:52:48 2013 +0100

----------------------------------------------------------------------
 README.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/brooklyn-server/blob/bfa0de2f/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index 6072351..2cdc47a 100644
--- a/README.md
+++ b/README.md
@@ -8,18 +8,17 @@ Brooklyn's main emphasis is managing live applications (e.g auto-scaling, except
 
 ### Deployment
 
-Brooklyn enables single-click deployment of complex applications.
+Brooklyn enables single-click deployment of complex applications, while tying-in with other great tools, and reusing and complementing existing workflows.
 
+Use Brooklyn to create an Application Blueprint, instructing Brooklyn how to wire together your applications and components, customizing and extending them as needed. Share the blueprint with others (optionally using Brooklyn's Web Service Catalog) to allow them to single-click deploy your application onto the infrastructure of their choice.
 
 Brooklyn features:
 
-* out-of-the-box support for many common software entities.
+* out-of-the-box support for many common software components.
 * integration with jclouds, allowing deployment to the majority of public and private clouds, in addition to pools of fixed IP machines.
 * integration with Apache Whirr (and thereby Chef and Puppet), allowing deployment of well-known services such as Hadoop and elasticsearch (and you can still use POBS, plain-old-bash-scripts).
 * integration with PaaS's such as OpenShift, allowing use of PaaSes alongside self-built clusters, for maximum flexibility.
 
-Brooklyn works with and ties into other tools, adding the concepts of manageable clusters and fabrics.
-
 In DevOps fashion, Brooklyn allows applications and roll-outs to be version controlled, tested programatically, and reused across locations and contexts. Develop on localhost, then reuse the same application descriptor to deploy to QA, and then to your production environment.
 
 ### Management