[Gzz-commits] manuscripts/storm article.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Benja Fallenstein <address@hidden>      03/02/15 14:46:00

Modified files:
        storm          : article.rst 

Log message:
        remove some redundancy because the text's too long (sorry antont)

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

Patches:
Index: manuscripts/storm/article.rst
diff -u manuscripts/storm/article.rst:1.216 manuscripts/storm/article.rst:1.217
--- manuscripts/storm/article.rst:1.216 Sat Feb 15 14:43:08 2003
+++ manuscripts/storm/article.rst       Sat Feb 15 14:46:00 2003
@@ -1070,14 +1070,14 @@
    replacement/equivalent of a conventional file and versioning system is
    trivial?
 
-Besides the selected issues discussed above, a few remarks about further
-evaluation of Storm follow. From a security point of view, the fact that all
-data is stored in immutable blocks has obvious benefits for reliablity (data
-is never overwritten). By way of using of SHA-1 cryptocraphic content hashes
-as identifiers, verifyability is another benefit. As for usability, the ease
-of replication and caching combined with location-independent identifiers
-enable several improvements, including the possibility to keep on working on
-shared documents even when there is no or an unreliable network connection.
+.. Besides the selected issues discussed above, a few remarks about further
+   evaluation of Storm follow. From a security point of view, the fact that all
+   data is stored in immutable blocks has obvious benefits for reliablity (data
+   is never overwritten). By way of using of SHA-1 cryptocraphic content hashes
+   as identifiers, verifyability is another benefit. As for usability, the ease
+   of replication and caching combined with location-independent identifiers
+   enable several improvements, including the possibility to keep on working on
+   shared documents even when there is no or an unreliable network connection.
    
 
 Conclusions