small docs typo fix for zones (#10549)

* Update zones.md

* Update zones.md round 2

docs/docs/configuration/zones.md

@@ -19,17 +19,18 @@ To create a zone, follow [the steps for a "Motion mask"](masks.md), but use the
 Often you will only want events to be created when an object enters areas of interest. This is done using zones along with setting required_zones. Let's say you only want to be notified when an object enters your entire_yard zone, the config would be:
 
 ```yaml
-camera:
-  record:
-    events:
+cameras:
+  name_of_your_camera:
+    record:
+      events:
+        required_zones:
+          - entire_yard
+    snapshots:
       required_zones:
         - entire_yard
-  snapshots:
-    required_zones:
-      - entire_yard
-  zones:
-    entire_yard:
-      coordinates: ...
+    zones:
+      entire_yard:
+        coordinates: ...
 ```
 
 ### Restricting zones to specific objects
@@ -37,25 +38,26 @@ camera:
 Sometimes you want to limit a zone to specific object types to have more granular control of when events/snapshots are saved. The following example will limit one zone to person objects and the other to cars.
 
 ```yaml
-camera:
-  record:
-    events:
+cameras:
+  name_of_your_camera:
+    record:
+      events:
+        required_zones:
+          - entire_yard
+          - front_yard_street
+    snapshots:
       required_zones:
         - entire_yard
         - front_yard_street
-  snapshots:
-    required_zones:
-      - entire_yard
-      - front_yard_street
-  zones:
-    entire_yard:
-      coordinates: ... (everywhere you want a person)
-      objects:
-        - person
-    front_yard_street:
-      coordinates: ... (just the street)
-      objects:
-        - car
+    zones:
+      entire_yard:
+        coordinates: ... (everywhere you want a person)
+        objects:
+          - person
+      front_yard_street:
+        coordinates: ... (just the street)
+        objects:
+          - car
 ```
 
 Only car objects can trigger the `front_yard_street` zone and only person can trigger the `entire_yard`. You will get events for person objects that enter anywhere in the yard, and events for cars only if they enter the street.
@@ -65,12 +67,13 @@ Only car objects can trigger the `front_yard_street` zone and only person can tr
 Sometimes objects are expected to be passing through a zone, but an object loitering in an area is unexpected. Zones can be configured to have a minimum loitering time before the object will be considered in the zone.
 
 ```yaml
-camera:
-  zones:
-    sidewalk:
-      loitering_time: 4 # unit is in seconds
-      objects:
-        - person
+cameras:
+  name_of_your_camera:
+    zones:
+      sidewalk:
+        loitering_time: 4 # unit is in seconds
+        objects:
+          - person
 ```
 
 ### Zone Inertia
@@ -78,21 +81,23 @@ camera:
 Sometimes an objects bounding box may be slightly incorrect and the bottom center of the bounding box is inside the zone while the object is not actually in the zone. Zone inertia helps guard against this by requiring an object's bounding box to be within the zone for multiple consecutive frames. This value can be configured:
 
 ```yaml
-camera:
-  zones:
-    front_yard:
-      inertia: 3
-      objects:
-        - person
+cameras:
+  name_of_your_camera:
+    zones:
+      front_yard:
+        inertia: 3
+        objects:
+          - person
 ```
 
 There may also be cases where you expect an object to quickly enter and exit a zone, like when a car is pulling into the driveway, and you may want to have the object be considered present in the zone immediately:
 
 ```yaml
-camera:
-  zones:
-    driveway_entrance:
-      inertia: 1
-      objects:
-        - car
+cameras:
+  name_of_your_camera:
+    zones:
+      driveway_entrance:
+        inertia: 1
+        objects:
+          - car
 ```