aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/access.md26
1 files changed, 13 insertions, 13 deletions
diff --git a/docs/access.md b/docs/access.md
index ce1e55a..c03f7c4 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -313,20 +313,20 @@ Whatever the policy, and without one, a change is refused that Automerge itself
wouldn't have written: bytes that aren't Automerge's encoding of the change; a first
operation not numbered one after the highest of its dependencies; a change that isn't
its actor's first and doesn't build on the one before; an operation naming one that
-wasn't made in the change's own history, or that isn't what it is named as (the
-object written into, the element of that list, a value replaced at that place); and an
-operation other than those Automerge's own transactions write. Those insert a value, an
-object or a mark's begin or end into a list or a text, replacing nothing; write at a
+wasn't made in the change's own history, or that isn't what it is named as (the object
+written into, the element of that list, a value or an object it replaces at that
+place); and an operation other than those Automerge's own transactions write. Those
+insert a value or an object into a list or a text, replacing nothing; write at a
list's element, never its head, without inserting, replacing what is at that element
-(the element itself, or what was written at it); write at a map's key, never inserting,
-a deletion or an increment replacing something; and mark only in a text, the end
-inserted right after the begin, at the begin or at an element after the one the begin
-follows. A table is refused too, which transactions make but can't write into, and the
-store makes none. Automerge applies some others, and then panics, saves a document that
-doesn't load, or holds another change than the one it was given. All of it is asked of the
-change and its history alone, so two nodes that hold a change's history come to the
-same, whatever else they hold: a change of the same batch refused after it passed
-(forged, or against the rules) stands in for nothing.
+(the element itself, or what was written at it); write at a map's key, never
+inserting, a deletion or an increment replacing something. Tables and marks are
+refused too: transactions make a table but can't write into it, and Automerge takes
+some marks and then breaks; the store writes neither. Automerge applies some others,
+and then panics, saves a document that doesn't load, or holds another change than the
+one it was given. All of it is asked of the change and its history alone, so two nodes
+that hold a change's history come to the same, whatever else they hold: a change of
+the same batch refused after it passed (forged, or against the rules) stands in for
+nothing.
In a swarm without a registry, whatever a user would need, any member may. A refused
change stays out, and so does whatever builds on it; the node logs it (`Refused a