dnsdist: Apply Peter's suggestion to the advisory

Co-authored-by: Peter van Dijk <peter.van.dijk@powerdns.com>

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 e1a644a9944e6b2c9c92bbcc8b42e98e41287de1..03ed40f3d0b841f63b63fdb6e925f4273a70b7c7 100644 (file)
--- 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.