From 39ce39aa4d5b02e2b57b745e19debfc412b1f154 Mon Sep 17 00:00:00 2001
From: Anthony Accioly <1591739+aaccioly@users.noreply.github.com>
Date: Mon, 23 Jun 2025 14:21:32 +0100
Subject: [PATCH] fix: correct grammar in bud/01 redirect requirements

Co-authored-by: hzrd149 <8001706+hzrd149@users.noreply.github.com>
---
 buds/01.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/buds/01.md b/buds/01.md
index 4808b81..94243bf 100644
--- a/buds/01.md
+++ b/buds/01.md
@@ -86,8 +86,8 @@ server does not know the MIME type of the blob, it MUST default to `application/
 
 If the endpoint returns a redirection 3xx status code such as 307 or 308 ([RFC 9110 section
 15.4](https://datatracker.ietf.org/doc/html/rfc9110#name-redirection-3xx)), it MUST redirect to a URL containing the
-same sha256 hash as the requested blob. This ensures that if a user copies or reuses the redirect URL, it will still
-contain the original sha56 hash.
+same sha256 hash as the requested blob. This ensures that if a user copies or reuses the redirect URL, it will
+contain the original sha256 hash.
 
 While the final blob may not be served from a Blossom server (e.g. CDN, IPFS, object storage, etc.), the destination
 server MUST set the `Access-Control-Allow-Origin: *` header on the response to allow cross-origin requests, as well as