From 05f251e53762f65ee9b7bd3f536cc495a3a357d4 Mon Sep 17 00:00:00 2001 From: vMeph Date: Thu, 27 Jun 2019 20:48:50 +0100 Subject: [PATCH] Update README.md --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index a16002d..1031c78 100644 --- a/README.md +++ b/README.md @@ -5,10 +5,10 @@ A Home Assistant integration to turn your browser into a controllable entity - a ## Example uses -- Make the camera feed from your front door pop up on the tablett in your kitchen when someone rings the doorbell. +- Make the camera feed from your front door pop up on the tablet in your kitchen when someone rings the doorbell. - Have a message pop up on every screen in the house when it's bedtime. - Make the browser on your workstation switch to a specific tab when the kitchen light is on after midnight -- Play a TTS message on your work computer when the trafic sensor tells you it's time to go home. +- Play a TTS message on your work computer when the traffic sensor tells you it's time to go home. # Installation instructions @@ -31,7 +31,7 @@ The most basic concept of `browser_mod` is the *device*. A *device* is a machine-browser combination identified by a unique `deviceID`. The `deviceID` is randomly generated and may look like `ded3b4dc-abedd098`. -- Chrome on your desktop and Chrome on your laptor are two differnt *devices*. +- Chrome on your desktop and Chrome on your laptop are two different *devices*. - Chrome on your laptop and Safari on your laptop are two different *devices*. - Two tabs in Firefox on the same computer is the same *device*. - Two windows in Edge on the same computer is the same *device*. @@ -71,9 +71,9 @@ The `media_player` entity also has some extra attributes presenting the current ## `browser_mod.command` service -Call the `browser_mod.command` service to controll your *device* in various ways. +Call the `browser_mod.command` service to control your *device* in various ways. -All service calls have two parameters in common, `command` which is the command to execute, and `deviceID` which is a list of *devices* to execute the command on. If `deviceID` is ommitted, the command will be executed on **all** currently connected *devices*. +All service calls have two parameters in common, `command` which is the command to execute, and `deviceID` which is a list of *devices* to execute the command on. If `deviceID` is omitted, the command will be executed on **all** currently connected *devices*. `deviceID` may also contain aliases, and there's a special alias named `this` which will evaluate to the *device* from which a command was initiated (if from the frontend).