From 1497c2d6b5f86a5d8e4d4695704a26d90a886131 Mon Sep 17 00:00:00 2001
From: Szilard Parrag <szilard.parrag@axoflow.com>
Date: Tue, 19 Nov 2024 09:18:30 +0100
Subject: [PATCH] fix(concepts-message-bsdsyslog): add proper link to RFC3164

Signed-off-by: Szilard Parrag <szilard.parrag@axoflow.com>
---
 .../concepts-message-bsdsyslog/_index.md                        | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/chapter-concepts/concepts-message-structure/concepts-message-bsdsyslog/_index.md b/content/chapter-concepts/concepts-message-structure/concepts-message-bsdsyslog/_index.md
index 2773e47f..0458b9d0 100644
--- a/content/chapter-concepts/concepts-message-structure/concepts-message-bsdsyslog/_index.md
+++ b/content/chapter-concepts/concepts-message-structure/concepts-message-bsdsyslog/_index.md
@@ -4,7 +4,7 @@ weight:  100
 ---
 <!-- DISCLAIMER: This file is based on the syslog-ng Open Source Edition documentation https://github.com/balabit/syslog-ng-ose-guides/commit/2f4a52ee61d1ea9ad27cb4f3168b95408fddfdf2 and is used under the terms of The syslog-ng Open Source Edition Documentation License. The file has been modified by Axoflow. -->
 
-This section describes the format of a syslog message, according to the [legacy-syslog or BSD-syslog protocol](https://tools.ietf.org/search/rfc3164). A syslog message consists of the following parts:
+This section describes the format of a syslog message, according to the [legacy-syslog or BSD-syslog protocol](https://datatracker.ietf.org/doc/rfc3164/). A syslog message consists of the following parts:
 
 - [`PRI`]({{< relref "/chapter-concepts/concepts-message-structure/concepts-message-bsdsyslog/concepts-message-bsdsyslog-pri/_index.md" >}})
 - [`HEADER`]({{< relref "/chapter-concepts/concepts-message-structure/concepts-message-bsdsyslog/concepts-message-bsdsyslog-header/_index.md" >}})