From b561851bd1dcacf73085d61bfeb9632adb734bb3 Mon Sep 17 00:00:00 2001
From: WhySooooFurious <45163558+WhySooooFurious@users.noreply.github.com>
Date: Thu, 19 Sep 2024 00:29:28 +0800
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 9273133..853e240 100644
--- a/README.md
+++ b/README.md
@@ -17,7 +17,7 @@ My DNS is compatible with these services
 
 Follow Part 1 of my main guide to install the DNS blocker.
 
-Part 2,3 and 4 is for ESign itself.
+Part 2, 3 and 4 is for ESign itself.
 
 ## How does this method work?
 By using leaked business enterprise certificates, We can sign apps using their credentials which means Apple lets us install the apps without any hassle, however after a while Apple revokes the certificate, this is where the WhySooooFurious DNS Blocker comes in, the DNS blocker blocks Apple servers from contacting your device about the expired/revoked/blacklisted certificate which in turn lets you use the apps for however long you'd like. The DNS also blocks ESign analytics as a bonus!