From 1b7c376e33f68701beb643129eb0f33d96f3f944 Mon Sep 17 00:00:00 2001
From: William Trelawny <22324745+willman42@users.noreply.github.com>
Date: Sun, 7 May 2023 17:28:14 -0400
Subject: [PATCH] Update traefik-v2-docker.md

Added link to Traefik docs

Signed-off-by: William Trelawny <22324745+willman42@users.noreply.github.com>
---
 docs/guides/webserver/traefik-v2-docker.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/guides/webserver/traefik-v2-docker.md b/docs/guides/webserver/traefik-v2-docker.md
index 4120105..e5e7a50 100644
--- a/docs/guides/webserver/traefik-v2-docker.md
+++ b/docs/guides/webserver/traefik-v2-docker.md
@@ -1,7 +1,7 @@
 ### Notes & Warnings
 
 - **This is an unsupported configuration created by the community**
-- This describes how to use Traefik v2 in a Docker container (via docker-compose.yml) to serve the Pi-hole web admin interface via https and includes a permenent http -> https redirect.
+- This describes how to use [Traefik](https://doc.traefik.io/traefik/) v2 in a Docker container (via docker-compose.yml) to serve the Pi-hole web admin interface via https and includes a permenent http -> https redirect.
 - This does not describe how to proxy DNS or DHCP requests to Pi-hole, which is not recommended.
 - For ACME challenges, the Traefik container may need to be able to resolve the desired Pi-hole hostname without relying on Pi-hole to do so. Provide this via the `extra_hosts` parameter in your Traefik container's config in docker-compose.yml if needed.
 - For LetsEncrypt to work Traefik must be reachable on port 80 and 443 from the Internet and have `domain.tld` pointed at its external address.