[Gzz-commits] gzz/Documentation/misc/hemppah-progradu mastert...

[Hermanni Hyytiälä]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Hermanni Hyytiälä <address@hidden>      03/03/25 11:22:34

Modified files:
        Documentation/misc/hemppah-progradu: masterthesis.tex 

Log message:
        Fix typo

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/Documentation/misc/hemppah-progradu/masterthesis.tex.diff?tr1=1.190&tr2=1.191&r1=text&r2=text

Patches:
Index: gzz/Documentation/misc/hemppah-progradu/masterthesis.tex
diff -u gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.190 
gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.191
--- gzz/Documentation/misc/hemppah-progradu/masterthesis.tex:1.190      Tue Mar 
25 10:48:10 2003
+++ gzz/Documentation/misc/hemppah-progradu/masterthesis.tex    Tue Mar 25 
11:22:34 2003
@@ -1788,7 +1788,7 @@
 \section{Evaluation of Peer-to-Peer approaches with regard to Fenfire}
 
 In this section we focus on locating the Storm blocks in Peer-to-Peer 
environment. We don't
-respond to fetching of Storm blocks as fetching of Storm block can be 
performed easily once
+respond to fetching of Storm blocks as fetching can be performed easily once
 Storm block is located. 
 
 In chapter 2, we discussed main differences between the loosely and the 
tightly structured 
@@ -1802,7 +1802,7 @@
 originator is located in the overlay.}. To summarize, the tightly structured 
approach
 is more efficient and scalable than the loosely structured approach.
 
-Since both Storm and tightly structured overlays use globally unique 
identifiers for each,
+Since both Storm and tightly structured overlays use globally unique 
identifiers for each data item,
 it is feasible to use tightly structured overlays for \emph{locating} Storm 
blocks efficiently.
 Another key feature of tightly structured overlays is that they are able
 to provide general purpose \emph{interface} for Reference Resolution Services 
(RRS)