Skip to content

Commit c3f65b1

Browse files
committed
Minor fixes after peer review
1 parent 25afc52 commit c3f65b1

File tree

1 file changed

+2
-2
lines changed
  • doc/reference/reference_lua/box_stat

1 file changed

+2
-2
lines changed

doc/reference/reference_lua/box_stat/memtx.rst

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ This example illustrates memory statistics for ``used`` tuples in a transaction.
9393

9494
The cluster must be started with the :ref:`database.use_mvcc_engine <configuration_reference_database_use_mvcc_engine>`
9595
parameter set to true. This :ref:`enables MVCC <txn_mode_mvcc-enabling>` so that
96-
``box.stat.memtx.tx().mvcc`` contained non-zero values.
96+
``box.stat.memtx.tx().mvcc`` contains non-zero values.
9797

9898
The next step is to create a space with a primary index and to begin a transaction:
9999

@@ -117,7 +117,7 @@ In the transaction above, three tuples are replaced by the `0` key:
117117

118118
MVCC considers all these tuples as ``used`` since they belong to the current transaction.
119119
Also, MVCC considers tuples ``{0, 0}`` and ``{0, 'aa..aa'}`` as ``retained`` because
120-
they don't belong to any index (unlike ``{0, 1}``), but they cannot be deleted yet.
120+
they don't belong to any index (unlike ``{0, 1}``) but cannot be deleted yet.
121121

122122
Calling ``box.stat.memtx.tx()`` now will bring something like this:
123123

0 commit comments

Comments
 (0)