From cae782d2792eec57ccc489869c7298462813ccd9 Mon Sep 17 00:00:00 2001
From: Peter Bourgon <peterbourgon@users.noreply.github.com>
Date: Thu, 10 Mar 2022 17:25:25 +0100
Subject: [PATCH] README: fix link to issue

---
 README.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index afbdd08..ae618b2 100644
--- a/README.md
+++ b/README.md
@@ -88,9 +88,11 @@ type ConfigFileParser func(r io.Reader, set func(name, value string) error) erro
 In general, you should call flag.NewFlagSet with the flag.ContinueOnError error 
 handling strategy, which, somewhat confusingly, is the only way that ff.Parse can
 return errors. (The other strategies terminate the program on error. Rude!) This 
-is [the only way to detect certain types of parse failures][#90], in addition to 
+is [the only way to detect certain types of parse failures][90], in addition to 
 being good practice in general.
 
+[90]: https://github.com/peterbourgon/ff/issues/90
+
 ## Flags and env vars
 
 One common use case is to allow configuration from both flags and env vars.