diff --git a/modules/intro/pages/transaction-and-acid.adoc b/modules/intro/pages/transaction-and-acid.adoc
index b8a2a214..f2031d39 100644
--- a/modules/intro/pages/transaction-and-acid.adoc
+++ b/modules/intro/pages/transaction-and-acid.adoc
@@ -23,8 +23,7 @@ The TigerGraph system provides traditional ACID consistency: A transaction can i
 The TigerGraph system also provides distributed system Sequential Consistency: every replica of the data performs the same operations in the same order. This is one of the strongest forms of consistency available, stronger than causal consistency, for example.
 
 == *Isolation Level*
-
-TigerGraph supports the Serializable isolation level, the strongest form of isolation. Internally, TigerGraph uses MVCC to implement the isolation. MVCC, or Multi-Version Concurrency Control, makes use of multiple snapshots of portions of the database state in order to support isolated concurrent operations.  In principle, there can be one snapshot per read or write operation.
+TigerGraph supports the read-committed isolation level, the default standard for many major databases. Internally, TigerGraph uses MVCC to implement the isolation. MVCC, or Multi-Version Concurrency Control, makes use of multiple snapshots of portions of the database state in order to support isolated concurrent operations.  In principle, there can be one snapshot per read or write operation.
 
 == *No Dirty Reads*