fix widespread naming errors across all docs — array_started, fallback, FALLBACK_

array_start.sh → array_started.sh (bulk rename — actual file has always been
array_started.sh; docs consistently used the wrong name across 9 files)

failover.sh → fallback.sh (bulk rename — script is Fallback/fallback.sh;
docs used the old name throughout)

FAILOVER_HOST2_RUNS_FOR_HOST1_TIER1 → FALLBACK_HOST2_COVERS_HOST1_TIER1
(README.md — wrong variable name, actual vars use FALLBACK_ prefix and
COVERS_ not RUNS_FOR_)

docker_watchdog.sh attribution: "started by array_started.sh" → "called every
minute by watchdog_orchestrator.sh" (docker_watchdog is not in ARRAY_START_SCRIPTS)

server_reboot.sh shutdown sequence: step 7 "rc.docker stop" → calls
array_stopping.sh (user_scripts, fallback, rsync, mover, docker_container_stop)

Rsync manual ARRAY_START_SCRIPTS list: removed stability_watchdog and
docker_watchdog (now in watchdog_orchestrator); failover → fallback

README-User_Script_Plug-in.md

@@ -95,7 +95,7 @@ Background: YES — required (starts continuous background processes)
 
 ```bash
 #!/bin/bash
-/mnt/user/appdata/unraid_scripts/Orchestrators/array_start.sh
+/mnt/user/appdata/unraid_scripts/Orchestrators/array_started.sh
 ```
 
 **What it does:**
@@ -113,7 +113,7 @@ ramdisk_setup.sh         — creates /mnt/ramdisk_transcodes and symlink before
 docker_network_connect.sh— ensures custom networks exist + containers connected
 stability_watchdog.sh   ← last-resort — three-tier server stability watchdog
 docker_watchdog.sh       ← continuous — two-tier container healing watchdog
-failover.sh              ← continuous — mutual failover state machine
+fallback.sh              ← continuous — mutual failover state machine
 ```
 
 **After running:**
@@ -659,7 +659,7 @@ that survive rsync updates without parser changes.
 ## 🔄  FAILOVER
 ## ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-> **failover.sh is started by array_start.sh — not scheduled separately.**
+> **fallback.sh is started by array_started.sh — not scheduled separately.**
 > These entries exist for manual control and testing only.
 
 ---
@@ -869,10 +869,10 @@ No profile container stop required. Incremental — safe to run at any time.
 ## 🐳  DOCKER_ESSENTIALS
 ## ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-> **docker_watchdog.sh is started by array_start.sh — not scheduled separately.**
+> **docker_watchdog.sh is called every minute by watchdog_orchestrator.sh — not scheduled separately.**
 > docker_daily_restart.sh is called by daily_sync_maintenance.sh.
 > docker_weekly_restart.sh is called by weekly_sync_maintenance.sh.
-> docker_network_connect.sh is called by array_start.sh.
+> docker_network_connect.sh is called by array_started.sh.
 > These entries exist for manual control only.
 
 ---
@@ -969,7 +969,7 @@ Dispatcharr-Basic, ErsatzTV-Emby — services that degrade with uptime.
 ```
 Category:   Docker_Essentials
 Name:       docker_network_connect_manual
-Schedule:   None — run manually (runs automatically via array_start.sh)
+Schedule:   None — run manually (runs automatically via array_started.sh)
 Background: NO
 ```
 
@@ -1143,7 +1143,7 @@ Host-aware: HOST1 manages Movies, HOST2 manages Anime_Movies.
 ## 🎬  TRANSCODES
 ## ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
-> **ramdisk_setup.sh is called by array_start.sh — not scheduled separately.**
+> **ramdisk_setup.sh is called by array_started.sh — not scheduled separately.**
 > **transcode_manager.sh and transcode_cleanup.sh are called by transcode_management.sh.**
 > These entries exist for manual status checks and emergency use.
 
@@ -1197,7 +1197,7 @@ flip count, session split ramdisk vs SSD).
 
 > **stability_watchdog.sh is called by watchdog_orchestrator.sh — not scheduled separately.**
 > **webgui_watchdog.sh, system_tuning_monitor.sh, clear_logs.sh are scheduled below.**
-> **inotify_tuning.sh, php_fpm_max_children.sh, docker_syslog_filter.sh run via array_start.sh.**
+> **inotify_tuning.sh, php_fpm_max_children.sh, docker_syslog_filter.sh run via array_started.sh.**
 
 ---
 
@@ -1616,7 +1616,7 @@ automatically at 1am as the first job in the window.
 
 **Only one entry needed at startup:** `array_start`. It handles everything.
 
-`array_start.sh` is the single "At Startup of Array" entry. It reads ARRAY_START_SCRIPTS
+`array_started.sh` is the single "At Startup of Array" entry. It reads ARRAY_START_SCRIPTS
 from master.conf and launches each in order. No other startup entries. No dragging to
 reorder individual scripts. Change the order by editing master.conf.