Fix number of gotos in 2024/ferguson1

There actually are 134 post cpp - not 130.

2024/ferguson1/README.md

@@ -39,7 +39,7 @@
 ## Judges' remarks:
 
 You will have to go to "Fun-Damentals" to understand the logic flow of
-this game.  While you jump as many as 130 times to travel from `main()`
+this game.  While you jump as many as 134 times to travel from `main()`
 to an successful `exit(666)` you may have a devil of a time trying to
 figure out how this program actually does what it does.
 
@@ -55,7 +55,7 @@ inside this C code.  :-)
 
 
 <div id="devil">
-### A Pact With the Devil On the Oregon Trail (...and his 130 regrets of goto)
+### A Pact With the Devil On the Oregon Trail (...and his 134 regrets of goto)
 </div>
 
 The **Go To Hell In A Handcart Travel Company** PROUDLY welcomes all sinners to
@@ -2447,7 +2447,7 @@ really does not seem to be dead (it's quite sneaky).
 
 I could be wrong on whether this is one the compiler missed though: it's hard to
 follow all the `goto`s. As you find out in [obfuscation.html](obfuscation.html) it's
-130 after pre-processing! Yes I might be mad. But then again I might just be
+134 after pre-processing! Yes I might be mad. But then again I might just be
 the Devil. Who knows? What I do know is code that is meant to be reached is
 reached! Yes I've played it many times. Some code I made dead seemed totally
 useless but why not add to confusion? If that includes one that the compiler

2024/ferguson1/index.html

@@ -485,7 +485,7 @@ Location: <a href="../../location.html#US">US</a> - <em>United States of America
 <pre><code>    ./prog.alt</code></pre>
 <h2 id="judges-remarks">Judges’ remarks:</h2>
 <p>You will have to go to “Fun-Damentals” to understand the logic flow of
-this game. While you jump as many as 130 times to travel from <code>main()</code>
+this game. While you jump as many as 134 times to travel from <code>main()</code>
 to an successful <code>exit(666)</code> you may have a devil of a time trying to
 figure out how this program actually does what it does.</p>
 <p>Before you set off on your adventure to decode this program’s logic, make
@@ -496,7 +496,7 @@ how well prepared you are, you will have a devil of a time jumping around
 inside this C code. :-)</p>
 <h2 id="authors-remarks">Author’s remarks:</h2>
 <div id="devil">
-<h3 id="a-pact-with-the-devil-on-the-oregon-trail-and-his-130-regrets-of-goto">A Pact With the Devil On the Oregon Trail (…and his 130 regrets of goto)</h3>
+<h3 id="a-pact-with-the-devil-on-the-oregon-trail-and-his-134-regrets-of-goto">A Pact With the Devil On the Oregon Trail (…and his 134 regrets of goto)</h3>
 </div>
 <p>The <strong>Go To Hell In A Handcart Travel Company</strong> PROUDLY welcomes all sinners to
 our GREATEST destination yet, with:</p>
@@ -2440,7 +2440,7 @@ might be one that the compiler does not trigger a dead code warning on. It
 really does not seem to be dead (it’s quite sneaky).</p>
 <p>I could be wrong on whether this is one the compiler missed though: it’s hard to
 follow all the <code>goto</code>s. As you find out in <a href="obfuscation.html">obfuscation.html</a> it’s
-130 after pre-processing! Yes I might be mad. But then again I might just be
+134 after pre-processing! Yes I might be mad. But then again I might just be
 the Devil. Who knows? What I do know is code that is meant to be reached is
 reached! Yes I’ve played it many times. Some code I made dead seemed totally
 useless but why not add to confusion? If that includes one that the compiler