Fix build warnings

doc/book/admin/logs.rst

@@ -6,8 +6,8 @@ Logs
 Each Tarantool instance logs important events to its own log file ``<instance-name>.log``.
 For instances started with :ref:`tt <tt-cli>`, the log location is defined by
 the ``log_dir`` parameter in the :ref:`tt configuration <tt-config>`.
-By default, it's ``/var/log/tarantool`` in the ``tt`` :ref:`system mode <config_modes>`,
-and the ``var/log/`` subdirectory of the ``tt`` working directory in the :ref:`local mode <config_modes>`.
+By default, it's ``/var/log/tarantool`` in the ``tt`` :ref:`system mode <tt-config_modes>`,
+and the ``var/log/`` subdirectory of the ``tt`` working directory in the :ref:`local mode <tt-config_modes>`.
 In the specified location, ``tt`` creates separate directories for each instance's logs.
 
 To check how logging works, write something to the log using the :ref:`log <log-module>` module:

doc/book/admin/upgrades/upgrade_cluster.rst

@@ -329,5 +329,5 @@ Switching the master
         the replica set state by calling ``box.cfg{ read_only == false }`` on the master.
         Then pick another candidate and restart the procedure.
 
-After switching the master, perform the :ref:`replication check <upgrades-admin-replication-check>`
+After switching the master, perform the :ref:`replication check <admin-upgrades-replication-check>`
 on each instance of the replica set.

doc/dev_guide/building_from_source.rst

@@ -245,7 +245,7 @@ Additional steps
 
     ``tarantoolctl`` is deprecated in favor of :ref:`tt CLI <tt-cli>`.
     Find the instructions on switching from ``tarantoolctl`` to ``tt`` in
-    :ref:`Migration from tarantoolctl to tt <tarantoolctl-migration-to-tt>``.
+    :ref:`Migration from tarantoolctl to tt <tarantoolctl-migration-to-tt>`.
 
 The CMake option for hinting that the result will be distributed is
 :code:`-DENABLE_DIST=ON`. With this option, ``make install``

doc/how-to/sql/sql_tutorial.rst

@@ -181,6 +181,7 @@ Retrieve the 4 rows in the table, in descending order by ``column2``, then
 .. important::
 
     Tarantool has its own
+
 The result is:
 
 .. code-block:: tarantoolsession

doc/how-to/vshard_quick.rst

@@ -15,7 +15,7 @@ This example includes 5 Tarantool instances and 2 replica sets:
 * ``storage_2_a`` – a ``storage`` instance, the **master** of the **second** replica set
 * ``storage_2_b`` – a ``storage`` instance, the **replica** of the **second** replica set
 
-All instances are managed using the :ref:`tt <tt_cli>` administrative utility.
+All instances are managed using the :ref:`tt <tt-cli>` administrative utility.
 
 Change the directory to ``example/`` and use ``make`` to run the development cluster:
 

doc/reference/reference_lua/box_schema/space_create.rst

@@ -46,7 +46,7 @@ space_opts
 
     .. NOTE::
 
-    These options are also passed to :doc:`/reference/reference_lua/box_space/alter`.
+        These options are also passed to :doc:`/reference/reference_lua/box_space/alter`.
 
     ..  _space_opts_if_not_exists:
 

doc/reference/reference_lua/box_space/create_index.rst

@@ -58,7 +58,7 @@ index_opts
 
     .. NOTE::
 
-    These options are also passed to :doc:`/reference/reference_lua/box_index/alter`.
+        These options are also passed to :doc:`/reference/reference_lua/box_index/alter`.
 
     ..  _index_opts_type:
 
@@ -289,7 +289,7 @@ key_part
 
         .. NOTE::
 
-        To create a key part by a field name, you need to specify :ref:`space_object:format() <box_space-format>` first.
+            To create a key part by a field name, you need to specify :ref:`space_object:format() <box_space-format>` first.
 
         | Type: string or number
 

doc/reference/reference_lua/compat/box_cfg_replication_sync_timeout.rst

@@ -37,7 +37,7 @@ It is important to set the desired behavior before the initial ``box.cfg{}`` cal
     ---
     - error: 'builtin/box/load_cfg.lua:253: The compat  option ''box_cfg_replication_sync_timeout''
         takes effect only before the initial box.cfg() call'
-...
+    ...
 
 A fresh Tarantool run:
 

doc/reference/reference_lua/compat/compat_tutorial.rst

@@ -31,7 +31,7 @@ The options list is serialized in the interactive console with additional detail
     - - option_2: old
     - - option_default_old: default (old)
     - - option_default_new: default (new)
-...
+    ...
 
 Listing options details
 -----------------------

doc/reference/reference_rock/vshard/vshard_router.rst

@@ -864,7 +864,7 @@ Router public API
         :param options:
 
             * ``timeout`` — a request timeout, in seconds. If the ``router`` cannot identify a
-          shard with the specified ``bucket_id``, it will retry until the timeout is reached.
+              shard with the specified ``bucket_id``, it will retry until the timeout is reached.
 
             * other :ref:`net.box options <net_box-options>`, such as ``is_async``,
               ``buffer``, ``on_push`` are also supported.
@@ -891,7 +891,7 @@ Router public API
         :param options:
 
             * ``timeout`` — a request timeout, in seconds. If the ``router`` cannot identify a
-          shard with the specified ``bucket_id``, it will retry until the timeout is reached.
+              shard with the specified ``bucket_id``, it will retry until the timeout is reached.
 
             * other :ref:`net.box options <net_box-options>`, such as ``is_async``,
               ``buffer``, ``on_push`` are also supported.
@@ -929,7 +929,7 @@ Router public API
         :param options:
 
             * ``timeout`` — a request timeout, in seconds. If the ``router`` cannot identify a
-          shard with the specified ``bucket_id``, it will retry until the timeout is reached.
+              shard with the specified ``bucket_id``, it will retry until the timeout is reached.
 
             * other :ref:`net.box options <net_box-options>`, such as ``is_async``,
               ``buffer``, ``on_push`` are also supported.
@@ -957,7 +957,7 @@ Router public API
         :param options:
 
             * ``timeout`` — a request timeout, in seconds. If the ``router`` cannot identify a
-          shard with the specified ``bucket_id``, it will retry until the timeout is reached.
+              shard with the specified ``bucket_id``, it will retry until the timeout is reached.
 
             * other :ref:`net.box options <net_box-options>`, such as ``is_async``,
               ``buffer``, ``on_push`` are also supported.

doc/reference/tooling/tarantoolctl.rst

@@ -236,6 +236,7 @@ as part of Tarantool distribution -- see OS-specific default paths in
 :ref:`Notes for operating systems <admin-os_notes>`):
 
 .. code-block:: lua
+
    default_cfg = {
        pid_file  = "/var/run/tarantool",
        wal_dir   = "/var/lib/tarantool",
@@ -246,6 +247,7 @@ as part of Tarantool distribution -- see OS-specific default paths in
        language  = "Lua",
    }
    instance_dir = "/etc/tarantool/instances.enabled"
+
 where:
 
 * | ``pid_file``

doc/reference/tooling/tt_cli/logrotate.rst

@@ -1,7 +1,7 @@
 .. _tt-logrotate:
 
 Rotating instance logs
-====================
+======================
 
 ..  code-block:: bash