refactor(docs): Change behavior to behaviors

Makes a better URL.
This commit is contained in:
innovaker
2020-11-11 21:25:32 +00:00
committed by Pete Johanson
parent a685d88744
commit 2871dca9bf
16 changed files with 45 additions and 45 deletions

View File

@@ -25,7 +25,7 @@ Rotation is handled separately as a type of sensor. The behavior for this is set
sensor-bindings = <BINDING CW_KEY CCW_KEY>;
```
- `BINDING`, for now, has only one behavior available; `&inc_dec_kp` for key presses (see [Key Press](/docs/behavior/key-press) for details on available keycodes).
- `BINDING`, for now, has only one behavior available; `&inc_dec_kp` for key presses (see [Key Press](/docs/behaviors/key-press) for details on available keycodes).
- `CW_KEY` is the keycode activated by a clockwise turn.
- `CCW_KEY` is the keycode activated by a counter-clockwise turn.

View File

@@ -30,7 +30,7 @@ For example, the simplest behavior in ZMK is the "key press" behavior, which res
(a certain spot on the keyboard), and when that position is pressed, send a keycode to the host, and
when the key position is released, updates the host to notify of the keycode being released.
For the full set of possible behaviors, start at the [Key Press](/docs/behavior/key-press) behavior.
For the full set of possible behaviors, start at the [Key Press](/docs/behaviors/key-press) behavior.
## Layers
@@ -148,7 +148,7 @@ Each layer should have:
1. A `bindings` property this will be a list of behaviour bindings, one for each key position for the keyboard.
1. (Optional) A `sensor-bindings` property that will be a list of behavior bindings for each sensor on the keyboard. (Currently, only encoders are supported as sensor hardware, but in the future devices like trackpoints would be supported the same way)
For the full set of possible behaviors, start at the [Key Press](/docs/behavior/key-press) behavior.
For the full set of possible behaviors, start at the [Key Press](/docs/behaviors/key-press) behavior.
### Complete Example