From 88e893e47e428fbc48983ba01269c30daf1cd8c4 Mon Sep 17 00:00:00 2001 From: Pete Johanson Date: Mon, 16 Dec 2024 18:49:55 -0500 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Cem Aksoylar --- docs/docs/keymaps/input-processors/behaviors.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/keymaps/input-processors/behaviors.md b/docs/docs/keymaps/input-processors/behaviors.md index 66d26da0a8e..849a3aeb4af 100644 --- a/docs/docs/keymaps/input-processors/behaviors.md +++ b/docs/docs/keymaps/input-processors/behaviors.md @@ -9,7 +9,7 @@ The behaviors input processor is used invoke standard behaviors when certain inp :::note -The behaviors input processor is primarily intended for `INPUT_EV_KEY` type of events that have a binary on/off state, not vector types for relative or absolute movements. +This input processor is primarily intended for `INPUT_EV_KEY` type of events that have a binary on/off state, not vector types for relative or absolute movements. ::: @@ -37,7 +37,7 @@ Should you wish to update the existing instance to trigger different behaviors f }; ``` -By default, the `bindings` property maps all the buttons to [`&none`](../behaviors/misc.md#none). +By default, the `bindings` property maps all the buttons to [`&none`](../behaviors/misc.md#none), so you will want to override the `bindings` property like above if you use this processor by assigning it to an [input listener](usage.md). ## User-Defined Instances