Fixed typos in Readme

Author: frwololo

README.md

@@ -6,7 +6,7 @@ A WebServer+Wifi Repeater+Fake DNS Server to Host PS4/PS5 Exploits on ESP8266
 
 
 ## Details and usage
-This is an implementation of a barebones webServer to Host PS4/PS5 Exploits on an ESP86, that also acts as a Wifi Repeater to maintain internet access for the console. This tool has the following features:
+This is an implementation of a barebones webServer to Host PS4/PS5 Exploits on an ESP8266, that also acts as a Wifi Repeater to maintain internet access for the console. This tool has the following features:
 - Basic Webserver to host PS4 and PS5 exploits (including limited support for HTTPS to handle the PS5)
 - FakeDNS that redirects playstation.net (user guides) to the web server, and blocks other playstation addresses
 - The Access Point acts as a Wifi Repeater so that the clients (PS4, PS5, PC) can still access the internet for domains that are not blocked/redirected by the DNS
@@ -52,7 +52,7 @@ In other words, it's a self contained solution to run the PS4/PS5 exploits while
 - Set up your console's Network Settings to connect via Wifi, using your ESP8266 Access point ("PS5_WEB_AP" by default, and password "password")
 - On PS4 or PS5, go to Settings > User's Guide > User's Guide, this should load the exploit page.
 
-There are a bunch of tutorials on how to run these out there, once ths host is set up it is no different from others, except for the fact that it allows the console to access internet
+There are a bunch of tutorials on how to run these out there, once the host is set up it is no different from others, except for the fact that it allows the console to access internet
 
 #### Notes
 - If you want/need to get everything back offline like "other" ESP8266 Hosts, go back to 10.1.1.1/admin.html, set "ENABLE WIFI" to 0, then save the config again.
@@ -72,7 +72,7 @@ There are a bunch of tutorials on how to run these out there, once ths host is s
 
 ## FAQ and Troubleshooting
 ### How good is the FakeDNS?
-It's a very rough design that just looks for some specific domain names (currently hardcoded inside the main source file) and either redirect those to the local ESP WebServer (namely playstation.net, where the user guides are hosted), or blocks them (other kwnonw PlayStation telemetry domains). Just because the DNS suggests that these domains should be redirect or blocked, doesn't mean the client device can't do whatever they like. In the case of the PS4 and PS5, this seems to be enough, but I can't guarantee that the console isn't bypassing DNS replies, and (for example) asks another DNS on the Network. I can imagine this would be technically doable now that the ESP86 opens Internet access.
+It's a very rough design that just looks for some specific domain names (currently hardcoded inside the main source file) and either redirect those to the local ESP WebServer (namely playstation.net, where the user guides are hosted), or blocks them (other kwnonw PlayStation telemetry domains). Just because the DNS suggests that these domains should be redirect or blocked, doesn't mean the client device can't do whatever they like. In the case of the PS4 and PS5, this seems to be enough, but I can't guarantee that the console isn't bypassing DNS replies, and (for example) asks another DNS on the Network. I can imagine this would be technically doable now that the ESP8266 opens Internet access.
 
 Furthermore, there's no support for regexps at the moment so it's really a simple string check in its current state.
 
@@ -81,14 +81,14 @@ If you get some "Error Connection close" when testing https://10.1.1.1 (local HT
 
 ## Technical thoughts and stuff
 ### Why
-Multiple versions of the ESP8266 Hosts exist to host PS4/PS5 exploits, for the most part based on work by Stooged (https://github.com/stooged/). To my knowledge however, none of them allow the clients (PS4, PS5, or the PC that you inevitably want to connect to them) to access Internet. The Access Point is generally stuck as a "Local Network" provider. This is enough to provide basic exploit access to the console, but there might be cases where we want to maintain Internet access anyway.
-
-Most people achieve that by using a "Fake DNS" and either hosting the exploit locally on their PC ( https://wololo.net/2022/10/04/tutorial-running-the-ps5-4-03-exploit-on-windows-with-additional-dns-security-telemetry-blocking-etc/ ) or accessing one of the many "exploit hosts" online.
+Multiple versions of the ESP8266 Hosts exist to host PS4/PS5 exploits, for the most part based on work by Stooged (https://github.com/stooged/). To my knowledge however, none of them allow the clients (PS4, PS5, or the PC that you inevitably want to connect to them) to access the Internet. The Access Point is generally stuck as a "Local Network" provider. This is enough to provide basic exploit access to the console (and it ensures you won't get an automatic firmware update for the console), but there might be cases where we want to maintain Internet access anyway.
 
+Most people achieve that by using a "Fake DNS" and either hosting the exploit locally on their PC ( https://wololo.net/2022/10/04/tutorial-running-the-ps5-4-03-exploit-on-windows-with-additional-dns-security-telemetry-blocking-etc/ ) or accessing one of the many "exploit hosts" online. These solutions do not rely on ESP8266 whatsoever, or only as one element of a bigger solution (e.g; ESP8266 + Raspberry Pi).
+ 
 Given that the ESP8266 is able to simultaneously act as an an Access Point AND connect to a Wifi Router, I assumed there had to be ways it could act as a self contained Web Server + Fake DNS + Wifi Repeater, to mimic the other solutions. Turns out it is possible, with some limitations.
 
 ### Technical considerations
-There are samples showing us how to run an HTTPS WebServer on ESP8266, how to block specific domain names with some ad-blocking DNS, how to enable NAT to use th device as a Wifi Repeater. There wasn't any example of how these things are all put together, so I guess this is now it.
+There are samples showing us how to run an HTTPS WebServer on ESP8266, how to block specific domain names with some ad-blocking DNS, how to enable NAT to use the device as a Wifi Repeater. There wasn't any example of how these things are all put together, so I guess this is now it.
 Technically speaking, putting all these components together isn't particularly hard: The HTTP and HTTPS WebServer, including their content (exploits-related redirections, webAdmin) were takend from projects by [Stooged](https://github.com/stooged), which are widely used in the PS4/PS5 scene on multiple variations of the ESP8266 Hosts. The Default DNS Server however, is designed in a way that it will redirect all traffic to the AP Host (or that's how I understood it at least), so I replaced it with a modified version by [Rubfi](https://github.com/rubfi) which did more or less what I wanted. Last but not least, "Wifi Repeater" samples were available (technically, NAT routing) e.g. at https://github.com/AliBigdeli/Arduino-ESP8266-Repeater. 
 
 ## Credits