From 5492b9bc53359cc1a548ee80d3c35f12ed13ab99 Mon Sep 17 00:00:00 2001
From: fria <138676274+friadev@users.noreply.github.com>
Date: Sat, 29 Mar 2025 17:19:56 -0500
Subject: [PATCH] typo

---
 blog/posts/privacy-pass.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/blog/posts/privacy-pass.md b/blog/posts/privacy-pass.md
index 6794cf270..25ac6a50e 100644
--- a/blog/posts/privacy-pass.md
+++ b/blog/posts/privacy-pass.md
@@ -106,7 +106,7 @@ The landscape is very confusing right now so I'll try to illucidate what I've fo
 
 ### Privacy Pass
 
-[Privacy Pass](https://privacypass.github.io) started out as an attempt at a acy-preserving way to bypass CAPTCHAs.
+[Privacy Pass](https://privacypass.github.io) started out as an attempt at a privacy-preserving way to bypass CAPTCHAs.
 
 It started out and is still an extension that can be installed on the [Chrome](https://chromewebstore.google.com/detail/silk-privacy-pass-client/ajhmfdgkijocedmfjonnpjfojldioehi) or [Firefox](https://addons.mozilla.org/en-US/firefox/addon/privacy-pass/) extension store, but it's since expanded to become an [IETF standard](https://datatracker.ietf.org/wg/privacypass/about/). Be warned that many reviews state the extension doesn't work anymore, if you were curious to try it out.