Author: stefanegli
Date: Wed May 22 12:40:46 2013
New Revision: 1485192

URL: http://svn.apache.org/r1485192
Log:
SLING-2827 : added discovery.api and .impl[s] documentation (two more minor 
typos/rewordings)

Modified:
    sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext

Modified: 
sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext
URL: 
http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext?rev=1485192&r1=1485191&r2=1485192&view=diff
==============================================================================
--- 
sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext 
(original)
+++ 
sling/site/trunk/content/documentation/bundles/discovery-api-and-impl.mdtext 
Wed May 22 12:40:46 2013
@@ -100,15 +100,15 @@ The following is an example of a `Proper
 
 ## Deployment and configuration
 
-The discovery API makes no assumptions as to how the instances and clusters 
discovery each other. This is entirely
+The discovery API makes no assumptions as to how the instances and clusters 
discover each other. This is entirely
 up to the implementations. Some might choose automatic discovery within a LAN 
using IP multicast, others
 might choose explicit configuration via a central service etc.
 
 ## discovery.impl: Resource-based, OOTB Implementation
 
-The `discovery.impl` bundle is a resource-based, out of the box implementation 
using standard Sling. The discovery within 
-a cluster is done by writing heartbeat information into the (common) 
repository. The establishment of a clusterview
-is done by analyzing these heartbeats, initiating a voting within the cluster 
(such that each instance can agree
+The `discovery.impl` bundle is a resource-based, out of the box implementation 
of the `discovery.api` using standard Sling. 
+The discovery within a cluster is done by writing heartbeat information into 
the (common) repository. The establishment of a 
+clusterview is done by analyzing these heartbeats, initiating a voting within 
the cluster (such that each instance can agree
 that it sees the same number of instances) and by concluding the voting by 
promoting it as the new "established" view.
 
 ### Location in Repository


Reply via email to