Fix typos.

ChangeLog

@@ -100,7 +100,7 @@
 
 	* release version 3.0
 
-	* plugins/*: Move all crypt releated code into plugins.
+	* plugins/*: Move all crypt related code into plugins.
 	* plugins/sha256: New, $5$ aka sha256 hash.
 	* plugins/sha512: New, $6$ aka sha512 hash.
 
@@ -153,7 +153,7 @@
 
 	* src/x86.S: Added, optimized, thread safe version for ix86.
 
-	* src/crypt_blowfish.c: Use optimized assember functions on ix86.
+	* src/crypt_blowfish.c: Use optimized assembler functions on ix86.
 
 	* libxcrypt.spec: New.
 

NEWS

@@ -170,7 +170,7 @@ Version 4.3.2
 * Fix the gensalt function for the NT hashing method ($3$) to
   properly terminate its output string.  The output buffer for the
   returned string must be at least 30 bytes long.
-* Remove the gensalt fuction for the bcrypt x variant ($2x$).
+* Remove the gensalt function for the bcrypt x variant ($2x$).
   This prefix was never intended for use when hashing new passphrases.
   The only use case originally intended was to manually edit '$2a$' to
   '$2x$' in passphrase hashes to knowingly take the risk yet enable

doc/crypt.5

@@ -173,7 +173,7 @@ Recommended for new hashes.
 .hash "$y$" "\e$y\e$[./A-Za-z0-9]+\e$[./A-Za-z0-9]{,86}\e$[./A-Za-z0-9]{43}" unlimited 8 256 256 "up to 512" "1 to 11 (logarithmic)"
 .Ss gost-yescrypt
 gost-yescrypt uses the output from the yescrypt hashing method in place of a
-hmac message.  Thus, the yescrypt crypto properties are superseeded by the
+hmac message.  Thus, the yescrypt crypto properties are superseded by the
 GOST R 34.11-2012 (Streebog) hash function with a 256 bit digest.
 This hashing method is useful in applications that need modern passphrase
 hashing methods, but require to rely on the cryptographic properties of GOST

lib/alg-hmac-sha1.h

@@ -27,7 +27,7 @@
  */
 
 /* Generate the keyed-hash message authentication code of TEXT and KEY.
-   The resulting HMAC is writen into RESBUF, which should point to 20
+   The resulting HMAC is written into RESBUF, which should point to 20
    bytes of storage.  */
 extern void
 hmac_sha1_process_data (const uint8_t *text, size_t text_len,

lib/crypt-des.c

@@ -215,7 +215,7 @@ crypt_descrypt_rn (const char *phrase, size_t ARG_UNUSED (phr_size),
    Description: The cleartext is divided into blocks of 8 characters
    or less. Each block is encrypted using the standard UNIX libc crypt
    function. The result of the encryption for one block provides the
-   salt for the suceeding block.  The output is simply the
+   salt for the succeeding block.  The output is simply the
    concatenation of all the blocks.  Up to 16 blocks are supported
    (that is, the password can be no more than 128 characters long).
 

lib/xcrypt.h.in

@@ -28,7 +28,7 @@
    (v3.1.1 and earlier) of libxcrypt.
    We intentionally declare these functions using macros here,
    since we actually want to link compiled applications against
-   the unprefixed indentical functions defined in <crypt.h>.  */
+   the unprefixed identical functions defined in <crypt.h>.  */
 #ifndef IN_LIBCRYPT  /* Defined when building libxcrypt. */
 # ifdef __REDIRECT_NTH
 extern char * __REDIRECT_NTH (xcrypt, (const char *__phrase,

libxcrypt.spec.rpkg

@@ -272,7 +272,7 @@ This version of the libcrypt.so.1 library has entirely removed
 the functionality of the encrypt, encrypt_r, setkey, setkey_r,
 and fcrypt functions, while keeping fully binary compatibility
 with existing (third-party) applications possibly still using
-those funtions.  If such an application attemps to call one of
+those functions.  If such an application attempts to call one of
 these functions, the corresponding function will indicate that
 it is not supported by the system in a POSIX-compliant way.
 

test/special-char-salt.c

@@ -16,7 +16,7 @@
  * SUCH DAMAGE.
  */
 
-/* Simple test to ensure compatability of our implementations of the
+/* Simple test to ensure compatibility of our implementations of the
    md5crypt, sha256crypt, and sha512crypt hashing method with the ones
    found in other commonly used libcrypt libraries.  Their implementations
    allow for any ASCII character (with one exception to the colon ':'