diff --git a/docs/join_cluster.md b/docs/join_cluster.md
index d6c9183f95..4cfcc3c96b 100644
--- a/docs/join_cluster.md
+++ b/docs/join_cluster.md
@@ -7,11 +7,18 @@ redirect_from:
  - /docs/join_cluster.md/
 ---
 
-## Table of Contents
+**Note**: for the most recent updates on the topic of cluster membership and node lifecycle, please also check:
 
-- [Joining a Cluster](#joining-a-cluster)
+* [Node lifecycle: maintenance mode, rebalance/rebuild, shutdown, decommission](/docs/lifecycle_node.md)
 
-## Joining a Cluster
+Also, see related:
+
+* [Leaving aistore cluster](leave_cluster.md)
+* [Global rebalance](rebalance.md)
+* [CLI: `ais cluster` command](/docs/cli/cluster.md)
+* [Scripted integration tests](https://github.com/NVIDIA/aistore/tree/main/ais/test/scripts)
+
+## Joining a Cluster: _discovery_ URL, and more
 
 First, some basic facts. AIStore clusters can be deployed with an arbitrary number of AIStore proxies. Each proxy/gateway implements RESTful API and provides full access to objects stored in the cluster. Each proxy collaborates with all other proxies to perform majority-voted HA failovers (section [Highly Available Control Plane](ha.md).
 
diff --git a/docs/leave_cluster.md b/docs/leave_cluster.md
index ee415c672a..06e3e597db 100644
--- a/docs/leave_cluster.md
+++ b/docs/leave_cluster.md
@@ -7,6 +7,17 @@ redirect_from:
  - /docs/leave_cluster.md/
 ---
 
+**Note**: for the most recent updates on the topic of cluster membership and node lifecycle, please also check:
+
+* [Node lifecycle: maintenance mode, rebalance/rebuild, shutdown, decommission](/docs/lifecycle_node.md)
+
+Also, see related:
+
+* [Joining aistore cluster](join_cluster.md)
+* [Global rebalance](rebalance.md)
+* [CLI: `ais cluster` command](/docs/cli/cluster.md)
+* [Scripted integration tests](https://github.com/NVIDIA/aistore/tree/main/ais/test/scripts)
+
 ## Table of Contents
 
 - [Putting a node in maintenance](#putting-a-node-in-maintenance)
@@ -32,7 +43,7 @@ In general, when storage targets leave (or join) the cluster, the current *prima
 This results in each AIS target starting to traverse its locally stored content, recomputing object locations, and sending at least some of the objects to their respective *new* locations.
 Object migration is then carried out via an intra-cluster optimized [communication mechanism](/transport/README.md) and over a separate [physical or logical network](/cmn/network.go), if provisioned.
 
-For more details about the rebalancing process, see [REBALANCE](/docs/rebalance.md). 
+For more details about the rebalancing process, see [REBALANCE](/docs/rebalance.md).
 
 ```console
 $ ais cluster add-remove-nodes start-maintenance 59262t8087