From 35ee7687b655ec21ab38a8a8303643712a748c65 Mon Sep 17 00:00:00 2001
From: arretx <32052562+arretx@users.noreply.github.com>
Date: Mon, 18 Sep 2017 12:48:40 -0700
Subject: [PATCH] Spelling correction... (#3399)

Line 78 read that is, is...
---
 source/_components/alert.markdown | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/_components/alert.markdown b/source/_components/alert.markdown
index 2f3f58d5184..8967a134e5f 100644
--- a/source/_components/alert.markdown
+++ b/source/_components/alert.markdown
@@ -75,7 +75,7 @@ freshwater_temp_alert:
 
 ### {% linkable_title Complex Alert Criteria %}
 
-By design, the `alert` component only handles very simple criteria for firing. That is, is only checks if a single entity's state is equal to a value. At some point, it may be desireable to have an alert with a more complex criteria. Possibly, when a battery percentage falls below a threshold. Maybe you want to disable the alert on certain days. Maybe the alert firing should depend on more than one input. For all of these situations, it is best to use the alert in conjunction with a `Template Binary Sensor`. The following example does that.
+By design, the `alert` component only handles very simple criteria for firing. That is, it only checks if a single entity's state is equal to a value. At some point, it may be desireable to have an alert with a more complex criteria. Possibly, when a battery percentage falls below a threshold. Maybe you want to disable the alert on certain days. Maybe the alert firing should depend on more than one input. For all of these situations, it is best to use the alert in conjunction with a `Template Binary Sensor`. The following example does that.
 
 ```yaml
 binary_sensor: