From 2fb347d7e6e69662221480f5572e91b2e41774d6 Mon Sep 17 00:00:00 2001
From: Remi Gacogne <remi.gacogne@powerdns.com>
Date: Tue, 20 May 2025 12:24:03 +0200
Subject: [PATCH] dnsdist: Apply Peter's suggestion to the advisory

Co-authored-by: Peter van Dijk <peter.van.dijk@powerdns.com>
---
 .../powerdns-advisory-for-dnsdist-2025-03.rst                   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pdns/dnsdistdist/docs/security-advisories/powerdns-advisory-for-dnsdist-2025-03.rst b/pdns/dnsdistdist/docs/security-advisories/powerdns-advisory-for-dnsdist-2025-03.rst
index e1a644a994..03ed40f3d0 100644
--- a/pdns/dnsdistdist/docs/security-advisories/powerdns-advisory-for-dnsdist-2025-03.rst
+++ b/pdns/dnsdistdist/docs/security-advisories/powerdns-advisory-for-dnsdist-2025-03.rst
@@ -21,7 +21,7 @@ In some circumstances, when DNSdist is configured to allow an unlimited number o
 
 `CVSS Score: 7.5 <https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H&version=3.1>`__
 
-The remedy is: upgrade to the patched 1.9.10 version
+The remedy is: upgrade to the patched 1.9.10 version.
 
 A workaround is to restrict the maximum number of queries on incoming TCP connections to a safe value, like 50, via the :func:`setMaxTCPQueriesPerConnection` setting.
 
-- 
2.47.2