From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Fri, 4 Jul 2025 02:31:35 +0000 (-0400)
Subject: spelling: to use
X-Git-Tag: rec-5.4.0-alpha0~40^2~5
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6a34c6527af45a97874ae2cab68549e266f99150;p=thirdparty%2Fpdns.git

spelling: to use

Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
---

diff --git a/pdns/dnsdistdist/docs/advanced/ocsp-stapling.rst b/pdns/dnsdistdist/docs/advanced/ocsp-stapling.rst
index 761525715b..98462499f7 100644
--- a/pdns/dnsdistdist/docs/advanced/ocsp-stapling.rst
+++ b/pdns/dnsdistdist/docs/advanced/ocsp-stapling.rst
@@ -31,7 +31,7 @@ Certificate signed by an external authority
 
 When the certificate has been signed by an external certification authority, the process is a bit more complicated because the OCSP needs to be retrieved from that CA, and there are very few options available to do that at the moment.
 
-One of those options is to the use the OpenSSL ocsp command-line tool, although it's a bit cumbersome to use.
+One of those options is to use the OpenSSL ocsp command-line tool, although it's a bit cumbersome to use.
 
 The first step is to retrieve the URL at which the CA provides an OCSP responder. This can be done via the OpenSSL x509 command: