Add minor fixes (cfg reference)

doc/reference/configuration/cfg_authentication.rst

@@ -24,7 +24,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies a period of time (in seconds) that a specific user should wait
+    Specify a period of time (in seconds) that a specific user should wait
     for the next attempt after failed authentication.
 
     With the configuration below, Tarantool refuses the authentication attempt if the previous
@@ -105,7 +105,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies the minimum number of characters for a password.
+    Specify the minimum number of characters for a password.
 
     The following example shows how to set the minimum password length to 10.
 
@@ -181,7 +181,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies the maximum period of time (in days) a user can use the same password.
+    Specify the maximum period of time (in days) a user can use the same password.
     When this period ends, a user gets the "Password expired" error on a login attempt.
     To restore access for such users, use :doc:`box.schema.user.passwd </reference/reference_lua/box_schema/user_passwd>`.
 
@@ -207,7 +207,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies the number of unique new user passwords before an old password can be reused.
+    Specify the number of unique new user passwords before an old password can be reused.
 
     In the example below, a new password should differ from the last three passwords.
 

doc/reference/configuration/cfg_flight_recorder.rst

@@ -36,7 +36,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies the size (in bytes) of the log storage.
+    Specify the size (in bytes) of the log storage.
     You can set this option to ``0`` to disable the log storage.
 
     | Type: integer
@@ -51,7 +51,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies the maximum size (in bytes) of the log message.
+    Specify the maximum size (in bytes) of the log message.
     The log message is truncated if its size exceeds this limit.
 
     | Type: integer
@@ -67,7 +67,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies the level of detail the log has.
+    Specify the level of detail the log has.
     You can learn more about log levels from the :ref:`log_level <cfg_logging-log_level>`
     option description.
     Note that the ``flightrec_logs_log_level`` value might differ from ``log_level``.
@@ -84,7 +84,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies the time period (in seconds) that defines how long metrics are stored from the moment of dump.
+    Specify the time period (in seconds) that defines how long metrics are stored from the moment of dump.
     So, this value defines how much historical metrics data is collected up to the moment of crash.
     The frequency of metric dumps is defined by :ref:`flightrec_metrics_interval <cfg_flightrec_metrics_interval>`.
 
@@ -100,7 +100,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies the time interval (in seconds) that defines the frequency of dumping metrics.
+    Specify the time interval (in seconds) that defines the frequency of dumping metrics.
     This value shouldn't exceed :ref:`flightrec_metrics_period <cfg_flightrec_metrics_period>`.
 
     .. NOTE::
@@ -125,7 +125,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies the size (in bytes) of storage for the request and response data.
+    Specify the size (in bytes) of storage for the request and response data.
     You can set this parameter to ``0`` to disable a storage of requests and responses.
 
     | Type: integer
@@ -141,7 +141,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies the maximum size (in bytes) of a request entry.
+    Specify the maximum size (in bytes) of a request entry.
     A request entry is truncated if this size is exceeded.
 
     | Type: integer
@@ -156,7 +156,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies the maximum size (in bytes) of a response entry.
+    Specify the maximum size (in bytes) of a response entry.
     A response entry is truncated if this size is exceeded.
 
     | Type: integer

doc/reference/configuration/cfg_logging.rst

@@ -11,21 +11,21 @@ application.
 * :ref:`log_format <cfg_logging-log_format>`
 * :ref:`log_modules <cfg_logging-log_modules>`
 
-.. _cfg_logging-log_level:
+..  _cfg_logging-log_level:
 
-.. confval:: log_level
+..  confval:: log_level
 
     Since version 1.6.2.
 
-    Specifies the level of detail the :ref:`log <admin-logs>` has. There are seven levels:
+    Specify the level of detail the :ref:`log <admin-logs>` has. There are seven levels:
 
-    * 1 – ``SYSERROR``
-    * 2 – ``ERROR``
-    * 3 – ``CRITICAL``
-    * 4 – ``WARNING``
-    * 5 – ``INFO``
-    * 6 – ``VERBOSE``
-    * 7 – ``DEBUG``
+    * 1 -- ``SYSERROR``
+    * 2 -- ``ERROR``
+    * 3 -- ``CRITICAL``
+    * 4 -- ``WARNING``
+    * 5 -- ``INFO``
+    * 6 -- ``VERBOSE``
+    * 7 -- ``DEBUG``
 
     By setting ``log_level``, you can enable logging of all events with severities above
     or equal to the given level. Tarantool prints logs to the standard

doc/reference/configuration/cfg_replication.rst

@@ -240,7 +240,7 @@
 
     Since :doc:`2.11.0 </release/2.11.0>`.
 
-    Specifies a strategy used to bootstrap a :ref:`replica set <replication-bootstrap>`.
+    Specify a strategy used to bootstrap a :ref:`replica set <replication-bootstrap>`.
     The following strategies are available:
 
     *   ``auto``: a node doesn't boot if a half or more of other nodes in a replica set are not connected.
@@ -291,7 +291,7 @@
 
     This option is in effect if :ref:`bootstrap_strategy <cfg_replication-bootstrap_strategy>` is set to ``legacy``.
 
-    Specifies the number of nodes to be up and running to start a replica set.
+    Specify the number of nodes to be up and running to start a replica set.
     This parameter has effect during :ref:`bootstrap <replication-leader>` or
     :ref:`configuration update <replication-configuration_update>`.
     Setting ``replication_connect_quorum`` to ``0`` makes Tarantool
@@ -580,7 +580,7 @@
 
     Since version :doc:`2.6.1 </release/2.6.1>`.
 
-    Specifies the role of a replica set node in the
+    Specify the role of a replica set node in the
     :ref:`leader election process <repl_leader_elect>`.
 
     Possible values:
@@ -630,7 +630,7 @@
 
     Since version :doc:`2.6.1 </release/2.6.1>`.
 
-    Specifies the timeout between election rounds in the
+    Specify the timeout between election rounds in the
     :ref:`leader election process <repl_leader_elect>` if the previous round
     ended up with a split-vote.
 
@@ -664,7 +664,7 @@
 
     In earlier Tarantool versions, use :ref:`election_fencing_enabled <cfg_election-election_fencing_enabled_deprecated>` instead.
 
-    Specifies the :ref:`leader fencing mode <repl_leader_elect_fencing>` that
+    Specify the :ref:`leader fencing mode <repl_leader_elect_fencing>` that
     affects the leader election process. When the parameter is set to ``soft``
     or ``strict``, the leader resigns its leadership if it has less than
     :ref:`replication_synchro_quorum <cfg_replication-replication_synchro_quorum>`

doc/reference/configuration/cfg_storage.rst

@@ -72,7 +72,7 @@
 
     Since version :doc:`2.10.0 </release/2.10.0>`.
 
-    Specifies the allocator used for memtx tuples.
+    Specify the allocator used for memtx tuples.
     The possible values are ``system``  and ``small``:
 
     * ``system`` is based on the ``malloc`` function.
@@ -109,7 +109,7 @@
 
     Since version :doc:`2.8.1 </release/2.8.1>`.
 
-    Specifies the granularity (in bytes) of memory allocation in the :ref:`small allocator <cfg_storage-memtx_allocator>`.
+    Specify the granularity (in bytes) of memory allocation in the :ref:`small allocator <cfg_storage-memtx_allocator>`.
     The value of ``slab_alloc_granularity`` should be a power of two and should be greater than or equal to 4.
     Below are few recommendations on how to adjust the ``slab_alloc_granularity`` value: