diff --git a/docker/main/rootfs/etc/s6-overlay/s6-rc.d/go2rtc/run b/docker/main/rootfs/etc/s6-overlay/s6-rc.d/go2rtc/run
index 2c3a7ab6f..46bc3175f 100755
--- a/docker/main/rootfs/etc/s6-overlay/s6-rc.d/go2rtc/run
+++ b/docker/main/rootfs/etc/s6-overlay/s6-rc.d/go2rtc/run
@@ -61,7 +61,7 @@ if [[ ! -f "/dev/shm/go2rtc.yaml" ]]; then
     echo "[INFO] Preparing new go2rtc config..."
 
     if [[ -n "${SUPERVISOR_TOKEN:-}" ]]; then
-        # Running as a Home Assistant add-on, infer the IP address and port
+        # Running as a Home Assistant Add-on, infer the IP address and port
         get_ip_and_port_from_supervisor
     fi
 
diff --git a/docker/main/rootfs/etc/s6-overlay/s6-rc.d/prepare/run b/docker/main/rootfs/etc/s6-overlay/s6-rc.d/prepare/run
index 6b52bc848..02e5bb621 100755
--- a/docker/main/rootfs/etc/s6-overlay/s6-rc.d/prepare/run
+++ b/docker/main/rootfs/etc/s6-overlay/s6-rc.d/prepare/run
@@ -8,7 +8,7 @@ function migrate_addon_config_dir() {
     local home_assistant_config_dir="/homeassistant"
 
     if ! mountpoint --quiet "${home_assistant_config_dir}"; then
-        # Not running as a Home Assistant add-on
+        # Not running as a Home Assistant Add-on
         return 0
     fi
 
@@ -99,7 +99,7 @@ function migrate_addon_config_dir() {
     echo "[INFO] Migrating config file from '${old_config_file}' to '${new_config_file}'..."
     mv -vf "${old_config_file}" "${new_config_file}"
 
-    echo "[INFO] Migration from Home Assistant config dir to add-on config dir completed."
+    echo "[INFO] Migration from Home Assistant config dir to Add-on config dir completed."
 }
 
 function migrate_db_from_media_to_config() {
diff --git a/docs/docs/configuration/live.md b/docs/docs/configuration/live.md
index 48ec8944d..cc46dec58 100644
--- a/docs/docs/configuration/live.md
+++ b/docs/docs/configuration/live.md
@@ -121,9 +121,9 @@ WebRTC works by creating a TCP or UDP connection on port `8555`. However, it req
 
 :::tip
 
-This extra configuration may not be required if Frigate has been installed as a Home Assistant add-on, as Frigate uses the Supervisor's API to generate a WebRTC candidate.
+This extra configuration may not be required if Frigate has been installed as a Home Assistant Add-on, as Frigate uses the Supervisor's API to generate a WebRTC candidate.
 
-However, it is recommended if issues occur to define the candidates manually. You should do this if the Frigate add-on fails to generate a valid candidate. If an error occurs you will see some warnings like the below in the add-on logs page during the initialization:
+However, it is recommended if issues occur to define the candidates manually. You should do this if the Frigate Add-on fails to generate a valid candidate. If an error occurs you will see some warnings like the below in the Add-on logs page during the initialization:
 
 ```log
 [WARN] Failed to get IP address from supervisor
diff --git a/docs/docs/integrations/home-assistant.md b/docs/docs/integrations/home-assistant.md
index 26fc0e23a..c5feda81a 100644
--- a/docs/docs/integrations/home-assistant.md
+++ b/docs/docs/integrations/home-assistant.md
@@ -93,7 +93,7 @@ services:
 
 ### Home Assistant Add-on
 
-If you are using Home Assistant Add-on, the URL should be one of the following depending on which add-on variant you are using. Note that if you are using the Proxy Add-on, you should NOT point the integration at the proxy URL. Just enter the same URL used to access Frigate directly from your network.
+If you are using Home Assistant Add-on, the URL should be one of the following depending on which Add-on variant you are using. Note that if you are using the Proxy Add-on, you should NOT point the integration at the proxy URL. Just enter the same URL used to access Frigate directly from your network.
 
 | Add-on Variant             | URL                                       |
 | -------------------------- | ----------------------------------------- |