commit 2865452c40f26a847448a314a3f4b50e4b49322e
from: Omar Polo <op@omarpolo.com>
date: Thu Jan 11 16:26:50 2024 UTC

typo

commit - 1ee636a45c28838b3e3ce44eb8d998ecf3fa61df
commit + 2865452c40f26a847448a314a3f4b50e4b49322e
blob - 096332f7cd345e361e7081bb53e8955078c24ef5
blob + 9caa4b7794311f548dbe7c46c4d0de973abd1f06
--- site/index.gmi
+++ site/index.gmi
@@ -46,7 +46,7 @@ $ sudo make install # eventually
 A SHA256 file is available.  However, it only checks for accidental corruption.  You can use signify (gmid-VERS.sha256.sig) and the public key PUBKEY to cryptographically verify the downloaded tarball.  The signify public key for the previous and the next release is included in the tarball.
 
 => SITE/gmid-VERS.sha256	gmid-VERS.sha256
-=> SITE/gmid-VERS.sha25.sig	gmid-VERS.sha256.sig
+=> SITE/gmid-VERS.sha256.sig	gmid-VERS.sha256.sig
 
 To verify the signatures with signify(1):