From 5a7e3faf2f11581bd6994daea716adc13e67cb01 Mon Sep 17 00:00:00 2001
From: LRVT <21357789+l4rm4nd@users.noreply.github.com>
Date: Sat, 16 Mar 2024 02:06:08 +0100
Subject: [PATCH] Update README.md

---
 examples/arr-suite/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/examples/arr-suite/README.md b/examples/arr-suite/README.md
index 6b880de..c782755 100644
--- a/examples/arr-suite/README.md
+++ b/examples/arr-suite/README.md
@@ -58,7 +58,7 @@ You can follow this Youtube tutorial on how to setup most of the arr application
 
 https://www.youtube.com/watch?v=LD8-Qr3B2-o
 
-**Note**:  As all arr containers live within the same Docker network, you can easily reference container names instead of IPs. Docker will resolve the container names automatically to the current docker containers' IP. No need for port mappings or defining your Docker server's IP address. Use Docker networks! The only exception is qbittorrent, which uses the vpn killswitch network of the gluetun container. Here, the gluetun container will expose qbittorrent's web ui on TCP/8080.
+**Note**:  As all arr containers live within the same Docker network, you can easily reference container names instead of IPs. Docker will resolve the container names automatically to the current docker containers' IP. No need for port mappings or defining your Docker server's IP address. Use Docker networks! The only exception is qbittorrent, which uses the vpn killswitch network of the gluetun container. Here, the gluetun container will expose qbittorrent's web ui on TCP/8080 and the IP address of your docker host server. Setup qbittorrent in all arr-applications using your server's local IP address, on which port 8080 is mapped to.
 
 > [!WARNING]
 > We configured qbittorrent to use the non-default path `/media/downloads` for downloads.