README

1 files changed, 19 insertions, 13 deletions

diff --git a/EndoForge/README.md b/EndoForge/README.md
index 2e03084..00567c9 100644
--- a/EndoForge/README.md
+++ b/EndoForge/README.md
@@ -30,22 +30,27 @@ machine containing the repository.
 The contributions are stored in namespaces according to the public keys of the
 contributors. This prevents collisions.
 
-(It is also possible to do _without_ `IP` connectivity using DHT connectivity;
+The contributions are cryptographically validated, which allows consensus
+mechanisms to be implemented in git `post-receive` hooks to synchronize the
+repositories, or just automate their distribution along standardized channels.
+
+(It is also possible to do _without_ `IP` connectivity using `DHT` connectivity;
 see `tuntox.git`.)
 
 ## WHAT IS A `Forge`
 
-A `Forge` is a "place" where programmers share source code.[1]
-
-Anyone could share any content, in principle.
+A `Forge` is a network "hub" that provides storage and hosting for version
+control repository databases. The largest `Forge` is Microsoft's `GitHub`.
 
-The point is the *revision control system* used track past changes. The `Forge`
-is the place that stores all the different past versions of the code in a format
-that allows all changes to be undone. Modifying databases of past history is how
-multiple programmers collaborate on the same work of source code.
+A `Forge` is the "place" where programmers share their source code with one
+another. The point is the *revision control system* used track past changes. The
+`Forge` stores all the different past versions of the code in a format that
+allows all changes to be inspected and undone. Modifying these databases of all
+past history is how multiple programmers collaborate on the same work of source
+code. (Such databases were the first blockchains.)
 
 The largest `Forge` is Microsoft's `GitHub`; but in another sense, the largest
-`Forge` is `Wikipedia`. )
+`Forge` is `Wikipedia`.
 
 Note that a `Forge` is different from a web site. A `Git`-based `Forge` must
 accept contributions in the `Git-Over-SSH` protocol. That is the convenient and
@@ -58,7 +63,7 @@ service before they can connect using `Git`'s native language of `SSH`.
 Using a `Self-Forge` relieves users of dependency on any troublesome
 intermediary `Forge`. You get your own `Forge`. You are your own `Forge`.
 
-## What is `Git-Over-SSH`
+## WHAT IS `Git-Over-SSH`
 
 `Git-Over-SSH` is the standard `Git` protocol for _both reading and writing_ a
 repository. It is the same `Git` protocol one uses when _pushing_ to
@@ -83,8 +88,8 @@ They can then commit changes to the repository, and push them back to `origin`.
 The changes will exist in a separate space from where any other user can
 overwrite. The cryptography of `OpenSSH` makes this possible.
 
-HOW IT WORKS
-------------
+HOW ENDOFORGE WORKS
+-------------------
 
 Normally, `OpenSSH` server only permits connections from users whose keys have
 been pre-authorized on the server. `OpenSSH` assumes that access should be
@@ -127,7 +132,8 @@ Note that, once installed, you can run this in ANY repository.
 
 You can also run `make shared` but that just runs the same `git config` for you.
 
-## HOW TO DISABLE
+HOW TO DISABLE
+--------------
 
 To disable public access to the repository, run: