From 1828841b49a5351b57f91812efbd17f307470fa6 Mon Sep 17 00:00:00 2001 From: Blake Blackshear Date: Sat, 13 Aug 2022 06:36:06 -0500 Subject: [PATCH] Typo --- docs/docs/configuration/record.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/configuration/record.md b/docs/docs/configuration/record.md index 4aae60959..7aeec9d0c 100644 --- a/docs/docs/configuration/record.md +++ b/docs/docs/configuration/record.md @@ -43,7 +43,7 @@ The same options are available with events. Let's consider a scenario where you - With the `motion` option all segments for the duration of the event with motion would be saved. This means any segment where a car drove by in the street, person walked by, lighting changed, etc. would be saved. - With the `active_objects` it would only keep segments where the object was active. In this case the only segments that would be saved would be the ones where the car was driving up, you going inside, you coming outside, and the car driving away. Essentially reducing the 4 hours to a minute or two of event footage. -A configration example of the above retain modes where all `motion` segments are stored for 7 days and `active objects` are stored for 14 days would be as follows: +A configuration example of the above retain modes where all `motion` segments are stored for 7 days and `active objects` are stored for 14 days would be as follows: ```yaml record: enabled: True