Tidy up link names for new migration section, add _index.md

content/en/hosting/4.x/app-developer.md

@@ -1,7 +1,7 @@
 ---
 title: "App Developer Hosting in CHT 4.x"
 linkTitle: "App Developer Hosting"
-weight: 30
+weight: 10
 aliases:
   - /apps/guides/hosting/4.x/app-developer
   - /apps/guides/hosting/app-developer

content/en/hosting/4.x/migration/_index.md

@@ -0,0 +1,6 @@
+---
+title: Migration Guides
+weight: 20
+description: >
+ Guides for hosting, maintaining, and monitoring CHT applications
+---

content/en/hosting/4.x/migration/data-migration-3x-docker-to-4x-k3s-multi.md

@@ -1,10 +1,9 @@
 ---
 title: "Migration from Docker Compose CHT 3.x to 3-Node Clustered CHT 4.x on K3s"
-linkTitle: "Migration: 3.x Docker Compose to 4.x K3s (Multi-node)"
-weight: 1
+linkTitle: "To K3s Multi-node"
+weight: 10
 description: >
   Guide to migrate existing data from CHT 3.x Docker Compose deployment to CHT 4.x clustered K3s deployment with 3 CouchDB nodes
-relatedContent: >
 ---
 {{< read-content file="hosting/4.x/migration/_partial_migration_3x_docker_to_4x_k3s.md"  >}}
 

content/en/hosting/4.x/migration/data-migration-3x-docker-to-4x-k3s-single.md

@@ -1,7 +1,7 @@
 ---
 title: "Migration from 3.x Docker Compose to 4.x K3s (Single Node)"
-linkTitle: "Migration: 3.x Docker Compose to 4.x K3s (Single-Node)"
-weight: 1
+linkTitle: "To K3s Single-Node"
+weight: 20
 description: >
   Guide on how to migrate existing data from CHT 3.x Docker Compose deployment to CHT 4.x single-node K3s deployment
 relatedContent: >

content/en/hosting/4.x/migration/migration-to-4x-docker.md

@@ -1,7 +1,7 @@
 ---
 title: "Migration from CHT 3.x to CHT 4.x"
-linkTitle: "Data migration to 4.x"
-weight: 1
+linkTitle: "To Docker Single-Node"
+weight: 30
 aliases:
   - /apps/guides/hosting/4.x/data-migration
 description: >