From f68ef96546992d5c107cd2838e7a6856f051292c Mon Sep 17 00:00:00 2001
From: LRVT <21357789+l4rm4nd@users.noreply.github.com>
Date: Thu, 20 Jul 2023 17:04:29 +0200
Subject: [PATCH] Update README.md

---
 examples/traefik/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/examples/traefik/README.md b/examples/traefik/README.md
index 3b03317..f4e7d7f 100644
--- a/examples/traefik/README.md
+++ b/examples/traefik/README.md
@@ -10,9 +10,9 @@
 
 Spawning up a Traefik reverse proxy can be done in various ways. 
 
-There are options to outsorce the traefik configuration into YAML configuration files. Alternatively, the configuration parameters can be defined directly as command definitions, which are applied during runtime of the Traefik container. 
+There are options to outsource the Traefik configuration into static and dynamic YAML configuration files. Alternatively, the configuration parameters can be defined directly as command definitions, which are applied during runtime of the Traefik container. We've provided both options as Docker Compose examples.
 
-Optionally configure logrotation on your Docker host server if you've enabled Traefik access logs. See `logrotate_example.txt` as example.
+Please remember to configure logrotation on your Docker host server if you've enabled Traefik access logs. See `logrotate_example.txt` as example. The logs will increase in size and may cause disk space issues, if not handled properly.
 
 ### Spawning up Traefik with outsourced configuration files