svn commit: r1172991 - /karaf/cellar/trunk/manual/src/main/webapp/user-guide/obr.conf

[jb...@apache.org]

Author: jbonofre
Date: Tue Sep 20 06:27:52 2011
New Revision: 1172991

URL: http://svn.apache.org/viewvc?rev=1172991&view=rev
Log:
[KARAF-877] Typo fixes on the Cellar OBR support documentation

Modified:
    karaf/cellar/trunk/manual/src/main/webapp/user-guide/obr.conf

Modified: karaf/cellar/trunk/manual/src/main/webapp/user-guide/obr.conf
URL: http://svn.apache.org/viewvc/karaf/cellar/trunk/manual/src/main/webapp/user-guide/obr.conf?rev=1172991&r1=1172990&r2=1172991&view=diff
==============================================================================
--- karaf/cellar/trunk/manual/src/main/webapp/user-guide/obr.conf (original)
+++ karaf/cellar/trunk/manual/src/main/webapp/user-guide/obr.conf Tue Sep 20 06:27:52 2011
@@ -1,16 +1,16 @@
 h1. OBR Support
 
-Apache Karaf Cellar is able to "broadcast" OBR actions between the cluster nodes (of the same group).
+Apache Karaf Cellar is able to "broadcast" OBR actions between cluster nodes of the same group.
 
 h2. Enable OBR support
 
-To enable the Cellar OBR support, you have to install the cellar-obr feature:
+To enable the Cellar OBR support, the cellar-obr feature must first be installed:
 
 {code}
 karaf@root> features:install cellar-obr
 {code}
 
-Of course, if the Cellar core feature is already install, you can use it to install the cellar-core features on all
+Of course, if the Cellar core feature is already installed, you can use it to install the cellar-core features on all
 nodes of the same group:
 
 {code}
@@ -21,7 +21,7 @@ The Cellar OBR feature will install the 
 
 h2. Register repository URL in a cluster
 
-The cluster:obr-addurl command register a OBR repository URL (repository.xml) in a cluster group:
+The cluster:obr-addurl command registers an OBR repository URL (repository.xml) in a cluster group:
 
 {code}
 karaf@root> cluster:obr-addurl group file://path/to/repository.xml
@@ -54,7 +54,7 @@ karaf@root> cluster:obr-list group
 [camel-example-route-throttling                                                       ] [org.apache.camel.camel-example-route-throttling            ] [2.9.0.SNAPSHOT          ]
 {code}
 
-When you remove a repository URL from the distributed OBR, the bundles distributed set is updated:
+When you remove a repository URL from the distributed OBR, the bundles' distributed set is updated:
 
 {code}
 karaf@root> cluster:obr-removeurl group http://karaf.cave.host:9090/cave/repo-repository.xml
@@ -62,14 +62,14 @@ karaf@root> cluster:obr-removeurl group 
 
 h2. Deploying bundles using the cluster OBR
 
-You can deploy a bundle (and the bundles in dependency) using the OBR on a given cluster group:
+You can deploy a bundle (and that bundle's dependent bundles) using the OBR on a given cluster group:
 
 {code}
 karaf@root> cluster:obr-deploy group bundleId
 {code}
 
-The bundle ID is the symbolic name (as displayed by the cluster:obr-list command). If you don't provide the version, the OBR deploys the latest version
-available. To provide the version, use comma after the symbolic name:
+The bundle ID is the symbolic name, viewable using the cluster:obr-list command. If you don't provide the version, the OBR deploys the latest version
+available. To provide the version, use a comma after the symbolic name:
 
 {code}
 karaf@root> cluster:obr-deploy group org.apache.servicemix.specs.java-persistence-api-1.1.1
@@ -78,7 +78,7 @@ karaf@root> cluster:obr-deploy group org
 
 The OBR will automatically install the bundles required to satisfy the bundle dependencies.
 
-By default, the deploy command doesn't start the bundle. To start the bundles just after the deployment, you can use the -s option:
+The deploy command doesn't start bundles by default. To start the bundles just after deployment, you can use the -s option:
 
 {code}
 karaf@root> cluster:obr-deploy -s group org.ops4j.pax.web.pax-web-runtime