summaryrefslogtreecommitdiff
path: root/docs/feature_backlight.md
diff options
context:
space:
mode:
authorArthur Tabatchnic <arthur@keeldocs.io>2021-04-11 13:50:45 +0300
committerGitHub <noreply@github.com>2021-04-11 12:50:45 +0200
commit0f516d902622ad4edd6e5f46a1903101b4a6f5b0 (patch)
tree2d885d63911bd8e84b6ac88ed40541cd4c415050 /docs/feature_backlight.md
parentb23eeb6a14831064578428306938d577be3b6a05 (diff)
A few small typo fixes in docs (#12524)
Diffstat (limited to 'docs/feature_backlight.md')
-rw-r--r--docs/feature_backlight.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/feature_backlight.md b/docs/feature_backlight.md
index 2adb16e4a8..74511dd43f 100644
--- a/docs/feature_backlight.md
+++ b/docs/feature_backlight.md
@@ -171,7 +171,7 @@ BACKLIGHT_DRIVER = software
#### Multiple Backlight Pins :id=multiple-backlight-pins
-Most keyboards have only one backlight pin which control all backlight LEDs (especially if the backlight is connected to an hardware PWM pin).
+Most keyboards have only one backlight pin which controls all backlight LEDs (especially if the backlight is connected to a hardware PWM pin).
In software PWM, it is possible to define multiple backlight pins, which will be turned on and off at the same time during the PWM duty cycle.
This feature allows to set, for instance, the Caps Lock LED's (or any other controllable LED) brightness at the same level as the other LEDs of the backlight. This is useful if you have mapped Control in place of Caps Lock and you need the Caps Lock LED to be part of the backlight instead of being activated when Caps Lock is on, as it is usually wired to a separate pin from the backlight.