From eb312de8710b8e65d00bb9027cbf370b5cfb1370 Mon Sep 17 00:00:00 2001 From: Pedro Pombeiro Date: Thu, 1 Dec 2016 08:49:54 +0100 Subject: [PATCH] Fix typo (#1523) --- source/_components/proximity.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/proximity.markdown b/source/_components/proximity.markdown index 41d210174b7..3d8c45b736f 100644 --- a/source/_components/proximity.markdown +++ b/source/_components/proximity.markdown @@ -53,7 +53,7 @@ Configuration variables: - **ignored_zones** array (*Optional*): Where proximity is not calculated for a device (either the device being monitored or ones being compared (e.g. work or school). - **devices** array (*Optional*): A list of devices to compare location against to check closeness to the configured zone. - **tolerance** (*Optional*): The tolerance used to calculate the direction of travel in meters (m) to filter out small GPS coordinate changes. -- **unit_of_measurement** (*Optional*): The unit of measurement for distance. Valid values are (km, m, mi, ft) [kilometers, meters, miles and feet respectfully]. The default value is kilometers. +- **unit_of_measurement** (*Optional*): The unit of measurement for distance. Valid values are (km, m, mi, ft) [kilometers, meters, miles and feet respectively]. The default value is kilometers. To add multiple proximity components, simply use a list in your `configuration.yaml` file: