3.0 configuration: update per TW review

Author: andreyaksenov

doc/how-to/replication/repl_bootstrap.rst

@@ -6,6 +6,8 @@ Master-replica: manual failover
 
 **Example on GitHub**: `manual_leader <https://github.com/tarantool/doc/tree/latest/doc/code_snippets/snippets/replication/instances.enabled/manual_leader>`_
 
+This tutorial shows how to configure a replica set with manual failover.
+
 
 ..  _replication-tt-env:
 
@@ -236,7 +238,7 @@ To check that a replica (``instance002``) gets all updates from the master, foll
 
     .. NOTE::
 
-        Note that a ``vclock`` value might include the 0-th component that is related to local space operations and might differ for different instances in a replica set.
+        Note that a ``vclock`` value might include the ``0`` component that is related to local space operations and might differ for different instances in a replica set.
 
     .. vclock_0th_component_note_end
 
@@ -298,7 +300,8 @@ Starting an instance
 Reloading configuration
 ~~~~~~~~~~~~~~~~~~~~~~~
 
-After adding ``instance003`` to the configuration and starting it, configurations on all instances should be reloaded to allow ``instance001`` and ``instance002`` to get data from the new instance in case it becomes a master:
+After you added ``instance003`` to the configuration and started it, you need to reload configurations on all instances.
+This is required to allow ``instance001`` and ``instance002`` to get data from the new instance in case it becomes a master.
 
 1.  Connect to ``instance003`` using ``tt connect``:
 

doc/how-to/replication/repl_bootstrap_auto.rst

@@ -5,6 +5,8 @@ Master-replica: automated failover
 
 **Example on GitHub**: `auto_leader <https://github.com/tarantool/doc/tree/latest/doc/code_snippets/snippets/replication/instances.enabled/auto_leader>`_
 
+This tutorial shows how to configure a replica set with automated failover.
+
 
 ..  _replication-automated-failover-tt-env:
 
@@ -178,7 +180,7 @@ Checking a replica set status
         ...
 
 4.  Execute ``box.info.replication`` to check a replica set status.
-    Make sure that ``upstream.status`` and ``downstream.status`` are ``follow`` for ``instance002`` and ``instance003``.
+    Make sure that ``upstream.status`` and ``downstream.status`` are ``follow`` for ``instance001`` and ``instance003``.
 
     .. code-block:: console
 
@@ -227,7 +229,7 @@ Checking a replica set status
 Adding data
 ~~~~~~~~~~~
 
-To check that replicas (``instance001`` and ``instance003``) get all updates from the master(``instance002``), follow the steps below:
+To check that replicas (``instance001`` and ``instance003``) get all updates from the master (``instance002``), follow the steps below:
 
 1.  Connect to ``instance002`` using ``tt connect``:
 
@@ -241,7 +243,7 @@ To check that replicas (``instance001`` and ``instance003``) get all updates fro
 
 3.  Use the ``select`` operation on ``instance001`` and ``instance003`` to make sure data is replicated.
 
-4.  Check that the 1-st component of :ref:`box.info.vclock <box_introspection-box_info>` values are the same on all instances:
+4.  Check that the ``1`` component of :ref:`box.info.vclock <box_introspection-box_info>` values are the same on all instances:
 
     -   ``instance001``:
 
@@ -368,7 +370,7 @@ To test how automated failover works if the current master is stopped, follow th
 Choosing a leader manually
 --------------------------
 
-1.  Make sure that :ref:`box.info.vclock <box_introspection-box_info>` values (excluding the 0-th components) are the same on all instances:
+1.  Make sure that :ref:`box.info.vclock <box_introspection-box_info>` values (except the ``0`` components) are the same on all instances:
 
     -   ``instance001``:
 

doc/how-to/replication/repl_bootstrap_master_master.rst

@@ -5,6 +5,8 @@ Master-master
 
 **Example on GitHub**: `master_master <https://github.com/tarantool/doc/tree/latest/doc/code_snippets/snippets/replication/instances.enabled/master_master>`_
 
+This tutorial shows how to configure a replica set with master-master configuration.
+
 
 ..  _replication-master-master-tt-env: