aboutsummaryrefslogtreecommitdiff
path: root/src/util/crdt/crdt.rs
diff options
context:
space:
mode:
authorStefan Majer <stefan.majer@f-i-ts.de>2025-01-16 13:22:00 +0100
committerStefan Majer <stefan.majer@f-i-ts.de>2025-01-16 13:22:00 +0100
commit2eb9fcae20cb7e41b1197f4565db492a97f95736 (patch)
treebe9b2912ae92b07ef5e7905372b1bc2a542234c6 /src/util/crdt/crdt.rs
parent255b01b626096ef98cf24c9552b39c0372fb4eb3 (diff)
downloadgarage-2eb9fcae20cb7e41b1197f4565db492a97f95736.tar.gz
garage-2eb9fcae20cb7e41b1197f4565db492a97f95736.zip
Fix all typos
Diffstat (limited to 'src/util/crdt/crdt.rs')
-rw-r--r--src/util/crdt/crdt.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/util/crdt/crdt.rs b/src/util/crdt/crdt.rs
index 06876897..fdf63084 100644
--- a/src/util/crdt/crdt.rs
+++ b/src/util/crdt/crdt.rs
@@ -33,8 +33,8 @@ pub trait Crdt {
/// arises very often, for example with a Lww or a LwwMap: the value type has to be a CRDT so that
/// we have a rule for what to do when timestamps aren't enough to disambiguate (in a distributed
/// system, anything can happen!), and with AutoCrdt the rule is to make an arbitrary (but
-/// determinstic) choice between the two. When using an Option<T> instead with this impl, ambiguity
-/// cases are explicitely stored as None, which allows us to detect the ambiguity and handle it in
+/// deterministic) choice between the two. When using an Option<T> instead with this impl, ambiguity
+/// cases are explicitly stored as None, which allows us to detect the ambiguity and handle it in
/// the way we want. (this can only work if we are happy with losing the value when an ambiguity
/// arises)
impl<T> Crdt for Option<T>