examples should show how to check the signature of the next release

diff --git a/usr.bin/signify/signify.1 b/usr.bin/signify/signify.1
index 0e9cd3f..2d1a29e 100644 (file)
--- a/usr.bin/signify/signify.1
+++ b/usr.bin/signify/signify.1
@@ -1,4 +1,4 @@
-.\" $OpenBSD: signify.1,v 1.58 2024/02/17 16:13:24 deraadt Exp $
+.\" $OpenBSD: signify.1,v 1.59 2024/03/02 23:38:00 benno Exp $
 .\"
 .\"Copyright (c) 2013 Marc Espie <espie@openbsd.org>
 .\"Copyright (c) 2013 Ted Unangst <tedu@openbsd.org>
@@ -14,7 +14,7 @@
 .\"WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
 .\"ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\"OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-.Dd $Mdocdate: February 17 2024 $
+.Dd $Mdocdate: March 2 2024 $
 .Dt SIGNIFY 1
 .Os
 .Sh NAME
@@ -171,12 +171,12 @@ Verify a release directory containing
 .Pa SHA256.sig
 and a full set of release files:
 .Bd -literal -offset indent -compact
-$ signify -C -p /etc/signify/openbsd-75-base.pub -x SHA256.sig
+$ signify -C -p /etc/signify/openbsd-76-base.pub -x SHA256.sig
 .Ed
 .Pp
 Verify a bsd.rd before an upgrade:
 .Bd -literal -offset indent -compact
-$ signify -C -p /etc/signify/openbsd-75-base.pub -x SHA256.sig bsd.rd
+$ signify -C -p /etc/signify/openbsd-76-base.pub -x SHA256.sig bsd.rd
 .Ed
 .Pp
 Sign a gzip archive: