Just a nitpick / editorial suggestion: The acronym "CRDT" is not extremely common, and never defined in the document. Such things trigger my obsessive personality streak hard and maybe others' too. Thankfully, Wikipedia gave me the answer, assuming this is about conflict-free replicated data types.
> A Conflict-free Replicated Data Type, or CRDT, is an umbrella term for any data structure that can be replicated and modified concurrently across multiple sites, and is guaranteed to converge without the need for a central authority to coordinate the changes.
Sorry about that. I saw the title, didn't know what CRDT meant, and clicked through to the document specifically to find out, not particularly wanting to read the article. I was then scan-reading and missed it. I must say in my defense, though, that the convention is to define an acronym when it's first used, excluding the title, and the definition is only at the fourth use excluding the title and first section heading.
> I must say in my defense, though, that the convention is to define an acronym when it's first used… the definition is only at the fourth use…
To be fair, the definition is not in the bulleted abstract, it is in the first use of the term in the first section, which someone not familiar with CRDT might first scan, helpfully headlined “Intro to CRDTs”:
# First part: Intro to text CRDTs
A Conflict-free Replicated Data Type, or CRDT, is an umbrella term for any data structure that can be replicated and modified concurrently across multiple sites, and is guaranteed to converge without the need for a central authority to coordinate the changes.
