From d6b17924e5b2a3b282323d3e69f9e478f49ada63 Mon Sep 17 00:00:00 2001
From: BitWorker <48549636+b1tw0rker@users.noreply.github.com>
Date: Mon, 16 Oct 2023 10:02:25 +0200
Subject: [PATCH] fix: added missing closed bracket

---
 pdns/dnsdistdist/docs/guides/dns-over-https.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pdns/dnsdistdist/docs/guides/dns-over-https.rst b/pdns/dnsdistdist/docs/guides/dns-over-https.rst
index 6f4e5d16b6..eefd78864c 100644
--- a/pdns/dnsdistdist/docs/guides/dns-over-https.rst
+++ b/pdns/dnsdistdist/docs/guides/dns-over-https.rst
@@ -25,7 +25,7 @@ the call to :func:`addDOHLocal`. It is optional and defaults to ``/`` in 1.4.0,
 
 The fifth parameter, if present, indicates various options. For instance, you use it to indicate custom HTTP headers. An example is::
 
-  addDOHLocal('2001:db8:1:f00::1', '/etc/ssl/certs/example.com.pem', '/etc/ssl/private/example.com.key', "/dns", {customResponseHeaders={["x-foo"]="bar"}}
+  addDOHLocal('2001:db8:1:f00::1', '/etc/ssl/certs/example.com.pem', '/etc/ssl/private/example.com.key', "/dns", {customResponseHeaders={["x-foo"]="bar"}})
 
 A more complicated (and more realistic) example is when you want to indicate metainformation about the server, such as the stated policy (privacy statement and so on). We use the link types of RFC 8631::
 
-- 
2.47.2