From ab9f7fd107275b24fb1ffebf677026df8336d3d2 Mon Sep 17 00:00:00 2001
From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com>
Date: Wed, 17 Jan 2024 05:53:31 -0800
Subject: [PATCH] Fix references in 2018/burton1/README.md

I believe that the previous commit got the ordering wrong. The
significant inspiration for the contest was linked to directly in
markdown rather than a '[...]: ...' style link so reference 3 should
actually be reference 2 (instead of the link to the main IOCCC readme
file). A question of course is what to do about the link

    http://ioccc.org/all/README

since all README files have been changed to README.md files.
Nevertheless right now the ioccc.org site has README, not README.md, so
it would be either a broken link or it would refer to say /all/README.md
(which might be the best way?).
---
 2018/burton1/README.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/2018/burton1/README.md b/2018/burton1/README.md
index 4c086d58d..f67590496 100644
--- a/2018/burton1/README.md
+++ b/2018/burton1/README.md
@@ -209,8 +209,7 @@ but `pcc` handles them correctly, and neither compiler accepts `char o[]` or
 not yet written for UNIX).
 
 [1]: http://minnie.tuhs.org/cgi-bin/utree.pl
-[2]: http://ioccc.org/all/README
-[3]: https://web.archive.org/web/20180521074522/http://www.computerworld.com.au/article/279011/a-z_programming_languages_bourne_shell_sh/?pp=4
+[2]: https://web.archive.org/web/20180521074522/http://www.computerworld.com.au/article/279011/a-z_programming_languages_bourne_shell_sh/?pp=4
 
 More significant is that v7 `printf(3)` does not report the number of characters
 written, and therefore 111 compiles but does not work correctly; 113 is the