DOC-1766 read-committed isolation level, v3.3

modules/intro/pages/transaction-and-acid.adoc

@@ -23,7 +23,7 @@ The TigerGraph system also provides distributed system Sequential Consistency: e
 [discrete]
 ==== *Isolation Level* +++<a id="TigerGraphTransactionProcessingandACIDPropertiesSupport-IsolationLevel">++++++</a>+++
 
-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.
 
 [discrete]
 ==== *No Dirty Reads* +++<a id="TigerGraphTransactionProcessingandACIDPropertiesSupport-NoDirtyReads">++++++</a>+++