From 8d00d62cc8ea0f37abfe4c16cdbc0388ba6aebaa Mon Sep 17 00:00:00 2001 From: Leofis G Date: Wed, 6 Jul 2022 01:07:05 +0800 Subject: [PATCH] Update sui-compared.md (#2925) --- doc/src/learn/sui-compared.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/learn/sui-compared.md b/doc/src/learn/sui-compared.md index c79507aca7943..a25c82d78a657 100644 --- a/doc/src/learn/sui-compared.md +++ b/doc/src/learn/sui-compared.md @@ -24,7 +24,7 @@ A lot of transactions do not have complex interdependencies with other, arbitrar Sui further expands this approach to more involved transactions that may explicitly depend on multiple elements under their sender's control, using an [object model](../build/objects.md) and leveraging [Move](../build/move.md)'s strong ownership model. By requiring that dependencies be explicit, Sui applies a "multi-lane" approach to transaction validation, making sure those independent transaction flows can progress without impediment from the others. -This doesn't mean that Sui as a platform never orders transactions with respect to each other, or that it we allows owners to only affect their owned microcosm of objects. Sui will also process transactions that have an effect on some shared state, in a rigorous, consensus-ordered manner. They're just not the default use case. +This doesn't mean that Sui as a platform never orders transactions with respect to each other, or that it allows owners to only affect their owned microcosm of objects. Sui will also process transactions that have an effect on some shared state, in a rigorous, consensus-ordered manner. They're just not the default use case. ## A collaborative approach to transaction submission