From 1482b3ef1e749d3d9359a5d8886417c7d116878a Mon Sep 17 00:00:00 2001
From: Clay-Mysten <100217682+Clay-Mysten@users.noreply.github.com>
Date: Tue, 21 Jun 2022 18:46:50 -0400
Subject: [PATCH] Update sui-compared.md (#2645)

---
 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 8a87326da4367..3f28e082b2f6c 100644
--- a/doc/src/learn/sui-compared.md
+++ b/doc/src/learn/sui-compared.md
@@ -28,7 +28,7 @@ This doesn't mean that Sui as a platform never orders transactions with respect
 
 ## A collaborative approach to transaction submission
 
-Sui validates transactions individually, rather than batching them in the traditional blocks. The key advantage of this approach low latency; each successful transaction quickly obtains a certificate of finality that proves to anyone that the transaction will be processed by the Sui network.
+Sui validates transactions individually, rather than batching them in the traditional blocks. The key advantage of this approach is low latency; each successful transaction quickly obtains a certificate of finality that proves to anyone that the transaction will be processed by the Sui network.
 
 But the process of submitting a transaction is a bit more involved. That little more work occurs on the network. (With bandwidth getting cheaper, this is less of a concern.) Whereas a usual blockchain can accept a bunch of transactions from the same author in a fire-and-forget mode, Sui transaction submission follows these steps: