Adjusted Wording, Added link to GH Actions
@@ -62,13 +62,17 @@ After opening the `<board>.dts.pre.tmp:<line number>` and scrolling down to the
### Split Keyboard Halves Unable to Pair
-The previous method of pairing split keyboard halves involved a **BLE Reset** with a specific combination of held keys that would remove all bluetooth profile information from the keyboard.
+Previously, pairing split keyboard halves involved a **BLE Reset** via a combination of held keys that removed all bluetooth profile information from the keyboard.
Since then, a much simpler procedure of performing a bluetooth reset for split keyboards has come about, without the need for any file modification:
-1. Log into Github and download the "settings clear" UF2 image from latest GH actions from the `main` of ZMK
-1. Put both sides into bootloader mode
-1. Flash both sides with the "settings clear" UF2 images from step 1. After, put both sides into bootloader mode again.
-1. Flash the actual image for each half of the split keyboard
+**New Procedure:**
+
+1. Log into Github and download the "settings clear" UF2 image from the [latest build in Github Actions](https://github.com/zmkfirmware/zmk/actions?query=workflow%3ABuild+branch%3Amain)
+1. Put each half of the split keyboard into bootloader mode
+1. Flash one of the halves of the split with the "settings clear" UF2 image from step 1. Immediately after flashing "settings clear" to the chosen half, immediately put it into bootloader mode
+to avoid accidental bonding between the halves.
+1. Repeat step 3 with the other half of the split keyboard
+1. Flash the actual image for each half of the split keyboard (e.g `my_board_left.uf2` to the left half, `my_board_right.uf2` to the right half)
After completing these steps, pair the halves of the split keyboard together by resetting them at the same time. Most commonly, this is done by grounding the reset pins
for each of your keyboard's microcontrollers or pressing the reset buttons at the same time.
\ No newline at end of file
