docs: Add warning box for clearing settings for splits, generalize troubleshooting procedure (#3039)

Co-authored-by: Nicolas Munnich <98408764+nmunnich@users.noreply.github.com>

docs/docs/config/settings.md

@@ -41,6 +41,13 @@ See example for building firmware using this shield in the [troubleshooting docs
 
 In both cases, regular, non-reset firmware will need to be flashed afterwards for normal operation.
 
+:::warning
+
+Since pairing information between split keyboards are also cleared with this process, you will need to clear settings on all parts of a split keyboard.
+Please follow the full procedure described in [troubleshooting](../troubleshooting/connection-issues.mdx#split-keyboard-parts-unable-to-pair) so that the parts can pair correctly after clearing.
+
+:::
+
 :::tip
 
 [ZMK Studio](../features/studio.md)-specific settings can be easily cleared using the "Restore Stock Settings" button in the header of the Studio client.

docs/docs/config/system.md

@@ -19,10 +19,10 @@ Definition file: [zmk/app/Kconfig](https://github.com/zmkfirmware/zmk/blob/main/
 | `CONFIG_ZMK_WPM`            | bool   | Enable calculating words per minute          | n       |
 | `CONFIG_HEAP_MEM_POOL_SIZE` | int    | Size of the heap memory pool                 | 8192    |
 
-:::tip
+:::info
 
 Because ZMK enables [the Zephyr setting](https://docs.zephyrproject.org/3.5.0/kconfig.html#CONFIG_BT_DEVICE_NAME_DYNAMIC) that allows for runtime modification of the device BT name,
-changing `CONFIG_ZMK_KEYBOARD_NAME` requires [clearing the stored settings](./settings.md) on the controller in order to take effect.
+changing `CONFIG_ZMK_KEYBOARD_NAME` requires [clearing the stored settings](./settings.md#clearing-persisted-settings) on the controller in order to take effect.
 
 :::