Rename, purge use of term delta

This would be a fine document to introduce the term delta, but
it looks like the content flows just fine without it.

book/src/SUMMARY.md

@@ -30,7 +30,7 @@
   - [Blocktree](blocktree.md)
   - [Data Plane Fanout](data-plane-fanout.md)
   - [Reliable Vote Transmission](reliable-vote-transmission.md)
-  - [Fork Deltas](fork-deltas.md)
+  - [Bank Forks](bank-forks.md)
   - [Cluster Economics](ed_overview.md)
     - [Validation-client Economics](ed_validation_client_economics.md)
       - [State-validation Protocol-based Rewards](ed_vce_state_validation_protocol_based_rewards.md)

book/src/fork-deltas.md → book/src/bank-forks.md

@@ -1,4 +1,4 @@
-# Fork Deltas
+# Bank Fork
 
 This design describes a way to checkpoint the bank state such that it can track
 multiple forks without duplicating data.  It addresses the following
@@ -11,9 +11,8 @@ challenges:
 
 ## Architecture
 
-The basic design idea is to maintain a DAG of forks.  Each fork points back to
-a single ancestor.  The DAG is initialized with a root.  Each subsequent fork
-must descend from the root.
+The basic design idea is to maintain a DAG of forks. The DAG is initialized with
+a *root*.  Each subsequent fork must descend from the root.
 
 ## Active Forks
 
@@ -24,7 +23,7 @@ For example:
 
 <img alt="Forks" src="img/forks.svg" class="center"/>
 
-The following *active forks* are in the deltas DAG
+The following *active forks* are in the forks DAG
 
 * 4,2,1
 * 5,2,1