[Gzz-commits] manuscripts/pointers article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/06 02:41:46

Modified files:
        pointers       : article.rst 

Log message:
        edit

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/pointers/article.rst.diff?tr1=1.142&tr2=1.143&r1=text&r2=text

Patches:
Index: manuscripts/pointers/article.rst
diff -u manuscripts/pointers/article.rst:1.142 
manuscripts/pointers/article.rst:1.143
--- manuscripts/pointers/article.rst:1.142      Thu Nov  6 02:35:20 2003
+++ manuscripts/pointers/article.rst    Thu Nov  6 02:41:46 2003
@@ -362,7 +362,7 @@
     A *pool* is a collection of blocks. The data published
     by a particular P2P Web server, the data downloaded
     by a client, the data in a client's cache, and all 
-    data available on the whole P2P Web can all be seen as a pool.
+    data available on the whole P2P Web can each be seen as a pool.
     A pool provides the functionality to
     fetch a block by its global id; local (cache- or filesystem-like)
     pools also allow
@@ -441,7 +441,7 @@
 Using pointer records, we can provide the functionality
 of static web pages. While dynamic web pages generated
 through server-side scripting and database connections
-are certainly important, this still makes up for 
+are certainly important, this is still 
 a significant portion of today's Web.
 (We may provide tools for handling simple cases
 such as showing a list of the newest articles on a news site
@@ -460,7 +460,7 @@
 the latest issue of, e.g., Slashdot (an popular online news site)
 could be downloaded from other devices' caches, instead
 of paying for wireless Internet access; trust would not be
-an issue as the pointer blocks' signatures could be validated.
+an issue as the pointer records' signatures could be validated.
 
 The peer-to-peer network we propose would use
 random-looking, semantic-free identifiers; arguments for this
@@ -509,7 +509,7 @@
 (and their pointers records) to a CD
 to take to a machine that is not connected
 to a network. Because the versioning model
-needs only the pointer blocks, not a connection
+needs only the pointer records, not a connection
 to the network, the software update could be
 performed exactly the same way as with an Internet connection.
 Other P2P versioning schemes, such as the Content-Addressable