From 904b167493b574528cf610dadbf2c764547d61b3 Mon Sep 17 00:00:00 2001
From: ff00ff-security <195214694+ff00ff-security@users.noreply.github.com>
Date: Thu, 16 Jan 2025 14:59:17 +0000
Subject: [PATCH] Update Authentication_Cheat_Sheet.md inclusive/neutral
 terminology (#1582)

Updated wording to use inclusive/neutral terminology.
---
 cheatsheets/Authentication_Cheat_Sheet.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cheatsheets/Authentication_Cheat_Sheet.md b/cheatsheets/Authentication_Cheat_Sheet.md
index 0fc5e81416..cfb6efb10d 100644
--- a/cheatsheets/Authentication_Cheat_Sheet.md
+++ b/cheatsheets/Authentication_Cheat_Sheet.md
@@ -90,7 +90,7 @@ TLS Client Authentication, also known as two-way TLS authentication, consists of
 It is a good idea to do this when:
 
 - It is acceptable (or even preferred) that the user has access to the website only from a single computer/browser.
-- The user is not easily scared by the process of installing TLS certificates on his browser, or there will be someone, probably from IT support, who will do this for the user.
+- The user is not easily scared by the process of installing TLS certificates on their browser, or there will be someone, probably from IT support, who will do this for the user.
 - The website requires an extra step of security.
 - It is also a good thing to use when the website is for an intranet of a company or organization.