From cfd1f1c1cae516835d8166fa111b21a5e83aa8ca Mon Sep 17 00:00:00 2001
From: Kisaragi <48310258+KisaragiEffective@users.noreply.github.com>
Date: Sat, 20 May 2023 03:45:43 +0900
Subject: [PATCH] Fix typo in README.md (#312)

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 44ac42b7..d31bee43 100644
--- a/README.md
+++ b/README.md
@@ -97,7 +97,7 @@ Encoding a JWT takes 3 parameters:
 - some claims: your own struct
 - a key/secret
 
-When using HS256, HS2384 or HS512, the key is always a shared secret like in the example above. When using
+When using HS256, HS384 or HS512, the key is always a shared secret like in the example above. When using
 RSA/EC, the key should always be the content of the private key in the PEM or DER format.
 
 If your key is in PEM format, it is better performance wise to generate the `EncodingKey` once in a `lazy_static` or