From 9f174d964be8306997e52f5d26f7be1b93ae0a07 Mon Sep 17 00:00:00 2001
From: fria <138676274+friadev@users.noreply.github.com>
Date: Fri, 28 Mar 2025 11:41:19 -0500
Subject: [PATCH] more detail on blind signatures

---
 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 256c89353..e85d03329 100644
--- a/blog/posts/privacy-pass.md
+++ b/blog/posts/privacy-pass.md
@@ -64,7 +64,7 @@ You can imagine blind signatures like an envelope that's been wrapped in [carbon
 
 The organization then signs it, indicating you're a valid customer and you're allowed to access the service.
 
-Later, when you're presented with a request to authenticate as an active subscriber of  PrivacyGuides+, you unwrap the envelope and discard it along with the carbon paper. You rewrap it in a new envelope with a window showing the signature, and the requester can then be sure that you're allowed to access PrivacyGuides+.
+Later, when you're presented with a request to authenticate as an active subscriber of  PrivacyGuides+, you unwrap the envelope and discard it along with the carbon paper. You rewrap it in a new envelope with a window showing the signature and a different pseudonym, and the requester can then be sure that you're allowed to access PrivacyGuides+.
 
 ![A diagram showing an envelope being wrapped in carbon paper, transfered to an organization, then passing over a boundary representing the unlinkability between the two transactions. Then the envelope is unwrapped, put in a new envelope with a window showing the signature from the previous organization, and presented to a different organization.](../assets/images/privacy-pass/Blind_signatures.png)