From e11c4ed30d4e5e88eac3eae4729fd4ae36e0224e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jo=C3=A3o=20Pacheco?= <joao.pacheco@g.globo>
Date: Wed, 6 Oct 2021 17:41:25 -0300
Subject: [PATCH] fix typos

---
 owasp-top10-2021-apps/a6/golden-hat/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/owasp-top10-2021-apps/a6/golden-hat/README.md b/owasp-top10-2021-apps/a6/golden-hat/README.md
index aa6eaef26..55142bac9 100644
--- a/owasp-top10-2021-apps/a6/golden-hat/README.md
+++ b/owasp-top10-2021-apps/a6/golden-hat/README.md
@@ -60,7 +60,7 @@ Once we try reaching the `/golden.secret` we can see interesting headers:
     <img src="https://raw.githubusercontent.com/chinchila/secDevLabs/lab-smuggling/owasp-top10-2021-apps/a6/golden-hat/images/attack1.png"/>
 </p>
 
-As we can see this `Via: mitmproxy/5.3.0` helps us with the recon. Now that we know the vulnerability we can search for CVEs on this version of mitmproxy. Once we found the CVE-2021-39214, we can make a 1-day exploit to this vulnerability.
+As we can see this `Via: mitmproxy/5.3.0` helps us with the recon. Now that we know what is running on the server we can search for CVEs on this version of mitmproxy. Once we found the CVE-2021-39214, we can make an exploit to this vulnerability.
 
 Let's take a look on the mitmproxy source code, [TAG 5.3.0](https://github.com/mitmproxy/mitmproxy/tree/v5.3.0) at file [/mitmproxy/net/http/http1/read.py:L209](https://github.com/mitmproxy/mitmproxy/blob/a738b335a36b58f2b30741d76d9fe41866309299/mitmproxy/net/http/http1/read.py#L209):