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)

crypto/chacha/asm/chachap10-ppc.pl

@@ -787,7 +787,7 @@ $code.=<<___;
 
 	vxxlor	        $xv6  ,$xb6,$xb6                # save vr23, so we get 8 regs
 	vxxlor	        $xv7  ,$xb7,$xb7                # save vr23, so we get 8 regs
-	be?vxxlorc      $beperm,$xv26,$xv26             # copy back the the beperm.
+	be?vxxlorc      $beperm,$xv26,$xv26             # copy back the beperm.
 
 	vxxlorc	   @K[0],$xv0,$xv0                #27
 	vxxlorc	   @K[1],$xv1,$xv1 		  #24

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

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,

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>

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.

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.
 

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)>

ssl/quic/quic_port.c

@@ -220,7 +220,7 @@ static int port_update_poll_desc(QUIC_PORT *port, BIO *net_bio, int for_write)
      * single pollable currently. In the future, once complete polling
      * infrastructure has been implemented, this limitation can be removed.
      *
-     * For now, just update the descriptor on the the engine's reactor as we are
+     * For now, just update the descriptor on the engine's reactor as we are
      * guaranteed to be the only port under it.
      */
     if (for_write)