From: Neil Horman Date: Thu, 11 Apr 2024 20:19:01 +0000 (-0400) Subject: Remove repetitive words X-Git-Tag: openssl-3.4.0-alpha1~692 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3c0bb68c75bc517224d57b973dce0cd016342faf;p=thirdparty%2Fopenssl.git Remove repetitive words Signed-off-by: fanqiaojun Reviewed-by: Paul Dale Reviewed-by: Tim Hudson Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/24128) --- diff --git a/crypto/chacha/asm/chachap10-ppc.pl b/crypto/chacha/asm/chachap10-ppc.pl index 032cf2585bb..ea4f3faf53d 100755 --- a/crypto/chacha/asm/chachap10-ppc.pl +++ b/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 diff --git a/doc/designs/quic-design/quic-api.md b/doc/designs/quic-design/quic-api.md index fceacdda6df..8aa972b4dfe 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 172098b5475..4bea5fd5033 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 032edb2a368..51473a65c29 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 diff --git a/doc/man3/EVP_EncryptInit.pod b/doc/man3/EVP_EncryptInit.pod index 7ecfec86373..0bf10c90d71 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 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 88a2f6c311b..62365a7e309 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 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 bfcf0d1a144..4835db7f84a 100644 --- a/doc/man7/ossl-guide-migration.pod +++ b/doc/man7/ossl-guide-migration.pod @@ -1104,7 +1104,7 @@ L, L and L. Use of low-level digest functions such as L have been informally discouraged from use for a long time. Applications should instead -use the the high level EVP APIs L, L +use the high level EVP APIs L, L and L, or the quick one-shot L. Note that the functions L, L, L, L diff --git a/ssl/quic/quic_port.c b/ssl/quic/quic_port.c index 96c289f7e7e..c8cdc668989 100644 --- a/ssl/quic/quic_port.c +++ b/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)