From 6fc863f1c4a1bc984348cf68e03104ada4c27fa6 Mon Sep 17 00:00:00 2001
From: TomShawn <41534398+TomShawn@users.noreply.github.com>
Date: Wed, 8 Sep 2021 16:42:20 +0800
Subject: [PATCH] Update optimistic-transaction.md

---
 optimistic-transaction.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/optimistic-transaction.md b/optimistic-transaction.md
index 8f46108251179..c1ffae47f36ba 100644
--- a/optimistic-transaction.md
+++ b/optimistic-transaction.md
@@ -65,7 +65,7 @@ However, TiDB transactions also have the following disadvantages:
 
 ## Transaction retries
 
-In the optimistic transaction model, transactions might fail to be committed because of write–write conflict in heavy contention scenarios. TiDB uses optimistic concurrency control by default, whereas MySQL applies pessimistic concurrency control. This means that MySQL adds locks during SQL execution, and its Repeatable Read isolation level allows for current reads, so commits generally do not encounter exceptions. To lower the difficulty of adapting applications, TiDB provides an internal retry mechanism.
+In the optimistic transaction model, transactions might fail to be committed because of write–write conflict in heavy contention scenarios. TiDB uses optimistic concurrency control by default, whereas MySQL applies pessimistic concurrency control. This means that MySQL adds locks during the execution of write-type SQL statements, and its Repeatable Read isolation level allows for current reads, so commits generally do not encounter exceptions. To lower the difficulty of adapting applications, TiDB provides an internal retry mechanism.
 
 ### Automatic retry