diff --git a/docs/curl.1 b/docs/curl.1
index e3303a54f89038..cf37d63c92c931 100644
--- a/docs/curl.1
+++ b/docs/curl.1
@@ -548,7 +548,7 @@ used several times, the last one will be used.
 (SSL) Tells curl to use the specified public key file (or hashes) to verify the
 peer. This can be a path to a file which contains a single public key in PEM or
 DER format, or any number of base64 encoded sha256 hashes preceded by
-\'sha256//\' and seperated by \';\'
+\'sha256//\' and separated by \';\'
 
 When negotiating a TLS or SSL connection, the server sends a certificate
 indicating its identity. A public key is extracted from this certificate and
diff --git a/docs/libcurl/opts/CURLMOPT_PUSHFUNCTION.3 b/docs/libcurl/opts/CURLMOPT_PUSHFUNCTION.3
index fb5e4e49c49623..d0468ec15ecff8 100644
--- a/docs/libcurl/opts/CURLMOPT_PUSHFUNCTION.3
+++ b/docs/libcurl/opts/CURLMOPT_PUSHFUNCTION.3
@@ -69,7 +69,7 @@ multi handle, the callback must not do that by itself.
 The callback can access PUSH_PROMISE headers with two accessor
 functions. These functions can only be used from within this callback and they
 can only access the PUSH_PROMISE headers. The normal response headers will be
-pased to the header callback for pushed streams just as for normal streams.
+passed to the header callback for pushed streams just as for normal streams.
 .IP curl_pushheader_bynum
 Returns the header at index 'num' (or NULL). The returned pointer points to a
 "name:value" string that will be freed when this callback returns.
diff --git a/docs/libcurl/opts/CURLOPT_PINNEDPUBLICKEY.3 b/docs/libcurl/opts/CURLOPT_PINNEDPUBLICKEY.3
index 0d4357ab1a3d72..e3de9f2a8e94f9 100644
--- a/docs/libcurl/opts/CURLOPT_PINNEDPUBLICKEY.3
+++ b/docs/libcurl/opts/CURLOPT_PINNEDPUBLICKEY.3
@@ -31,7 +31,7 @@ CURLcode curl_easy_setopt(CURL *handle, CURLOPT_PINNEDPUBLICKEY, char *pinnedpub
 Pass a pointer to a zero terminated string as parameter. The string can be the
 file name of your pinned public key. The file format expected is "PEM" or "DER".
 The string can also be any number of base64 encoded sha256 hashes preceded by
-"sha256//" and seperated by ";"
+"sha256//" and separated by ";"
 
 When negotiating a TLS or SSL connection, the server sends a certificate
 indicating its identity. A public key is extracted from this certificate and