Update text after review

Author: xuniq

doc/reference/reference_lua/box_info/synchro.rst

@@ -63,9 +63,9 @@ box.info.synchro
     That is, synchronous transactions work like asynchronous ones.
     `1` means that a successful WAL writing to the master is enough to commit.
 
-    ..  code-block:: console
+    ..  code-block:: tarantoolsession
 
-        instance001> box.info.synchro
+        app:instance001> box.info.synchro
         ---
         - queue:
             owner: 1
@@ -89,7 +89,7 @@ box.info.synchro
 
     Check the current state of synchronous replication:
 
-    ..  code-block:: console
+    ..  code-block:: tarantoolsession
 
         app:instance001> box.info.synchro
         ---
@@ -105,29 +105,29 @@ box.info.synchro
 
     Create a space called ``sync`` and enable synchronous replication on this space:
 
-    ..  code-block:: console
+    ..  code-block:: tarantoolsession
 
         app:instance001> s = box.schema.space.create("sync", {is_sync=true})
         ---
         ...
 
     Then, create an index:
 
-    ..  code-block:: console
+    ..  code-block:: tarantoolsession
 
         app:instance001> _ = s:create_index('pk')
         ---
         ...
 
-    After that, use ``box.ctl.promote()`` function to claim a queue:
+    After that, use ``box.ctl.promote()`` function to claim the queue:
 
-    ..  code-block:: console
+    ..  code-block:: tarantoolsession
 
         app:instance001> box.ctl.promote()
 
     Next, perform data manipulations:
 
-    ..  code-block:: console
+    ..  code-block:: tarantoolsession
 
         app:instance001> require('fiber').new(function() box.space.sync:replace{1} end)
         ---
@@ -151,7 +151,7 @@ box.info.synchro
     If you call the ``box.info.synchro`` command again,
     you will see that now there are 3 transactions waiting in the queue:
 
-    ..  code-block:: console
+    ..  code-block:: tarantoolsession
 
         app:instance001> box.info.synchro
         ---