Update warning on how and when to use the unbind command

Author: NataliaIvakina

modules/ROOT/pages/tools/neo4j-admin/unbind.adoc

@@ -5,6 +5,16 @@
 
 You can use the `neo4j-admin server unbind` command to remove and archive the cluster state of a cluster server so that it can rebind to a cluster.
 
+[WARNING]
+====
+Avoid running the `unbind` command on all servers, as this results in the loss of cluster quorum.
+
+In Neo4j 5.x, use the `unbind` command only when troubleshooting a specific server and you need to convert it into a standalone instance.
+
+Keep in mind there is no guarantee that the allocator will reassign the same databases to this server, potentially resulting in orphaned database stores.
+The `unbind` command preserves all database stores on the server; and when the unbound server is restarted and enabled, it is seen as an entirely new server.
+====
+
 [[unbind-command-syntax]]
 == Syntax
 
@@ -69,14 +79,6 @@ You can use the `neo4j-admin server unbind` command to remove the cluster state
 To remove the cluster state of a server, run the `neo4j-admin server unbind` command from the _<NEO4J_HOME>_ folder of that server.
 When restarted, an unbound server rejoins the cluster as a new server and has to be enabled using the `ENABLE SERVER` command.
 
-[WARNING]
-====
-Note that the `unbind` command preserves all database stores on the server.
-When the unbound server is restarted and enabled, it is seen as an entirely new server.
-Therefore, there is no guarantee that the allocator will pick this server to host the same databases.
-This may lead to having orphaned database stores on this server.
-====
-
 === Turn a cluster member into a standalone server
 
 To start the Neo4j server in single (standalone) mode after unbinding it from the cluster, verify that xref:configuration/configuration-settings.adoc#config_initial.server.mode_constraint[`initial.server.mode_constraint`] is set to `NONE` in xref:configuration/neo4j-conf.adoc[The neo4j.conf file].