From e3322d8d891a4a15f6378e5d35d5c8a48812b983 Mon Sep 17 00:00:00 2001
From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com>
Date: Mon, 6 Nov 2023 08:09:03 -0800
Subject: [PATCH] Format/typo check 1991/cdupont/README.md

---
 1991/cdupont/README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/1991/cdupont/README.md b/1991/cdupont/README.md
index 81fa33093..b06ccc4d1 100644
--- a/1991/cdupont/README.md
+++ b/1991/cdupont/README.md
@@ -21,7 +21,7 @@ sorryfor_this_unused_but_very_needed_label:
 ```
 
 Notice that if you C beautify (cb) or pre-process this program, it
-will no longer work correctly, or at all.  (go ahead, try it... :-))
+will no longer work correctly, if at all.  (go ahead, try it... :-))
 
 NOTE: One should remove the final trailing newline to obtain the
 original source file.  This step is not needed to compile
@@ -36,7 +36,7 @@ letter and key. Thus, the message is code.  That is why I use silly
 comments, most often badly spaced.
 
 The space character sequence between the words is given by a simple
-computation on an octal constant (given here as an hex value, of
+computation in an octal constant (given here as an hex value, of
 course).
 
 This way, any message can be mixed into a code, since the keys allow