Added most of the proposed changes, still to go: the graphic, "Site"

report.lyx

@@ -1,4 +1,4 @@
-#LyX 1.6.9 created this file. For more info see http://www.lyx.org/
+#LyX 1.6.7 created this file. For more info see http://www.lyx.org/
 \lyxformat 345
 \begin_document
 \begin_header
@@ -1025,9 +1025,9 @@ reference "alg:A-simple-generator"
 \end_inset
 
 .
- This solution poses problems when dealine with concurrent systems, and
- systems of a distributed nature.
- In both concurrent systems, the simple solution in algorithm 
+ This solution poses problems when dealing with concurrent and distributed
+ systems.
+ In concurrent systems, the simple solution in algorithm 
 \begin_inset CommandInset ref
 LatexCommand ref
 reference "alg:A-simple-generator"
@@ -1041,7 +1041,7 @@ reference "alg:A-simple-generator"
 \begin_layout Standard
 The obvious solution to this problem is to ensure mutual exclusion by using
  some sort of lock, which may work well in many concurrent systems.
- In a distributed system, this lock, along withe the state, would have to
+ In a distributed system, this lock, along with the state, would have to
  be distributed.
  If the lock is not distributed, no guarantee can be made that two nodes
  in the distributed system do not generate the same number.
@@ -1086,14 +1086,16 @@ using an algorithm such as SHA-1.
 \end_layout
 
 \begin_layout Standard
-When using system wide unique identifiers, such as algorithm 
+When using system wide unique identifiers, such as the ones generated by
+ algorithm 
 \begin_inset CommandInset ref
 LatexCommand ref
 reference "alg:A-simple-generator"
 
 \end_inset
 
- with mutual exclusion, it is not possible to have splits between GGS clusters.
+ with mutual exclusion, it is not possible to have identifier collisions
+ when recovering from network splits between GGS clusters.
  Consider figure 
 \begin_inset CommandInset ref
 LatexCommand ref