From ea0df05817f7a7cd93ac30e0ebb2070eb0bd36a8 Mon Sep 17 00:00:00 2001
From: Cypher Pepe <125112044+cypherpepe@users.noreply.github.com>
Date: Tue, 17 Dec 2024 23:11:16 +0300
Subject: [PATCH] typos lib.rs

---
 curves/secp256k1-recover/src/lib.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/curves/secp256k1-recover/src/lib.rs b/curves/secp256k1-recover/src/lib.rs
index 837f2b8cf3..28fc2615b1 100644
--- a/curves/secp256k1-recover/src/lib.rs
+++ b/curves/secp256k1-recover/src/lib.rs
@@ -137,7 +137,7 @@ solana_define_syscall::define_syscall!(fn sol_secp256k1_recover(hash: *const u8,
 /// # Hashing messages
 ///
 /// In ECDSA signing and key recovery the signed "message" is always a
-/// crytographic hash, not the original message itself. If not a cryptographic
+/// cryptographic hash, not the original message itself. If not a cryptographic
 /// hash, then an adversary can craft signatures that recover to arbitrary
 /// public keys. This means the caller of this function generally must hash the
 /// original message themselves and not rely on another party to provide the
@@ -228,7 +228,7 @@ solana_define_syscall::define_syscall!(fn sol_secp256k1_recover(hash: *const u8,
 /// lengths of `hash` and `signature` beforehand.
 ///
 /// When run on-chain this function will not directly validate the lengths of
-/// `hash` and `signature`. It will assume they are the the correct lengths and
+/// `hash` and `signature`. It will assume they are the correct lengths and
 /// pass their pointers to the runtime, which will interpret them as 32-byte and
 /// 64-byte buffers. If the provided slices are too short, the runtime will read
 /// invalid data and attempt to interpret it, most likely returning an error,