update

Signed-off-by: you06 <[email protected]>

transaction-isolation-levels.md

@@ -50,7 +50,7 @@ The Repeatable Read isolation level in TiDB differs from ANSI Repeatable Read is
 
 ### Difference between TiDB and MySQL Repeatable Read
 
-The Repeatable Read isolation level in TiDB differs from that in MySQL. The MySQL Repeatable Read isolation level does not check whether the current version is visible when updating, which means it can continue to update even if the row has been updated after the transaction starts. In contrast, if the row has been updated after the transaction starts, the TiDB optimistic transaction is rolled back and retried. Transaction Retries in TiDB's optimistic transaction mechanism might fail, leading to a final failure of the transaction, while in TiDB's pessimistic transaction mechanism and MySQL, the updating transaction can be successful.
+The Repeatable Read isolation level in TiDB differs from that in MySQL. The MySQL Repeatable Read isolation level does not check whether the current version is visible when updating, which means it can continue to update even if the row has been updated after the transaction starts. In contrast, if the row has been updated after the transaction starts, the TiDB optimistic transaction is rolled back and retried. Transaction Retries in TiDB's optimistic concurrency control might fail, leading to a final failure of the transaction, while in TiDB's pessimistic concurrency control and MySQL, the updating transaction can be successful.
 
 ## Read Committed isolation level