fix(docs): Standardize all internal links

docs/docs/behaviors/bluetooth.md

@@ -84,5 +84,5 @@ ZMK support bluetooth “profiles” which allows connection to multiple devices
 The bluetooth MAC address and negotiated keys during pairing are stored in the permanent storage on your chip and can be reused even after reflashing the firmware. If for some reason you want to delete the stored information, you can bind the `BT_CLR` behavior described above to a key and use it to clear the _current_ profile.
 
 :::note
-If you clear bond of a paired profile, make sure you do the same thing on the peer device as well (typically achieved by _removing_ or _forgetting_ the bluetooth connection). Otherwise the peer will try to connect to your keyboard whenever it discovers it. But while the MAC address of both devices could remain the same, the security key no longer match: the peer device still possess the old key negotiated in the previous pairing procedure, but our keyboard firmware has deleted that key. So the connection will fail. If you [enabled USB logging](../development/usb-logging), you might see a lot of failed connection attempts due to the reason of “Security failed”.
+If you clear bond of a paired profile, make sure you do the same thing on the peer device as well (typically achieved by _removing_ or _forgetting_ the bluetooth connection). Otherwise the peer will try to connect to your keyboard whenever it discovers it. But while the MAC address of both devices could remain the same, the security key no longer match: the peer device still possess the old key negotiated in the previous pairing procedure, but our keyboard firmware has deleted that key. So the connection will fail. If you [enabled USB logging](../development/usb-logging.md), you might see a lot of failed connection attempts due to the reason of “Security failed”.
 :::

docs/docs/behaviors/hold-tap.md

@@ -33,7 +33,7 @@ When the hold-tap key is released and the hold behavior has not been triggered,
 
 ### Basic usage
 
-For basic usage, please see [mod-tap](./mod-tap.md) and [layer-tap](./layers.md) pages.
+For basic usage, please see [mod-tap](mod-tap.md) and [layer-tap](layers.md) pages.
 
 ### Advanced Configuration
 

docs/docs/behaviors/key-press.md

@@ -10,14 +10,14 @@ a certain key.
 
 The categories of supported codes are:
 
-- [Keyboard & Keypad](../codes/keyboard-keypad)
-- [Editing](../codes/editing)
-- [Media](../codes/media)
-- [Applications](../codes/applications)
-- [Input Assist](../codes/input-assist)
-- [Power](../codes/power)
+- [Keyboard & Keypad](../codes/keyboard-keypad.mdx)
+- [Editing](../codes/editing.mdx)
+- [Media](../codes/media.mdx)
+- [Applications](../codes/applications.mdx)
+- [Input Assist](../codes/input-assist.mdx)
+- [Power](../codes/power.mdx)
 
-Please visit the [codes](../codes) section for a comprehensive list.
+Please visit the [codes](../codes/index.mdx) section for a comprehensive list.
 
 For advanced users, user-defined HID usages are also supported but must be encoded, please see [`dt-bindings/zmk/keys.h`](https://github.com/zmkfirmware/zmk/blob/main/app/include/dt-bindings/zmk/keys.h) for further insight.
 
@@ -36,7 +36,7 @@ Doing so makes a set of defines such as `A`, `N1`, etc. available for use with t
 ### Improperly defined keymap - `dtlib.DTError: <board>.dts.pre.tmp:<line number>`
 
 When compiling firmware from a keymap, it may be common to encounter an error in the form of a`dtlib.DTError: <board>.dts.pre.tmp:<line number>`.
-For instructions to resolve such an error, click [here](../troubleshooting###Improperly-defined-keymap)
+For instructions to resolve such an error, click [here](../troubleshooting.md###Improperly-defined-keymap)
 
 ## Key Press
 

docs/docs/behaviors/layers.md

@@ -43,7 +43,7 @@ Example:
 
 ## Layer-tap
 
-The "layer-tap" behavior enables a layer when a key is held, and output another key when the key is only tapped for a short time. For more information on the inner workings of layer-tap, see [hold-tap](./hold-tap.md).
+The "layer-tap" behavior enables a layer when a key is held, and output another key when the key is only tapped for a short time. For more information on the inner workings of layer-tap, see [hold-tap](hold-tap.md).
 
 ### Behavior Binding
 

docs/docs/behaviors/mod-tap.md

@@ -46,4 +46,4 @@ You can configure a different tapping term in your keymap:
 
 ### Additional information
 
-The mod-tap is a [hold-tap](./hold-tap.md) under the hood with the "balanced" flavor and tapping-term-ms 200.
+The mod-tap is a [hold-tap](hold-tap.md) under the hood with the "balanced" flavor and tapping-term-ms 200.