From 44b824c654c45fa9b5d121949bda164d810b0281 Mon Sep 17 00:00:00 2001
From: Serdar Ozmen <serdar@hazelcast.com>
Date: Tue, 27 Dec 2022 16:46:51 +0300
Subject: [PATCH] Adding missing member-list element.

---
 .../modules/clusters/pages/discovering-by-tcp.adoc | 14 ++++++++------
 1 file changed, 8 insertions(+), 6 deletions(-)

diff --git a/docs/modules/clusters/pages/discovering-by-tcp.adoc b/docs/modules/clusters/pages/discovering-by-tcp.adoc
index 6cd7295f3..3b8918214 100644
--- a/docs/modules/clusters/pages/discovering-by-tcp.adoc
+++ b/docs/modules/clusters/pages/discovering-by-tcp.adoc
@@ -29,11 +29,13 @@ XML::
     <network>
         <join>
             <tcp-ip enabled="true">
-                <member>machine1</member>
-                <member>machine2</member>
-                <member>machine3:5799</member>
-                <member>192.168.1.0-7</member>
-                <member>192.168.1.21</member>
+                <member-list>
+                    <member>machine1</member>
+                    <member>machine2</member>
+                    <member>machine3:5799</member>
+                    <member>192.168.1.0-7</member>
+                    <member>192.168.1.21</member>
+                </member-list>
             </tcp-ip>
         </join>
     </network>
@@ -75,4 +77,4 @@ By default, Hazelcast binds to all local network interfaces to accept incoming
 traffic. You can change this behavior using the system property `hazelcast.socket.bind.any`.
 If you set this property to `false`, Hazelcast uses the interfaces specified in the `interfaces`
 element (see the xref:network-configuration.adoc#interfaces[Interfaces Configuration section]). If no interfaces are
-provided, then it tries to resolve one interface to bind from the `member` elements.
\ No newline at end of file
+provided, then it tries to resolve one interface to bind from the `member` elements.