Scale: Establish dedicated section

amotl · amotl · commit fd482107ca65 · 2024-11-29T15:37:43.000+01:00
Refactor `scale-up-down.md` and `kubernetes.rst` page into dedicated
section to be able to expand it further.
diff --git a/docs/admin/clustering/index.rst b/docs/admin/clustering/index.rst
@@ -14,6 +14,6 @@ adding more nodes. This section of the documentation covers that topic.
 
    multi-node-setup
    multi-zone-setup
-   scale-up-down
-   kubernetes
+   scale/index
+   scale/kubernetes
    logical-replication-setup
diff --git a/docs/admin/clustering/scale/index.md b/docs/admin/clustering/scale/index.md
@@ -1,5 +1,5 @@
 (scaling-clusters)=
-# Scaling Clusters Up and Down
+# Scale Clusters Up and Down
 
 A significant feature in CrateDB is that it can scale horizontally, which means
 that instead of adding more RAM, CPU, and disk resources to existing nodes, you
@@ -21,7 +21,7 @@ about the corresponding details to consider.
 
 
 (scaling-ondemand)=
-## On-Demand Scaling
+## Scale On-Demand
 
 The article about [scaling CrateDB clusters up and down to cope with peaks in
 demand] shares knowledge about the [shard allocation filtering] feature of
diff --git a/docs/admin/clustering/scale/kubernetes.rst b/docs/admin/clustering/scale/kubernetes.rst
@@ -1,8 +1,8 @@
 .. _scaling-kube:
 
-=============================
-Scaling CrateDB on Kubernetes
-=============================
+===========================
+Scale CrateDB on Kubernetes
+===========================
 
 CrateDB and `Docker`_ are a great match thanks to CrateDB’s `horizontally
 scalable`_ `shared-nothing architecture`_ that lends itself well to
