From 3412b9a6e850aae3335af1bc2cdf8e172a78a6fd Mon Sep 17 00:00:00 2001
From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com>
Date: Tue, 13 Aug 2024 07:11:36 -0700
Subject: [PATCH] Typo fix in 2004/burley/index.html
---
2004/burley/README.md | 2 +-
2004/burley/index.html | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/2004/burley/README.md b/2004/burley/README.md
index 88ee57588..7f81d42f4 100644
--- a/2004/burley/README.md
+++ b/2004/burley/README.md
@@ -86,7 +86,7 @@ Notice the clever use of `setjmp(3)` and `longjmp(3)` calls. Can you keep track
of what state is being saved and restored?
**NOTE**: the author talks about how it is a single statement. This might not be
-strictly true in 2023 for the fixes for it to work so you can look at the
+strictly true in 2023 with the fixes for it to work so you can look at the
original file [burley.orig.c](%%REPO_URL%%/2004/burley/burley.orig.c) to see
what is meant.
diff --git a/2004/burley/index.html b/2004/burley/index.html
index 565a31158..7b2fb80f2 100644
--- a/2004/burley/index.html
+++ b/2004/burley/index.html
@@ -488,7 +488,7 @@ the program so this “strategy” no longer works?
Notice the clever use of setjmp(3) and longjmp(3) calls. Can you keep track
of what state is being saved and restored?
NOTE: the author talks about how it is a single statement. This might not be
-strictly true in 2023 for the fixes for it to work so you can look at the
+strictly true in 2023 with the fixes for it to work so you can look at the
original file burley.orig.c to see
what is meant.