From 076642e33e3e13e0c90fa9502e525b1e52b550e8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C3=B6ren=20Beye?= Date: Sat, 19 Feb 2022 13:13:08 +0100 Subject: [PATCH] Improve glossary entry of add-ons (#21694) --- source/_data/glossary.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_data/glossary.yml b/source/_data/glossary.yml index ffdd7f28fc6..9a59d61a786 100644 --- a/source/_data/glossary.yml +++ b/source/_data/glossary.yml @@ -1,7 +1,7 @@ - topic: Action description: "An [Action](/docs/automation/action/) is an event that can be fired as a response to a trigger, once all conditions have been met." - topic: Add-on - description: "Add-ons provide additional, standalone, applications that can run beside Home Assistant. Most of these, add-on provided, applications can be integrated into Home Assistant using integrations. Examples of add-ons are: an MQTT broker, database service or a file server." + description: "Add-ons are additional standalone third-party software packages that can be installed on Home Assistant OS. Most of these, add-on provided, applications can be integrated into Home Assistant using integrations. Examples of add-ons are: an MQTT broker, database service or a file server." - topic: Automation description: "[Automations](/docs/automation/) connect one or more triggers to one or more actions in a 'when trigger then do action' fashion with additional optional conditions. For example, an automation might connect the trigger 'sunset' to the action 'turn the lights on' but only if the condition 'someone is home' is met. Pre-made automations for common use-cases are available via [the blueprints feature](/docs/automation/using_blueprints/)." - topic: Binary sensor