Update docs deps (#10591)

* remove deprecated caution in facor of warning

* Update last dep

docs/docs/guides/configuring_go2rtc.md

@@ -74,7 +74,7 @@ go2rtc:
       - "ffmpeg:rtsp://user:password@10.0.10.10:554/cam/realmonitor?channel=1&subtype=2#video=copy#audio=copy#audio=aac"
 ```
 
-:::caution
+:::warning
 
 To access the go2rtc stream externally when utilizing the Frigate Add-On (for instance through VLC), you must first enable the RTSP Restream port. You can do this by visiting the Frigate Add-On configuration page within Home Assistant and revealing the hidden options under the "Show disabled ports" section.
 

docs/docs/guides/getting_started.md

@@ -245,7 +245,7 @@ Now that you have optimized your configuration for decoding the video stream, yo
 
 Now that you know where you need to mask, use the "Mask & Zone creator" in the options pane to generate the coordinates needed for your config file. More information about masks can be found [here](../configuration/masks.md).
 
-:::caution
+:::warning
 
 Note that motion masks should not be used to mark out areas where you do not want objects to be detected or to reduce false positives. They do not alter the image sent to object detection, so you can still get events and detections in areas with motion masks. These only prevent motion in these areas from initiating object detection.
 

docs/docs/guides/parked_cars.md

@@ -11,7 +11,7 @@ This is an area targeted for improvement in future releases.
 
 Many people use Frigate to detect cars entering their driveway, and they often run into an issue with repeated events of parked cars and/or long running events after the car parks. This can cause Frigate to store more video than desired.
 
-:::caution
+:::warning
 
 It is not recommended to use motion masks to try and eliminate parked cars in your driveway. Motion masks are designed to prevent motion from triggering object detection and will not prevent objects from being detected in the area if motion is detected outside of the motion mask.
 

docs/docs/guides/reverse_proxy.md

@@ -13,7 +13,7 @@ The suggested steps are:
 - **Encrypt** content from the proxy webserver by installing SSL (such as with [Let's Encrypt](https://letsencrypt.org/)). Note that SSL is then not required on your Frigate webserver as the proxy encrypts all requests for you
 - **Restrict** access to your Frigate instance at the proxy using, for example, password authentication
 
-:::caution
+:::warning
 A reverse proxy can be used to secure access to an internal webserver but the user will be entirely reliant
 on the steps they have taken. You must ensure you are following security best practices.
 This page does not attempt to outline the specific steps needed to secure your internal website.
@@ -91,7 +91,7 @@ This method shows a working example for subdomain type reverse proxy with SSL en
 
 ### Setup server and port to reverse proxy
 
-This is set in `$server` and `$port` this should match your ports you have exposed to your docker container.  Optionally you listen on port `443` and enable `SSL`
+This is set in `$server` and `$port` this should match your ports you have exposed to your docker container. Optionally you listen on port `443` and enable `SSL`
 
 ```
 # ------------------------------------------------------------
@@ -112,7 +112,7 @@ server {
 
 ### Setup SSL (optional)
 
-This section points to your SSL files, the example below shows locations to a default Lets Encrypt SSL certificate. 
+This section points to your SSL files, the example below shows locations to a default Lets Encrypt SSL certificate.
 
 ```
   # Let's Encrypt SSL
@@ -122,7 +122,6 @@ This section points to your SSL files, the example below shows locations to a de
   ssl_certificate_key /etc/letsencrypt/live/npm-1/privkey.pem;
 ```
 
-
 ### Setup reverse proxy settings
 
 The settings below enabled connection upgrade, sets up logging (optional) and proxies everything from the `/` context to the docker host and port specified earlier in the configuration