docs: audit and fix stale references from recent changes (#5555)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: jamesarich

docs/ar-rSA/user/connections.md

@@ -22,7 +22,7 @@ Bluetooth Low Energy is the default and most common connection method on Android
 ### Pairing a Device
 
 1. Ensure your Meshtastic radio is powered on and in pairing mode.
-2. Open the app and navigate to **Connections**.
+2. Open the app and navigate to the **Connect** tab.
 3. Tap **Scan for Devices** — nearby Meshtastic radios will appear.
 4. Select your device from the list.
 5. Accept the Bluetooth pairing prompt if shown.
@@ -77,7 +77,7 @@ Some Meshtastic radios support WiFi connectivity, allowing TCP-based connections
 ### Configuration
 
 1. Connect your radio to a WiFi network via the radio's web interface or settings.
-2. In the app, go to **Connections → TCP**.
+2. In the app, go to **Connect → TCP**.
 3. Enter the radio's IP address and port (default: 4403).
 4. Tap **Connect**.
 
@@ -99,9 +99,9 @@ A successful connection is confirmed with a status indicator:
 
 ## Reconnection Behavior
 
-The app reconnects to the **last selected device** on startup. You can manually switch transports from the connections screen at any time.
+The app reconnects to the **last selected device** on startup. You can switch transports from the Connect screen at any time.
 
-To disconnect from a radio, use the disconnect button on the connections screen:
+To disconnect from a radio, tap the disconnect button on the Connect screen:
 
 ![Disconnect from radio](../../assets/screenshots/connections_disconnect.png)
 

docs/ar-rSA/user/desktop.md

@@ -45,7 +45,7 @@ The most reliable connection method on Desktop:
 
 1. Connect your Meshtastic radio via USB cable.
 2. The app should detect the serial port automatically.
-3. If not detected, select the correct serial port from the connections menu.
+3. If not detected, select the correct serial port from the Connect menu.
 
 ### TCP/IP
 
@@ -60,7 +60,7 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/
 
 1. Ensure your system has a Bluetooth adapter.
 2. The app scans for nearby Meshtastic radios automatically.
-3. Select your device from the connections screen.
+3. Select your device from the Connect screen.
 
 ## Feature Parity
 
@@ -88,10 +88,10 @@ The Desktop app uses the same Compose Multiplatform UI with adaptations for larg
 | ------------------- | --------------------------- |
 | **⌘Q** / **Ctrl+Q** | Quit the application        |
 | **⌘,** / **Ctrl+,** | Open Settings               |
-| **⌘1** / **Ctrl+1** | Switch to Conversations tab |
+| **⌘1** / **Ctrl+1** | Switch to Messages tab |
 | **⌘2** / **Ctrl+2** | Switch to Nodes tab         |
 | **⌘3** / **Ctrl+3** | Switch to Map tab           |
-| **⌘4** / **Ctrl+4** | Switch to Connections tab   |
+| **⌘4** / **Ctrl+4** | Switch to Connect tab   |
 
 ### Window & System Tray
 

docs/ar-rSA/user/nodes.md

@@ -86,11 +86,12 @@ From the node list, you can:
 
 - **Tap** a node to view its detail page
 - **Long-press** for quick actions:
+  - Mark/remove favorite
+  - Mute/unmute notifications
   - Send a direct message
-  - View on map
-  - Request position
-  - Mark as favorite
-  - Traceroute
+  - Trace route
+  - Ignore/unignore
+  - Remove node
 
 ## Filtering & Sorting
 

docs/ar-rSA/user/settings-module-admin.md

@@ -235,7 +235,7 @@ View detailed diagnostic information:
 
 - **"No response from target node"** — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
 - **Changes not applying** — some settings require a reboot to take effect. Try the Reboot action after saving.
-- **Can't see remote settings** — ensure your node has the admin key for the target node and that Admin Channel is enabled in Security Config.
+- **Can't see remote settings** — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
 
 ## Related Topics
 

docs/ar-rSA/user/settings-radio-user.md

@@ -148,7 +148,7 @@ The modem preset controls the fundamental tradeoff between **range** and **data
 | Public Key            | Your node's public key (read-only)                      |
 | Admin Key             | Key for remote administration                                              |
 | Private Key           | Your node's private key (handle securely)               |
-| Admin Channel Enabled | Allow admin commands via channel                                           |
+| ~~Admin Channel Enabled~~ | ⚠️ **Removed** — this toggle has been removed from the UI; admin channel behavior is now handled automatically |
 | Debug Log             | Output live debug logging over serial/bluetooth                            |
 | Serial Enabled        | Enable serial console access (moved from Device Config) |
 | Managed Mode          | Restrict non-admin channel changes                                         |

docs/be-rBY/user/connections.md

@@ -22,7 +22,7 @@ Bluetooth Low Energy is the default and most common connection method on Android
 ### Pairing a Device
 
 1. Ensure your Meshtastic radio is powered on and in pairing mode.
-2. Open the app and navigate to **Connections**.
+2. Open the app and navigate to the **Connect** tab.
 3. Tap **Scan for Devices** — nearby Meshtastic radios will appear.
 4. Select your device from the list.
 5. Accept the Bluetooth pairing prompt if shown.
@@ -77,7 +77,7 @@ Some Meshtastic radios support WiFi connectivity, allowing TCP-based connections
 ### Конфигурация
 
 1. Connect your radio to a WiFi network via the radio's web interface or settings.
-2. In the app, go to **Connections → TCP**.
+2. In the app, go to **Connect → TCP**.
 3. Enter the radio's IP address and port (default: 4403).
 4. Tap **Connect**.
 
@@ -99,9 +99,9 @@ A successful connection is confirmed with a status indicator:
 
 ## Reconnection Behavior
 
-The app reconnects to the **last selected device** on startup. You can manually switch transports from the connections screen at any time.
+The app reconnects to the **last selected device** on startup. You can switch transports from the Connect screen at any time.
 
-To disconnect from a radio, use the disconnect button on the connections screen:
+To disconnect from a radio, tap the disconnect button on the Connect screen:
 
 ![Disconnect from radio](../../assets/screenshots/connections_disconnect.png)
 

docs/be-rBY/user/desktop.md

@@ -45,7 +45,7 @@ The most reliable connection method on Desktop:
 
 1. Connect your Meshtastic radio via USB cable.
 2. The app should detect the serial port automatically.
-3. If not detected, select the correct serial port from the connections menu.
+3. If not detected, select the correct serial port from the Connect menu.
 
 ### TCP/IP
 
@@ -60,7 +60,7 @@ Bluetooth Low Energy is supported on Desktop via the [Kable](https://github.com/
 
 1. Ensure your system has a Bluetooth adapter.
 2. The app scans for nearby Meshtastic radios automatically.
-3. Select your device from the connections screen.
+3. Select your device from the Connect screen.
 
 ## Feature Parity
 
@@ -88,10 +88,10 @@ The Desktop app uses the same Compose Multiplatform UI with adaptations for larg
 | ------------------- | --------------------------- |
 | **⌘Q** / **Ctrl+Q** | Quit the application        |
 | **⌘,** / **Ctrl+,** | Open Settings               |
-| **⌘1** / **Ctrl+1** | Switch to Conversations tab |
+| **⌘1** / **Ctrl+1** | Switch to Messages tab |
 | **⌘2** / **Ctrl+2** | Switch to Nodes tab         |
 | **⌘3** / **Ctrl+3** | Switch to Map tab           |
-| **⌘4** / **Ctrl+4** | Switch to Connections tab   |
+| **⌘4** / **Ctrl+4** | Switch to Connect tab   |
 
 ### Window & System Tray
 

docs/be-rBY/user/nodes.md

@@ -86,11 +86,12 @@ From the node list, you can:
 
 - **Tap** a node to view its detail page
 - **Long-press** for quick actions:
+  - Mark/remove favorite
+  - Mute/unmute notifications
   - Send a direct message
-  - View on map
-  - Request position
-  - Mark as favorite
-  - Traceroute
+  - Trace route
+  - Ignore/unignore
+  - Remove node
 
 ## Filtering & Sorting
 

docs/be-rBY/user/settings-module-admin.md

@@ -235,7 +235,7 @@ View detailed diagnostic information:
 
 - **"No response from target node"** — the target may be out of range, offline, or have a mismatched admin key. Verify the admin key matches on both nodes.
 - **Changes not applying** — some settings require a reboot to take effect. Try the Reboot action after saving.
-- **Can't see remote settings** — ensure your node has the admin key for the target node and that Admin Channel is enabled in Security Config.
+- **Can't see remote settings** — ensure your node has the admin key for the target node. The admin channel is configured automatically when an admin key is set.
 
 ## Related Topics
 

docs/be-rBY/user/settings-radio-user.md

@@ -148,7 +148,7 @@ The modem preset controls the fundamental tradeoff between **range** and **data
 | Public Key            | Your node's public key (read-only)                      |
 | Admin Key             | Key for remote administration                                              |
 | Прыватны ключ         | Your node's private key (handle securely)               |
-| Admin Channel Enabled | Allow admin commands via channel                                           |
+| ~~Admin Channel Enabled~~ | ⚠️ **Removed** — this toggle has been removed from the UI; admin channel behavior is now handled automatically |
 | Debug Log             | Output live debug logging over serial/bluetooth                            |
 | Serial Enabled        | Enable serial console access (moved from Device Config) |
 | Managed Mode          | Restrict non-admin channel changes                                         |