docs: update docs/about.html with Amber

diff --git a/docs/about.html b/docs/about.html
index 39ec09afe8195052d4b17b29a3fc888bf6f9f751..89dcb9ad3b9031a8ff194d86df9c62327d414324 100644 (file)
--- a/docs/about.html
+++ b/docs/about.html
@@ -15,15 +15,15 @@
     <p><a href="http://allmydata.org">http://allmydata.org</a></p>
 
     <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 nor alter the contents of the files.</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>
-    <p>When linking a file or directory into a parent directory, you can use a read-write link or a read-only link.  If you use a read-write link, then anyone who has read-write access to the parent directory can gain read-write access to the child, but anyone who has read-only access to the parent directory can gain only read-only access to the child.  If you use a read-only link, then anyone who has either read-write or read-only access to the parent directory can gain read-only access to the child.</p>
+    <p>A "storage grid" is made up of 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 can neither read nor alter the contents of the files.</p>
+    <p>Users do rely on storage servers for <i>availability</i>.  The ciphertext is erasure-coded and distributed across <cite>N</cite> 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 simultaneous 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>In the typical deployment mode each user runs her own gateway on her own machine.  This way she need rely only on her own machine for the confidentiality and integrity of the data, and she can take advantage of filesystem integration using FUSE or 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 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 in this filesystem can give another user read-write access to that file or directory, or 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>
+    <p>When linking a file or directory into a parent directory, you can use a read-write link or a read-only link.  If you use a read-write link, then anyone who has read-write access to the parent directory can gain read-write access to the child, and anyone who has read-only access to the parent directory can gain read-only access to the child.  If you use a read-only link, then anyone who has either read-write or read-only access to the parent directory can gain read-only access to the child.</p>
     <p>There are two kinds of files: immutable and mutable.  Immutable files have the property that once they have been uploaded to the storage grid they can't be modified.  Mutable ones can be modified.</p>
-    <p>For much more technical detail, please see <a href="http://allmydata.org/trac/tahoe/wiki/Doc">The Doc Page</a> on the Wiki, and the other files in the <cite>docs</cite> directory of the source tree.</p>
+    <p>For more technical detail, please see <a href="architecture.txt">architecture.txt</a>, the <a href="http://allmydata.org/trac/tahoe/wiki/Doc">The Doc Page</a> on the Wiki, and the other files in the <a href="."><cite>docs</cite></a> directory of the source tree.</p>
 
     <h2>Installing</h2>
     <p>To install Tahoe, please see <a href="install.html">install.html</a>.</p>