chore: fix typos (#1274)

Signed-off-by: snoppy <[email protected]>
weidai11 · Apr 23, 2024 · c2bd7ef · c2bd7ef
1 parent 782057f
commit c2bd7ef
Show file tree

Hide file tree

Showing 4 changed files with 4 additions and 4 deletions.
diff --git a/nbtheory.h b/nbtheory.h
@@ -112,7 +112,7 @@ CRYPTOPP_DLL bool CRYPTOPP_API IsPrime(const Integer &p);
 ///   level is greater than 1, then 10 round RabinMillerTest() primality testing is performed.
 CRYPTOPP_DLL bool CRYPTOPP_API VerifyPrime(RandomNumberGenerator &rng, const Integer &p, unsigned int level = 1);
 
-/// \brief Application callback to signal suitability of a cabdidate prime
+/// \brief Application callback to signal suitability of a candidate prime
 class CRYPTOPP_DLL PrimeSelector
 {
 public:

diff --git a/osrng.cpp b/osrng.cpp
@@ -23,7 +23,7 @@
 
 // FreeBSD links /dev/urandom -> /dev/random. It showed up when we added
 // O_NOFOLLOW to harden the non-blocking generator. Use Arc4Random instead
-// for a non-blocking generator. Arc4Random is cryptograhic quality prng
+// for a non-blocking generator. Arc4Random is cryptographic quality prng
 // based on ChaCha20. The ChaCha20 generator is seeded from /dev/random,
 // so we can't completely avoid the blocking.
 // https://www.freebsd.org/cgi/man.cgi?query=arc4random_buf.

diff --git a/rdrand.h b/rdrand.h
@@ -20,7 +20,7 @@
 //   GenerateBlock unconditionally retries and always fulfills the request.
 
 // Throughput varies wildly depending on processor and manufacturer. A Core i5 or
-//   Core i7 RDRAND can generate at over 200 MiB/s. It is below theroetical
+//   Core i7 RDRAND can generate at over 200 MiB/s. It is below theoretical
 //   maximum, but it takes about 5 instructions to generate, retry and store a
 //   result. A low-end Celeron may perform RDRAND at about 7 MiB/s. RDSEED
 //   performs at about 1/4 to 1/2 the rate of RDRAND. AMD RDRAND performed poorly

diff --git a/validate.h b/validate.h
@@ -21,7 +21,7 @@ NAMESPACE_BEGIN(CryptoPP)
 NAMESPACE_BEGIN(Test)
 
 // A hint to help locate TestData/ and TestVectors/ after install. Due to
-// execve the path can be malicious. If the path is ficticous then we move
+// execve the path can be malicious. If the path is fictitious then we move
 // onto the next potential path. Also note we only read from the path; we
 // never write through it. Storage for the string is in test.cpp.
 extern std::string g_argvPathHint;