From: Zooko O'Whielacronx <zooko@zooko.com>
Date: Mon, 21 Jan 2008 22:54:43 +0000 (-0700)
Subject: doc: fix typos and otherwise edit about.html
X-Git-Url: https://git.rkrishnan.org/specifications//%22%3C?a=commitdiff_plain;h=cce2dbfe80ac92e03c9bd2e46236bd01d3dbbb47;p=tahoe-lafs%2Ftahoe-lafs.git

doc: fix typos and otherwise edit about.html
---

diff --git a/docs/about.html b/docs/about.html
index 86c664dc..213b2bf1 100644
--- a/docs/about.html
+++ b/docs/about.html
@@ -17,7 +17,7 @@
     <h2>Overview</h2>
     <p>A "storage grid" comprises a number of storage servers.  A storage server has local attached storage (typically one or more SATA hard disks).  A "gateway" uses the storage servers and provides to its clients a filesystem over a standard protocol such as HTTP(S), FUSE, or SMB.</p>
     <p>Users do not rely on storage servers to provide <i>confidentiality</i> nor <i>integrity</i> for the data -- instead all of the data is encrypted and integrity checked by the gateway, so that the servers are not able to learn anything about the data nor to alter it.</p>
-    <p>Users do rely on the storage servers for <i>availability</i> -- the ciphertext is erasure-coded and distributed across <cite>N</cite> different storage servers (the default value for <cite>N</cite> is 12) so that it can be recovered from any <cite>K</cite> of these servers (the default value of <cite>K</cite> is 3).  Therefore only the simulaneous failure of <cite>N-K+1</cite> (with the defaults, 10) servers to make the data unavailable.  Phrasing this in terms of <i>reliance</i>, we say that the users <i>rely on</i> the gateway for the confidentiality and integrity of the data, and on any 3 of the 12 severs for the availability of the data.</p>
+    <p>Users do rely on the storage servers for <i>availability</i> -- the ciphertext is erasure-coded and distributed across <cite>N</cite> different storage servers (the default value for <cite>N</cite> is 12) so that it can be recovered from any <cite>K</cite> of these servers (the default value of <cite>K</cite> is 3).  Therefore only the simulaneous failure of <cite>N-K+1</cite> (with the defaults, 10) servers can make the data unavailable.  Phrasing this in terms of <i>reliance</i>, we say that the users <i>rely on</i> the gateway for the confidentiality and integrity of the data, and on any 3 of the 12 servers for the availability of the data.</p>
     <p>The typical deployment mode is that each user runs her own gateway on her own machine.  This way she needs to rely only on her own machine for the confidentiality and integrity of the data, and she can take advantage of tighter filesystem interfaces such as FUSE and SMB.</p>
     <p>An alternate deployment mode is that the gateway runs on a remote machine and the user connects to it over HTTPS.  This means that the operator of the gateway can view and modify the user's data (the user <i>relies on</i> the gateway for confidentiality and integrity), but it means that the user can access the filesystem with a client that doesn't have the gateway software installed, such as an Internet kiosk or cell phone.</p>
     <p>A user who has read-write access to a file or directory can give another user read-write access to that file or directory, or can give another user read-only access to that file or directory.  A user who has read-only access to a file or directory can give another user read-only access to it.</p>