Fix typo

Closes #5579

crypto/src/main/java/org/springframework/security/crypto/password/LdapShaPasswordEncoder.java

@@ -38,7 +38,7 @@ import java.security.MessageDigest;
  * @author Luke Taylor
  * @since 4.2.6
  * @deprecated Digest based password encoding is not considered secure. Instead use an
- * adaptive one way funciton like BCryptPasswordEncoder, Pbkdf2PasswordEncoder, or
+ * adaptive one way function like BCryptPasswordEncoder, Pbkdf2PasswordEncoder, or
  * SCryptPasswordEncoder. Even better use {@link DelegatingPasswordEncoder} which supports
  * password upgrades. There are no plans to remove this support. It is deprecated to indicate
  * that this is a legacy implementation and using it is considered insecure.

crypto/src/main/java/org/springframework/security/crypto/password/Md4PasswordEncoder.java

@@ -70,7 +70,7 @@ import org.springframework.security.crypto.keygen.StringKeyGenerator;
  * @author Rob winch
  * @since 5.1
  * @deprecated Digest based password encoding is not considered secure. Instead use an
- * adaptive one way funciton like BCryptPasswordEncoder, Pbkdf2PasswordEncoder, or
+ * adaptive one way function like BCryptPasswordEncoder, Pbkdf2PasswordEncoder, or
  * SCryptPasswordEncoder. Even better use {@link DelegatingPasswordEncoder} which supports
  * password upgrades. There are no plans to remove this support. It is deprecated to indicate
  * that this is a legacy implementation and using it is considered insecure.

crypto/src/main/java/org/springframework/security/crypto/password/MessageDigestPasswordEncoder.java

@@ -74,7 +74,7 @@ import java.security.MessageDigest;
  * @author Rob Winch
  * @since 4.2.6
  * @deprecated Digest based password encoding is not considered secure. Instead use an
- * adaptive one way funciton like BCryptPasswordEncoder, Pbkdf2PasswordEncoder, or
+ * adaptive one way function like BCryptPasswordEncoder, Pbkdf2PasswordEncoder, or
  * SCryptPasswordEncoder. Even better use {@link DelegatingPasswordEncoder} which supports
  * password upgrades. There are no plans to remove this support. It is deprecated to indicate
  * that this is a legacy implementation and using it is considered insecure.