@@ -83,16 +83,16 @@ box.stat.memtx().tx
8383
8484**Example **
8585
86- Let's take a look at  `used ` and ` retained ` tuples in a transaction.
86+ Let's get memory statistics for  `used ` tuples in a transaction.
8787
88- Within the first `` box.cfg() `` call  to a new Tarantool instance, we 
89- :ref: ` enable the MVCC engine  < txn_mode_mvcc-enabling >` :
88+ To make transactions work, we need  to :ref: ` enable the MVCC engine  < txn_mode_mvcc-enabling >`. 
89+ We'll do it within the first `` box.cfg{} `` call to a new Tarantool instance :
9090
9191.. code-block :: lua 
9292
9393   box.cfg{memtx_use_mvcc_engine = true} 
9494
95-  Next, we create a space with a primary index, and begin a transaction:
95+  Next, we'll  create a space with a primary index, and begin a transaction:
9696
9797.. code-block :: lua 
9898
@@ -106,7 +106,7 @@ Next, we create a space with a primary index, and begin a transaction:
106106   box.space.test:replace{1, 1} 
107107   box.space.test:replace{2, 1} 
108108
109-  In the transaction above, we replace  three tuples by the `0 ` key:
109+  In the transaction above, we replaced  three tuples by the `0 ` key:
110110
111111* ``{0, 0} ``
112112* ``{0, 'aa...aa'} ``
@@ -168,3 +168,11 @@ If we call ``box.stat.memtx.tx()`` now, we'll see something like this:
168168	          count: 0 
169169	          total: 0 
170170	... 
171+ 
172+  Pay attention to highlighted lines -- it's the memory used allocated for `used ` tuples.
173+ 
174+ For a neat experiment, let's commit the transaction:
175+ 
176+ .. code-block :: lua 
177+ 
178+    box.commit() 
0 commit comments