From 9bb18514d16a7f9e9b33c970d21b0a1d9125205e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?alp1n3=20=F0=9F=8C=B2?=
 <59985265+alp1n3-eth@users.noreply.github.com>
Date: Tue, 17 Dec 2024 11:42:06 -0500
Subject: [PATCH] Fixed spelling error

liueu -> lieu
---
 .../07-Testing_for_Weak_Authentication_Methods.md               | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/document/4-Web_Application_Security_Testing/04-Authentication_Testing/07-Testing_for_Weak_Authentication_Methods.md b/document/4-Web_Application_Security_Testing/04-Authentication_Testing/07-Testing_for_Weak_Authentication_Methods.md
index 8be4c19908..29032da840 100644
--- a/document/4-Web_Application_Security_Testing/04-Authentication_Testing/07-Testing_for_Weak_Authentication_Methods.md
+++ b/document/4-Web_Application_Security_Testing/04-Authentication_Testing/07-Testing_for_Weak_Authentication_Methods.md
@@ -25,7 +25,7 @@ Additionally, applications may utilize alternative credentials that are treated
 6. Is the user prevented from using his username or other account information (such as first or last name) in the password?
 7. What are the minimum and maximum password lengths that can be set, and are they appropriate for the sensitivity of the account and application?
 8. Is it possible to set common passwords such as `Password1` or `123456`?
-9. Is the credential chosen for the user by the application, such as a social security number or a birthdate? Is the credential that's utilized in liueu of a standard password easily obtainable, predictable, or able to be brute forced?
+9. Is the credential chosen for the user by the application, such as a social security number or a birthdate? Is the credential that's utilized in lieu of a standard password easily obtainable, predictable, or able to be brute forced?
 
 ## Remediation