[master] 83e8292a2 spelling: crypto

[Poul-Henning Kamp]

commit 83e8292a28b15945bf17d0d1f26013ac7fa50a51
Author: Josh Soref <2119212+jsoref at users.noreply.github.com>
Date:   Wed Aug 7 08:30:54 2024 -0400

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

diff --git a/doc/sphinx/phk/ssl.rst b/doc/sphinx/phk/ssl.rst
index b38d9847e..581b8653a 100644
--- a/doc/sphinx/phk/ssl.rst
+++ b/doc/sphinx/phk/ssl.rst
@@ -58,7 +58,7 @@ a SSL proxy in separate process ?
 No, it will not, because the way varnish would have to do it would
 be to ... start a separate process to do the SSL handling.
 
-There is no other way we can guarantee that secret krypto-bits do
+There is no other way we can guarantee that secret crypto-bits do
 not leak anywhere they should not, than by fencing in the code that
 deals with them in a child process, so the bulk of varnish never
 gets anywhere near the certificates, not even during a core-dump.