diff --git a/docs/docs/troubleshooting/faqs.md b/docs/docs/troubleshooting/faqs.md
index beaf287b6a..bba4a1c187 100644
--- a/docs/docs/troubleshooting/faqs.md
+++ b/docs/docs/troubleshooting/faqs.md
@@ -120,7 +120,7 @@ Open one of the events in Explore → **Tracking Details**. If the detection sco
 What helps:
 
 - **Improve the view** — even a small angle change that gets more of the car visible could lift scores enough to stabilize tracking.
-- **Use a more accurate model** — `yolov9` over `mobiledet` or a larger version of `yolov9`, like `yolov9-s` over `yolov9-t` (though this will increase inference time and is still trained on the same COCO dataset). Also, [Frigate+](https://frigate.video/plus) for models trained on security-camera footage and tunable to your scene. Users have reported that Frigate+ is by far the most reliable fix.
+- **Use a more accurate model** — switching from `mobiledet` to `yolov9`, or stepping up to a larger variant like `yolov9-s` over `yolov9-t`, can help (at the cost of inference time, and still on the COCO dataset). The biggest gains usually come from fine-tuning a model on images from your own cameras so it learns your specific scene. [Frigate+](https://frigate.video/plus) is a paid option that does this - models are trained on security-camera footage and can be fine-tuned on images you submit from your own setup.
 - **Don't set `detect -> stationary -> max_frames` for `car`** — it artificially ends tracking and forces re-detection as a new object. See [Stationary Objects](../configuration/stationary_objects.md).
 - **Restrict alerts to the areas you care about** with `required_zones` — see [Zones](../configuration/zones.md#restricting-alerts-and-detections-to-specific-zones). Make sure those zones use the default `loitering_time: 0` unless you specifically want the review item to stay open until the car leaves.
 - **Filter impossible locations** with [object filter masks](../configuration/masks.md#object-filter-masks) if cars are being detected on rooftops, treetops, etc.