-provide read-only access to those files, allowing users to recover them. The
-filesystem can be used by other applications, too.
-
-
-THE GRID OF STORAGE SERVERS
-
-A key-value store is implemented by a collection of peer nodes -- processes
-running on computers -- called a "grid". (The term "grid" is also used
-loosely for the filesystem supported by these nodes.) The nodes in a grid
-establish TCP connections to each other using Foolscap, a secure
-remote-message-passing library.
-
-Each node offers certain services to the others. The primary service is that
-of the storage server, which holds data in the form of "shares". Shares are
-encoded pieces of files. There are a configurable number of shares for each
-file, 10 by default. Normally, each share is stored on a separate server, but
-a single server can hold multiple shares for a single file.
-
-Nodes learn about each other through an "introducer". Each node connects to a
-central introducer at startup, and receives a list of all other nodes from
-it. Each node then connects to all other nodes, creating a fully-connected
-topology. In the current release, nodes behind NAT boxes will connect to all
-nodes that they can open connections to, but they cannot open connections to
-other nodes behind NAT boxes. Therefore, the more nodes behind NAT boxes, the
-less the topology resembles the intended fully-connected topology.
-
-The introducer in nominally a single point of failure, in that clients who
-never see the introducer will be unable to connect to any storage servers.
-But once a client has been introduced to everybody, they do not need the
-introducer again until they are restarted. The danger of a SPOF is further
-reduced in other ways. First, the introducer is defined by a hostname and a
+provide read-only access to those files, allowing users to recover them.
+There are several other applications built on top of the Tahoe-LAFS filesystem
+(see the RelatedProjects page of the wiki for a list).
+
+
+THE KEY-VALUE STORE
+
+The key-value store is implemented by a grid of Tahoe-LAFS storage servers --
+user-space processes. Tahoe-LAFS storage clients communicate with the storage
+servers over TCP.
+
+Storage servers hold data in the form of "shares". Shares are encoded pieces
+of files. There are a configurable number of shares for each file, 10 by
+default. Normally, each share is stored on a separate server, but in some
+cases a single server can hold multiple shares of a file.
+
+Nodes learn about each other through an "introducer". Each server connects to
+the introducer at startup and announces its presence. Each client connects to
+the introducer at startup, and receives a list of all servers from it. Each
+client then connects to every server, creating a "bi-clique" topology. In the
+current release, nodes behind NAT boxes will connect to all nodes that they
+can open connections to, but they cannot open connections to other nodes
+behind NAT boxes. Therefore, the more nodes behind NAT boxes, the less the
+topology resembles the intended bi-clique topology.
+
+The introducer is a Single Point of Failure ("SPoF"), in that clients who
+never connect to the introducer will be unable to connect to any storage
+servers, but once a client has been introduced to everybody, it does not need
+the introducer again until it is restarted. The danger of a SPoF is further
+reduced in two ways. First, the introducer is defined by a hostname and a