CrateDB 3.x: Tune down content, as we are three versions ahead

Author: amotl

docs/admin/clustering/multi-node-setup.md

@@ -188,11 +188,6 @@ You must configure every node with a list of seed nodes. Each node
 discovers the rest of the cluster via the seed nodes.
 :::
 
-:::{TIP}
-If you are using CrateDB 3.x or below, you can use the
-[discovery.zen.ping.unicast.hosts] setting instead of
-{ref}`crate-reference:discovery.seed_hosts`.
-:::
 
 (unicast-discovery)=
 
@@ -294,11 +289,6 @@ CrateDB requires a [quorum] of nodes before a master can be elected. A quorum
 ensures that the cluster does not elect multiple masters in the event of a
 network partition (also known as a [split-brain] scenario).
 
-CrateDB (versions 4.x and above) will automatically determine the ideal [quorum
-size][quorum size], but if you are using CrateDB versions 3.x and below, you must manually set
-the quorum size using the [discovery.zen.minimum_master_nodes] setting. For
-a three-node cluster, you must declare all nodes to be master-eligible.
-
 (metadata-gateway)=
 
 #### Metadata gateway
@@ -432,6 +422,17 @@ transport.publish_port: 4321
 {ref}`More information about port settings <crate-reference:conf_ports>`
 :::
 
+## CrateDB 3.x
+
+CrateDB (versions 4.x and above) will automatically determine the ideal [quorum
+size][quorum size], but if you are using CrateDB versions 3.x and below, you
+must manually set the quorum size using the [discovery.zen.minimum_master_nodes]
+setting. For a three-node cluster, you must declare all nodes to be master-eligible.
+
+If you are using CrateDB 3.x or below, to configure every node with a list of
+seed nodes, you can use the [discovery.zen.ping.unicast.hosts] setting instead
+of {ref}`crate-reference:discovery.seed_hosts`.
+
 
 [127.0.0.1:4200]: http://127.0.0.1:4200/
 [127.0.0.1:4201]: http://127.0.0.1:4201/

docs/admin/clustering/scale/kubernetes.md

@@ -126,6 +126,7 @@ versions 4.x and above. Please refer to the current documentation section
 about {ref}`crate-reference:conf_discovery`.
 :::
 
+::::{dropdown} Details about `discovery.zen.minimum_master_nodes` on CrateDB 3.x
 The [discovery.zen.minimum_master_nodes] setting affects {ref}`metadata
 master <crate-reference:concept-clusters>` election with previous versions
 of CrateDB.
@@ -142,8 +143,8 @@ reconfiguration by altering the `discovery.zen.minimum_master_nodes` command
 option.
 
 Changes to the Kubernetes controller configuration can then be deployed using
-`kubectl replace` as shown in the previous subsection, [Using Version
-Control][using version control].
+`kubectl replace` as shown in the previous subsection, {ref}`using version
+control <scaling-kube-vc>`.
 
 :::{CAUTION}
 If [discovery.zen.minimum_master_nodes] is set to more than the current
@@ -154,6 +155,8 @@ Accordingly, it is important to adjust this number carefully when
 scaling CrateDB.
 :::
 
+::::
+
 (scaling-kube-recovery)=
 
 ### Recovery behavior
@@ -175,8 +178,8 @@ reconfiguration by altering the `EXPECTED_NODES` environment variable and the
 `recover_after_data_nodes` command option.
 
 Changes to the Kubernetes controller configuration can then be deployed using
-`kubectl replace` as shown in the previous subsection, [Using Version
-Control][using version control].
+`kubectl replace` as shown in the previous subsection, {ref}`using version
+control <scaling-kube-vc>`.
 
 :::{NOTE}
 You can scale a CrateDB cluster without updating these values, but the