From f40c001bc3d827b053b4b1e97f648af99246c1a9 Mon Sep 17 00:00:00 2001 From: Niko PLP Date: Mon, 9 Sep 2024 16:33:29 +0300 Subject: [PATCH] typo --- src/pages/en/framework/crdts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/en/framework/crdts.md b/src/pages/en/framework/crdts.md index 9a0b3dc..a8d42b7 100644 --- a/src/pages/en/framework/crdts.md +++ b/src/pages/en/framework/crdts.md @@ -89,7 +89,7 @@ Now let's have a look at what those CRDTs have in common and what is different b | **Counter CRDT** | ❌ | ❌ | ✅ 🔥 | | Counters are a safe way to manage integers in a concurrent system. Automerge is the only one offering counters. Please note that CRDT types in general are "eventual consistent" only (BASE model). If you need stronger guarantees like the ones provided by ACID systems (specially guaranteeing the sequencing of operations, very useful for preventing double-spending) then you have to use a **Synchronous Transaction** in NextGraph. | | **link/ref values (foreign key)** | ✅ 🔥 | ❌ \* | ❌ \* | -| (\*) discrete data cannot link to external documents. This is the reason why all Documents in NextGraph have a Graph part, in order to enable inter-linking of data and documents across the Global Giant Graph of Linked Data / Semantic Web | +| (\*) discrete data cannot link to external documents. This is the reason why all Documents in NextGraph have a Graph part, in order to enable inter-linking of data and documents across the Giant Global Graph of Linked Data / Semantic Web | | **Float values** | ✅ | 🟧 | ✅ | | Yjs doesn't enforce strong typing on values. they can be any valid JSON (and Floats are just Numbers). | | **Date values** | ✅ | ❌ | ✅ |