Add TCM connecting clusters

Author: p7nov

doc/reference/tooling/tcm/tcm_connect_clusters.rst

@@ -23,31 +23,29 @@ There are two ways to add a cluster to |tcm|:
 
     .. note::
 
-        In this case, be sure to deploy and start Tarantool on the cluster nodes using
-        the :ref:`tt-cli` or another suitable way.
+        In the latter case, you need to deploy Tarantool and start the cluster
+        instances using the :ref:`tt-cli` or another suitable way.
 
 ..  _tcm_connect_clusters_parameters:
 
 Connection parameters
 ---------------------
 
-When connecting a cluster to |tcm|, you need to provide twp sets of connection parameters:
+When connecting a cluster to |tcm|, you need to provide two sets of connection parameters:
 for the cluster instances and for the centralized configuration storage.
 
 Configuration storage connection
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 The cluster configuration can be stored in either an :ref:`etcd <configuration_etcd>`
-cluster or separate Tarantool-based storage. In both cases, the following connection
+cluster or a separate Tarantool-based storage. In both cases, the following connection
 parameters are required:
 
-*   **Prefix**. A key prefix used to identify the cluster in the configuration storage.
+*   A key prefix used to identify the cluster in the configuration storage.
     A prefix must be unique for each cluster in storage.
-*   **Endpoints**. URIs of all instances of the configuration storage (an etcd cluster
-    or a Tarantool cluster).
-*   **Username** and **Password**. The credentials for accessing the configuration
-    storage: an `etcd user <https://etcd.io/docs/v3.5/op-guide/authentication/rbac/>`__
-    or a :ref:`Tarantool user <authentication>`.
+*   URIs of all instances of the configuration storage.
+*   The credentials for accessing the configuration storage: an `etcd user <https://etcd.io/docs/v3.5/op-guide/authentication/rbac/>`__
+    or a :ref:`Tarantool user <authentication>` and .
 
 Additionally, if SSL or TLS encryption is enabled for the configuration storage,
 provide the corresponding encryption configuration: keys, certificates, and other
@@ -85,11 +83,11 @@ follow these steps:
     *   Optionally, provide a description and select a color to mark this cluster in |tcm|.
     *   Optionally, enter the URLs of cluster instances.
 
-#.  Provide the details of the cluster configuration storage: etcd or a Tarantool-based
-    storage:
+#.  Provide the details of the cluster configuration storage:
 
-    *    The prefix specified in the cluster configuration.
-    *    The URIs of configuration storage instances.
+    *    Storage type: **etcd** or **tarantool**.
+    *    The **Prefix** specified in the cluster configuration.
+    *    The URIs of the configuration storage instances.
     *    The credentials for accessing the configuration storage.
     *    The SSL/TLS parameters if the connection encryption is enabled on the storage.
 
@@ -102,7 +100,15 @@ follow these steps:
 Adding a new cluster
 ~~~~~~~~~~~~~~~~~~~~
 
-If you don't have a cluster yet, you can start from adding it to |tcm|:
+If you don't have a cluster yet, you can add one in |tcm| and write its configuration
+from scratch using the :ref:`built-in configuration editor <tcm_configuring_clusters>.
+
+.. important::
+
+    When adding a new cluster, you need to have a storage for its configuration up
+    and running so that |tcm| can connect to it. Cluster instances can be deployed later.
+
+To add a new cluster:
 
 #.  Go to **Clusters**  and click **Add**.
 #.  Fill in the general cluster information:
@@ -111,10 +117,9 @@ If you don't have a cluster yet, you can start from adding it to |tcm|:
     *   Optionally, provide a description and select a color to mark this cluster in |tcm|.
     *   Optionally, enter the URLs of cluster instances.
 
-#.  Define a unique prefix for identifying this cluster in the configuration storage.
-
-#.  Provide the connection details for the cluster configuration storage: etcd or a Tarantool-based
-    storage.
+#.  Select the type of the cluster configuration storage: **etcd** or **tarantool**.
+#.  Define a unique **Prefix** for identifying this cluster in the configuration storage.
+#.  Provide the connection details for the cluster configuration storage:
 
     *    The URIs of configuration storage instances.
     *    The credentials for accessing the configuration storage.
@@ -126,9 +131,9 @@ If you don't have a cluster yet, you can start from adding it to |tcm|:
 
 Once you add the cluster:
 
-*   set up the cluster configuration using the |tcm| :ref:`configuration editor <tcm_cluster_config>`
-*   deploy Tarantool on the cluster nodes using the :ref:`tt-cli` or other suitable tools
-*   start the cluster instances
+*   Set up the cluster configuration using the |tcm| :ref:`configuration editor <tcm_cluster_config>`.
+*   Deploy Tarantool on the cluster nodes using the :ref:`tt-cli` or other suitable tools.
+*   Start the cluster using the :ref:`tt-cli` or other suitable tools.
 
 ..  _tcm_connect_clusters_edit: