Fix Typos in documentation and comments (#852)

* Update README.md

rephrase warning message in README.md

* EncodingPatternPreservation: fix typo

* AbstractCodec: fix typo

* AbstractCodec: there is no such thing as a footgun usage

* AbstractPushbackSequence: fix typo. see https://languagetool.org/insights/post/regard/

* Base64: fix typo

* HashTrie: fix typo

* HashTrie: fix typo

* HTMLEntityCodec: fix typo

* MySQLCodec: fix typo

* MySQLCodec: fix typo

* PushBackSequenceImpl: fix typo

* PushbackString: fix typo

* EsapiConfiguration: fix typo

* AbstractPrioritizedPropertyLoader: fix typo

* AbstractPrioritizedPropertyLoader: fix grammar

* CipherText: fix typo

* CipherTextSerializer: fix typo

* CryptoHelper: fix typo

* CryptoHelper: fix typo

* CryptoHelper: fix grammar

* CryptoToken: fix typo

* CryptoToken: fix typo

* PlainText: fix typo

* RequestRateThrottleFilter: fix typo

* SecurityWrapperRequest: fix typo

* CompositeLogScrubber: fix typo

* JavaLogBridge: fix typo

* Authenticator: fix typo

* Encoder: fix typo

* Encryptor: untangle unclear sentence

* ESAPI: fix typo

* HTTPUtilities: fix typo

* HTTPUtilities: fix typo

* Logger: fix typo

* Logger: fix typo

* SecurityConfiguration: fix typo

* StringUtilities: correct javadoc

* User: fix typo

* Validator: fix typo

* Validator: fix typo

* CollectionsUtil: fix typo

* ObjFactory: fix typo

* EncodeForBase64Tag: fix typo

* EncodeForCSSTag: fix typo

* EncodeForHTMLAttributeTag: fix typo

* EncodeForHTMLTag: fix typo

* EncodeForJavaScriptTag: fix typo

* EncodeForURLTag: fix typo

* EncodeForVBScriptTag: fix typo

* EncodeForXMLAttributeTag: fix typo

* EncodeForXMLTag: fix typo

* EncodeForXPathTag: fix typo

* AbstractAccessReferenceMap: fix typo

* StringUtilities: replaceNull: rephrase javadoc using @code

* Encryptor: decrypt: fix typo, use expression from before f5e138c

* User: setLastFailedLoginTime: use "authenticate" instead of "log in"

Author: DarioViva42

README.md

@@ -17,7 +17,7 @@ OWASP® ESAPI (The OWASP Enterprise Security API) is a free, open source, web ap
 # Jakarta EE Support
 **IMPORTANT:**
 ESAPI has supported the Jakarta Servlet API (i.e., **jakarta.servlet.api**) since release
-2.5.3.0.  (Unfortunately, we were just forgot to note that in this **README** file. Duh!)
+2.5.3.0.  (Unfortunately, this information was previously missing in this **README** file.)
 
 Therefore, for release 2.5.3.0 and later versions of ESAPI, ESAPI ought to be able to support Spring Boot 3, Spring 6, Tomcat 10,
 and other applications or libraries requiring Jarkata EE. (If you find a case where it does

src/main/java/org/owasp/esapi/Authenticator.java

@@ -148,7 +148,7 @@ public interface Authenticator {
      * <p>
      * <b>WARNING:</b> The implementation of this method as defined in the
      * default reference implementation class, {@code FileBasedAuthenticator},
-     * uses a password hash algorthim that is known to be weak. You are advised
+     * uses a password hash algorithm that is known to be weak. You are advised
      * to replace the default reference implementation class with your own custom
      * implementation that uses a stronger password hashing algorithm.
      * See class comments in * {@code FileBasedAuthenticator} for further details.

src/main/java/org/owasp/esapi/ESAPI.java

@@ -93,7 +93,7 @@ public static Authenticator authenticator() {
     }
 
     /**
-     * The ESAPI Encoder is primarilly used to provide <i>output</i> encoding to
+     * The ESAPI Encoder is primarily used to provide <i>output</i> encoding to
      * prevent Cross-Site Scripting (XSS).
      * @return the current ESAPI Encoder object being used to encode and decode data for this application.
      */

src/main/java/org/owasp/esapi/Encoder.java

@@ -519,7 +519,7 @@ public interface Encoder {
      *
      * NB: The reference implementation encodes almost everything and may over-encode.
      *
-     * The difficulty with XPath encoding is that XPath has no built in mechanism for escaping
+     * The difficulty with XPath encoding is that XPath has no built-in mechanism for escaping
      * characters. It is possible to use XQuery in a parameterized way to
      * prevent injection.
      *

src/main/java/org/owasp/esapi/Encryptor.java

@@ -162,8 +162,8 @@ CipherText encrypt(SecretKey key, PlainText plaintext)
      * </p>
      * @param ciphertext The {@code CipherText} object to be decrypted.
      * @return The {@code PlainText} object resulting from decrypting the specified
-     *            ciphertext. Note that it it is desired to convert the returned
-     *            plaintext byte array to a Java String is should be done using
+     *            ciphertext. Note that if it is desired to convert the returned
+     *            plaintext byte array to a Java String it should be done using
      *            {@code new String(byte[], "UTF-8");} rather than simply using
      *            {@code new String(byte[]);} which uses native encoding and may
      *            not be portable across hardware and/or OS platforms.
@@ -186,8 +186,8 @@ CipherText encrypt(SecretKey key, PlainText plaintext)
      * @param key        The {@code SecretKey} to use for encrypting the plaintext.
      * @param ciphertext The {@code CipherText} object to be decrypted.
      * @return The {@code PlainText} object resulting from decrypting the specified
-     *            ciphertext. Note that it it is desired to convert the returned
-     *            plaintext byte array to a Java String is should be done using
+     *            ciphertext. Note that if it is desired to convert the returned
+     *            plaintext byte array to a Java String it should be done using
      *            {@code new String(byte[], "UTF-8");} rather than simply using
      *            {@code new String(byte[]);} which uses native encoding and may
      *            not be portable across hardware and/or OS platforms.

src/main/java/org/owasp/esapi/HTTPUtilities.java

@@ -377,7 +377,7 @@ public interface HTTPUtilities
      * everything to keey your application and environment secure. Some of the more obvious omissions are the
      * absence of examining the actual file content to determine the actual file type or running some AV scan
      * on the uploaded files. You have to add that functionality to you if you want or need that. Some
-     * reasource that you may find usefule are:
+     * resource that you may find useful are:
      * <ul>
      *   <li><a href="https://cheatsheetseries.owasp.org/cheatsheets/File_Upload_Cheat_Sheet.html">OWASP File Upload Cheat Sheet</a></li>
      *   <li><a href="https://cheatsheetseries.owasp.org/cheatsheets/Denial_of_Service_Cheat_Sheet.html">OWASP Denial of Service Cheat Sheet</a></li>

src/main/java/org/owasp/esapi/Logger.java

@@ -89,9 +89,9 @@
  * the basis for its logging implementation. Both provided implementations implement requirements #1 through #5 above.
  * </p><p>
  * <i>Customization</i>: It is expected that most organizations may wish to implement their own custom {@code Logger} class in
- * order to integrate ESAPI logging with their specific logging infrastructure. The ESAPI feference implementations
+ * order to integrate ESAPI logging with their specific logging infrastructure. The ESAPI reference implementations
  * can serve as a useful starting point to intended to provide a simple functional example of an implementation, but
- * they are also largely usuable out-of-the-box with some additional minimal log configuration.
+ * they are also largely usable out-of-the-box with some additional minimal log configuration.
  *
  * @author Jeff Williams (jeff.williams .at. aspectsecurity.com) <a
  * href="http://www.aspectsecurity.com">Aspect Security</a>

src/main/java/org/owasp/esapi/SecurityConfiguration.java

@@ -179,7 +179,7 @@ public interface SecurityConfiguration extends EsapiPropertyLoader {
      * considered the <i>default</i> key size that ESAPI will use for symmetric
      * ciphers supporting multiple key sizes. (Note that there is also an <b>Encryptor.MinEncryptionKeyLength</b>,
      * which is the <i>minimum</i> key size (in bits) that ESAPI will support
-     * for encryption. (There is no miminimum for decryption.)
+     * for encryption. (There is no minimum for decryption.)
      *
      * @return the key length (in bits)
      * @deprecated Use SecurityConfiguration.getIntProp("appropriate_esapi_prop_name") instead.

src/main/java/org/owasp/esapi/StringUtilities.java

@@ -90,7 +90,7 @@ public static boolean contains(StringBuilder input, char c) {
     }
 
     /**
-     * Returns the replace value if the value of test is null, "null", or ""
+     * Returns {@code replace} if {@code test} is null, "null" (case-insensitive), or blank, otherwise {@code test}
      *
      * @param test The value to test
      * @param replace The replacement value

src/main/java/org/owasp/esapi/User.java

@@ -380,7 +380,7 @@ public interface User extends Principal, Serializable {
     /**
      * Set the time of the last failed login for this user.
      *
-     * @param lastFailedLoginTime the date and time when the user just failed to login correctly.
+     * @param lastFailedLoginTime the date and time when the user just failed to authenticate correctly.
      */
     void setLastFailedLoginTime(Date lastFailedLoginTime);