From 6d8079ca7757e8ee1521c53f1868230c057a02fe Mon Sep 17 00:00:00 2001 From: Greg Stevenson Date: Sun, 16 Oct 2016 16:58:11 +0100 Subject: [PATCH] Typo and grammatical updates on keyboard component (#1253) --- source/_components/keyboard_remote.markdown | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/source/_components/keyboard_remote.markdown b/source/_components/keyboard_remote.markdown index 21e41b58cb9..f5fdf73b1e0 100644 --- a/source/_components/keyboard_remote.markdown +++ b/source/_components/keyboard_remote.markdown @@ -15,11 +15,9 @@ ha_iot_class: "Local Push" Receive signals from a keyboard and use it as a remote control. -This component allows to use a keyboard as remote control. It will fire `keyboard_remote_command_received` events witch can then be used -in automation rules. +This component allows you to use a keyboard as remote control. It will fire `keyboard_remote_command_received` events which can then be used in automation rules. -The `evdev` package is used to interface with the keyboard and thus this is Linux only. It also means you can't use your normal keyboard for this, -because `evdev` will block it. +The `evdev` package is used to interface with the keyboard and thus this is Linux only. It also means you can't use your normal keyboard for this because `evdev` will block it. ```yaml @@ -34,11 +32,11 @@ Configuration variables: - **device_descriptor** (*Required*): List of URLS for your feeds. - **key_value** (*Required*): Possible values are `key_up`, `key_down`, and `key_hold`. Be careful, `key_hold` will fire a lot of events. -And an automation rule to bring breath live into it. +And an automation rule to breathe life into it: ```yaml automation: - alias: Keyboard All light on + alias: Keyboard all lights on trigger: platform: event event_type: keyboard_remote_command_received