From b45a566bca509b087d0d36e5f6444fba136f9af2 Mon Sep 17 00:00:00 2001
From: Luc <luc.rousseaupro@gmail.com>
Date: Mon, 19 Jan 2026 16:55:05 +0100
Subject: [PATCH] fix broken link legacy_communication host drivers question

---
 data/1_Orchestration/legacy_communication.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/data/1_Orchestration/legacy_communication.yaml b/data/1_Orchestration/legacy_communication.yaml
index e5639ff..54e554a 100644
--- a/data/1_Orchestration/legacy_communication.yaml
+++ b/data/1_Orchestration/legacy_communication.yaml
@@ -60,7 +60,7 @@ questions:
       - { value: 'Mount a volume from the legacy system', correct: false }
       - { value: 'Use a static IP assignment or run the container with host networking', correct: true }
       - { value: 'Use dynamic IP allocation via overlay network', correct: false }
-    help: https://docs.docker.com/network/network-tutorial-host/
+    help: https://docs.docker.com/engine/network/drivers/host/
 
   - uuid: 36efbf34-91e6-49fd-9398-3948ae194c2c
     question: Which practice helps decouple Dockerized applications from legacy systems during a migration process?