aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/access.md12
1 files changed, 8 insertions, 4 deletions
diff --git a/docs/access.md b/docs/access.md
index 976197e..2b5f54c 100644
--- a/docs/access.md
+++ b/docs/access.md
@@ -314,10 +314,14 @@ wouldn't have written: bytes that aren't Automerge's encoding of the change; a f
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
-anything Automerge's own transactions never write (a deletion replacing nothing, a
-value put at a list's head without being inserted, a mark ended but right after its
-begin). Automerge applies some of those, and then panics, saves a document that doesn't
+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
+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. 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