aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/federation.md24
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/federation.md b/docs/federation.md
index 5873013..85d9db8 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -136,12 +136,11 @@ which are checkpoints (Checkpoints).
An event is none if its bytes aren't the JCS encoding of the JSON they read as, if a
field is missing or more, if its `key` or `sig` doesn't read back to itself spelled as
above, or if it is larger than the federation allows. So nobody but its signer makes
-another event of what a party signed. Federation 1 allows:
+another event of what a party signed. Of an event, federation 1 allows:
-* an event of up to 256 KiB, with up to 64 dependencies;
-* a party with up to 16 keys, in its version or its set, and a node list of up to 64
- nodes;
-* a path of up to 32 segments, each of up to 255 bytes;
+* up to 256 KiB, with up to 64 dependencies;
+* a key set of up to 16 keys, and a node list of up to 64 nodes;
+* in a write, a path of up to 32 segments, each of up to 255 bytes;
* in values, numbers that are integers from −2⁵³ to 2⁵³, and strings of whole Unicode
characters, no surrogate alone.
@@ -212,13 +211,14 @@ application keeps party names apart from its spelling (no party named `wiki` whi
`wiki.r` is lass's).
A version is none if a field is missing or more (but for `checkpoint`, which it may
-leave out), or if it breaks any of the above. It can't pass, and a version event naming
-it is refused. A proposal is taken whatever it holds: whether it is a version is asked
-where a version event names it, so that nodes knowing more of what a version may say
-don't part from those knowing less. A node shows whether a proposal is a version by the
-federation it knows, and a party's client backs none that isn't: two thirds backing one
-that can never be written bind the federation to its version, as a yes binds (Changing
-the policy).
+leave out), if it gives a party more keys than a key set may hold or more nodes than a
+node list, or a rule a path longer than a write's may be, or if it breaks any of the
+above. It can't pass, and a version event naming it is refused. A proposal is taken
+whatever it holds: whether it is a version is asked where a version event names it, so
+that nodes knowing more of what a version may say don't part from those knowing less. A
+node shows whether a proposal is a version by the federation it knows, and a party's
+client backs none that isn't: two thirds backing one that can never be written bind the
+federation to its version, as a yes binds (Changing the policy).
What the swarm's document holds beyond the events, and what a node takes at its API, is
the store's ([`store.md`](store.md), On Automerge).