From d168dedaa308893f7945016aa21fcd6009406ab1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?st=C3=ABn?= <158809757+stenzzor@users.noreply.github.com>
Date: Wed, 9 Jul 2025 19:04:51 +0400
Subject: [PATCH] Update README.md

Removed spelling mistake.
---
 Upload Insecure Files/Configuration Apache .htaccess/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Upload Insecure Files/Configuration Apache .htaccess/README.md b/Upload Insecure Files/Configuration Apache .htaccess/README.md
index 2290d065..707de259 100644
--- a/Upload Insecure Files/Configuration Apache .htaccess/README.md	
+++ b/Upload Insecure Files/Configuration Apache .htaccess/README.md	
@@ -1,7 +1,7 @@
 # .htaccess
 
 Uploading an .htaccess file to override Apache rule and execute PHP.
-"Hackers can also use “.htaccess” file tricks to upload a malicious file with any extension and execute it. For a simple example, imagine uploading to the vulnerabler server an .htaccess file that has AddType application/x-httpd-php .htaccess configuration and also contains PHP shellcode. Because of the malicious .htaccess file, the web server considers the .htaccess file as an executable php file and executes its malicious PHP shellcode. One thing to note: .htaccess configurations are applicable only for the same directory and sub-directories where the .htaccess file is uploaded."
+"Hackers can also use “.htaccess” file tricks to upload a malicious file with any extension and execute it. For a simple example, imagine uploading to the vulnerable server an .htaccess file that has AddType application/x-httpd-php .htaccess configuration and also contains PHP shellcode. Because of the malicious .htaccess file, the web server considers the .htaccess file as an executable php file and executes its malicious PHP shellcode. One thing to note: .htaccess configurations are applicable only for the same directory and sub-directories where the .htaccess file is uploaded."
 
 ## Summary