diff --git a/docs/docs/keymaps/behaviors/macros.md b/docs/docs/keymaps/behaviors/macros.md index a06efaf3760..391a90b7278 100644 --- a/docs/docs/keymaps/behaviors/macros.md +++ b/docs/docs/keymaps/behaviors/macros.md @@ -199,10 +199,10 @@ There are special macro controls which must be used in order to forward received For example, to pass the first parameter received into a `&kp` binding, you would use: ```dts -bindings = <¯o_param_1to1>, <&kp MACRO_PLACEHOLDER>; +bindings = <¯o_param_1to1>, <&kp PLACEHOLDER>; ``` -Because `kp` takes one parameter, you can't simply make the second entry `<&kp>` in the `bindings` list. Whatever value you do pass in will be replaced when the macro is triggered, so you can put _any_ value there, e.g. `0`, `A` keycode, etc. To make it very obvious that the parameter there is not actually going to be used, you can use `MACRO_PLACEHOLDER` which is simply an alias for `0`. +Because `kp` takes one parameter, you can't simply make the second entry `<&kp>` in the `bindings` list. Whatever value you do pass in will be replaced when the macro is triggered, so you can put _any_ value there, e.g. `0`, `A` keycode, etc. To make it very obvious that the parameter there is not actually going to be used, you can use `PLACEHOLDER` which is simply an alias for `0`. The available parameter controls are: @@ -244,14 +244,14 @@ lm: lm { #binding-cells = <2>; bindings = <¯o_param_1to1> - , <¯o_press &mo MACRO_PLACEHOLDER> + , <¯o_press &mo PLACEHOLDER> , <¯o_param_2to1> - , <¯o_press &kp MACRO_PLACEHOLDER> + , <¯o_press &kp PLACEHOLDER> , <¯o_pause_for_release> , <¯o_param_2to1> - , <¯o_release &kp MACRO_PLACEHOLDER> + , <¯o_release &kp PLACEHOLDER> , <¯o_param_1to1> - , <¯o_release &mo MACRO_PLACEHOLDER> + , <¯o_release &mo PLACEHOLDER> ; }; ```