aboutsummaryrefslogtreecommitdiff
path: root/docs/feature_tri_layer.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/feature_tri_layer.md')
-rw-r--r--docs/feature_tri_layer.md10
1 files changed, 6 insertions, 4 deletions
diff --git a/docs/feature_tri_layer.md b/docs/feature_tri_layer.md
index 3087fb5a55..a67ec97a89 100644
--- a/docs/feature_tri_layer.md
+++ b/docs/feature_tri_layer.md
@@ -1,4 +1,4 @@
-# Tri Layers :id=tri-layers
+# Tri Layers {#tri-layers}
This enables support for the OLKB style "Tri Layer" keycodes. These function similar to the `MO` (momentary) function key, but if both the "Lower" and "Upper" keys are pressed, it activates a third "Adjust" layer. To enable this functionality, add this line to your `rules.mk`:
@@ -8,9 +8,9 @@ TRI_LAYER_ENABLE = yes
Note that the "upper", "lower" and "adjust" names don't have a particular significance, they are just used to identify and clarify the behavior. Layers are processed from highest numeric value to lowest, however the values are not required to be consecutive.
-For a detailed explanation of how the layer stack works, check out [Keymap Overview](keymap.md#keymap-and-layers).
+For a detailed explanation of how the layer stack works, check out [Keymap Overview](keymap#keymap-and-layers).
-## Keycodes :id=keycodes
+## Keycodes {#keycodes}
| Keycode | Alias | Description |
|----------------------|-----------|---------------------------------------------------------------------------------------------------------|
@@ -45,4 +45,6 @@ Eg, if you wanted to set the "Adjust" layer to be layer 5, you'd add this to you
| `get_tri_layer_upper_layer()` | Gets the current "upper" layer. |
| `get_tri_layer_adjust_layer()` | Gets the current "adjust" layer. |
-!> Note: these settings are not persistent, and will be reset to the default on power loss or power cycling of the controller.
+::: warning
+Note: these settings are not persistent, and will be reset to the default on power loss or power cycling of the controller.
+:::