Skip to content

Commit 423161f

Browse files
committed
Minor fixes
1 parent 8c348fa commit 423161f

File tree

1 file changed

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

1 file changed

+4
-4
lines changed

doc/reference/reference_lua/box_stat/memtx.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ box.stat.memtx()
77

88
.. function:: memtx()
99

10-
Shows memtx-storage-engine activity.
10+
Shows ``memtx`` storage engine activity.
1111

1212
.. _box_introspection-box_stat_memtx_tx:
1313

@@ -88,13 +88,13 @@ Let's take a look at `used` and `retained` tuples in a transaction.
8888
Within the first ``box.cfg()`` call to a new Tarantool instance, we
8989
:ref:`enable the MVCC engine <txn_mode_mvcc-enabling>`:
9090

91-
.. code-block:: console
91+
.. code-block:: lua
9292
9393
box.cfg{memtx_use_mvcc_engine = true}
9494
9595
Next, we create a space with a primary index, and begin a transaction:
9696

97-
.. code-block:: console
97+
.. code-block:: lua
9898
9999
box.schema.space.create('test')
100100
box.space.test:create_index('pk')
@@ -118,7 +118,7 @@ they don't belong to any index (unlike ``{0, 1}``), but they cannot be deleted y
118118

119119
If we call ``box.stat.memtx.tx()`` now, we'll see something like this:
120120

121-
.. code-block:: javascript
121+
.. code-block:: tarantoolsession
122122
:emphasize-lines: 33-39
123123
124124
tarantool> box.stat.memtx.tx()

0 commit comments

Comments
 (0)