From 6a34c6527af45a97874ae2cab68549e266f99150 Mon Sep 17 00:00:00 2001 From: Josh Soref <2119212+jsoref@users.noreply.github.com> Date: Thu, 3 Jul 2025 22:31:35 -0400 Subject: [PATCH] spelling: to use Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> --- pdns/dnsdistdist/docs/advanced/ocsp-stapling.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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: -- 2.47.2