Add subheadings

Author: p7nov

doc/reference/tooling/tt_cli/cluster.rst

@@ -1,7 +1,7 @@
 .. _tt-cluster:
 
-Managing a cluster's configuration
-==================================
+Managing cluster configurations
+===============================
 
 .. code-block:: console
 
@@ -48,6 +48,11 @@ A URI must include a prefix that is unique for the application. It can also incl
 credentials and other connection parameters. Find the detailed
 description of the URI format in :ref:`tt-cluster-uri`.
 
+.. _tt-cluster-publish-instance:
+
+Writing configurations of specific instances
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
 In addition to whole cluster configurations, ``tt cluster publish`` can edit
 configurations of specific instances within applications. In this case, the
 source file should be a YAML file with a single :ref:`instance configuration section <configuration_overview>`,
@@ -75,6 +80,11 @@ the instance name in the ``name`` argument of the storage URI:
 
     $ tt cluster publish "http://localhost:2379/myapp?name=instance-002" instance.yaml
 
+.. _tt-cluster-publish-validation:
+
+Configuration validation
+~~~~~~~~~~~~~~~~~~~~~~~~
+
 ``tt cluster publish`` validates the provided configuration against the Tarantool
 configuration schema and aborts in case of an error. To skip the validation,
 add the ``--force`` option:
@@ -137,6 +147,11 @@ with a prefix identifying the application. For example, to print
 
     $ tt cluster show "http://localhost:2379/myapp"
 
+.. _tt-cluster-show-instance:
+
+Printing configurations of specific instances
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
 ``tt cluster show`` can print configurations of specific cluster instances. To
 print an instance configuration from a local ``config.yaml``, use the ``application:instance``
 argument:
@@ -152,6 +167,11 @@ the instance name in the ``name`` argument of the URI:
 
     $ tt cluster show "http://localhost:2379/myapp?name=instance-002"
 
+.. _tt-cluster-show-validation:
+
+Configuration validation
+~~~~~~~~~~~~~~~~~~~~~~~~
+
 To validate a cluster configuration against the Tarantool configuration schema,
 add the ``--validate`` option: