Remove repetitive words

Signed-off-by: fanqiaojun <fanqiaojun@yeah.net>

Reviewed-by: Paul Dale <ppzgs1@gmail.com>
Reviewed-by: Tim Hudson <tjh@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/24128)

6 files changed, 6 insertions, 6 deletions

diff --git a/doc/designs/quic-design/quic-api.md b/doc/designs/quic-design/quic-api.md
index fceacdda6d..8aa972b4df 100644
--- a/doc/designs/quic-design/quic-api.md
+++ b/doc/designs/quic-design/quic-api.md
@@ -1480,7 +1480,7 @@ network BIO.)
 There are only really two ways to handle this:
 
 - **RFC conformant mode.** `SSL_shutdown` only indicates that shutdown is
-  complete once the the entire connection closure process is complete.
+  complete once the entire connection closure process is complete.
 
   This process consists of the Closing and Draining states. In some cases the
   Closing state may last only briefly, namely if the peer chooses to respond to
diff --git a/doc/designs/quic-design/record-layer.md b/doc/designs/quic-design/record-layer.md
index 172098b547..4bea5fd503 100644
--- a/doc/designs/quic-design/record-layer.md
+++ b/doc/designs/quic-design/record-layer.md
@@ -503,7 +503,7 @@ struct ossl_record_method_st {
      * which is used in a subsequent call to |release_record|. The buffer must
      * remain available until release_record is called.
      *
-     * Internally the the OSSL_RECORD_METHOD the implementation may read/process
+     * Internally the OSSL_RECORD_METHOD the implementation may read/process
      * multiple records in one go and buffer them.
      */
     int (*read_record)(OSSL_RECORD_LAYER *rl, void **rechandle, int *rversion,
diff --git a/doc/man1/openssl-s_client.pod.in b/doc/man1/openssl-s_client.pod.in
index 032edb2a36..51473a65c2 100644
--- a/doc/man1/openssl-s_client.pod.in
+++ b/doc/man1/openssl-s_client.pod.in
@@ -944,7 +944,7 @@ Reconnect to the peer and attempt a resumption handshake
 
 Send a Key Update message. TLSv1.3 only. This command takes an optional
 argument. If the argument "req" is supplied then the peer is also requested to
-update its keys. Otherwise if "noreq" is supplied the the peer is not requested
+update its keys. Otherwise if "noreq" is supplied the peer is not requested
 to update its keys. The default is "req".
 
 =item B<reneg>
diff --git a/doc/man3/EVP_EncryptInit.pod b/doc/man3/EVP_EncryptInit.pod
index 7ecfec8637..0bf10c90d7 100644
--- a/doc/man3/EVP_EncryptInit.pod
+++ b/doc/man3/EVP_EncryptInit.pod
@@ -1438,7 +1438,7 @@ indicates if the operation was successful. If it does not indicate success
 the authentication operation has failed and any output data B<MUST NOT>
 be used as it is corrupted.
 
-The API does not store the the SIV (Synthetic Initialization Vector) in
+The API does not store the SIV (Synthetic Initialization Vector) in
 the cipher text. Instead, it is stored as the tag within the EVP_CIPHER_CTX.
 The SIV must be retrieved from the context after encryption, and set into
 the context before decryption.
diff --git a/doc/man3/RAND_get0_primary.pod b/doc/man3/RAND_get0_primary.pod
index 88a2f6c311..62365a7e30 100644
--- a/doc/man3/RAND_get0_primary.pod
+++ b/doc/man3/RAND_get0_primary.pod
@@ -68,7 +68,7 @@ To set the type of DRBG that will be instantiated, use the
 L<RAND_set_DRBG_type(3)> call before accessing the random number generation
 infrastructure.
 
-The two set functions, operate on the the current thread.  If you want to
+The two set functions, operate on the current thread.  If you want to
 use the same random number generator across all threads, each thread
 must individually call the set functions.
 
diff --git a/doc/man7/ossl-guide-migration.pod b/doc/man7/ossl-guide-migration.pod
index bfcf0d1a14..4835db7f84 100644
--- a/doc/man7/ossl-guide-migration.pod
+++ b/doc/man7/ossl-guide-migration.pod
@@ -1104,7 +1104,7 @@ L<EVP_DecryptInit_ex(3)>, L<EVP_DecryptUpdate(3)> and L<EVP_DecryptFinal_ex(3)>.
 
 Use of low-level digest functions such as L<SHA1_Init(3)> have been
 informally discouraged from use for a long time.  Applications should instead
-use the the high level EVP APIs L<EVP_DigestInit_ex(3)>, L<EVP_DigestUpdate(3)>
+use the high level EVP APIs L<EVP_DigestInit_ex(3)>, L<EVP_DigestUpdate(3)>
 and L<EVP_DigestFinal_ex(3)>, or the quick one-shot L<EVP_Q_digest(3)>.
 
 Note that the functions L<SHA1(3)>, L<SHA224(3)>, L<SHA256(3)>, L<SHA384(3)>