adjusted the warning about the multiple addresses and prolonged connection time
diff --git a/docs/_docs/clustering/tcp-ip-discovery.adoc b/docs/_docs/clustering/tcp-ip-discovery.adoc
index 16249ef..b47beac 100644
--- a/docs/_docs/clustering/tcp-ip-discovery.adoc
+++ b/docs/_docs/clustering/tcp-ip-discovery.adoc
@@ -7,15 +7,6 @@
Discovery SPI can be configured for Multicast and Static IP based node
discovery.
-[NOTE]
-====
-[discrete]
-You should configure multiple node addresses only if they represent some real connections which can give you more
-reliability. Setting several addresses may prolong detection of node failure. Parameters like `failureDetectionTimeout`
-work per address sequentially. If you assign, for example, two ip addresses a node, TcpDiscovery takes up to
-'failureDetectionTimeout * 2' to detect failure of this node.
-====
-
== Multicast IP Finder
`TcpDiscoveryMulticastIpFinder` uses Multicast to discover other nodes
@@ -97,7 +88,14 @@
----
--
-
+[WARNING]
+====
+[discrete]
+Provide multiple node addresses only if you are sure that those are reachable. The unreachable addresses increase the
+time it takes for the nodes to join the cluster. Let's say you set five IP addresses, and nobody listens for incoming
+connections on two addresses out of five. If Ignite starts connecting to the cluster via those two unreachable addresses,
+it will impact the node's startup time.
+====
== Multicast and Static IP Finder
